1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Looks like the CloudFormation template that was shared tries to incorrectly create a resource without specifying the S3 bucket as a dependency. This causes the template to fail. Update the template with the fix below and it should work for your deployment.
The resource that was failing:
TwitterSentimentCrawler:
Type: AWS::Glue::Crawler
Properties:
DatabaseName: !Ref TwitterSentimentDatabase
Role: !GetAtt GlueCrawlerPermissions.Arn
Description: Crawler to crawl Twitter data
Targets:
S3Targets:
- Path: !Sub s3://${AWS::StackName}-${AWS::AccountId}-${AWS::Region}-twitter/processed/entities/
- Path: !Sub s3://${AWS::StackName}-${AWS::AccountId}-${AWS::Region}-twitter/processed/sentiment/
- Path: !Sub s3://${AWS::StackName}-${AWS::AccountId}-${AWS::Region}-twitter/processed/keyphrases/
RecrawlPolicy:
RecrawlBehavior: CRAWL_NEW_FOLDERS_ONLY
The fix:
TwitterSentimentCrawler:
Type: AWS::Glue::Crawler
Properties:
DatabaseName: !Ref TwitterSentimentDatabase
Role: !GetAtt GlueCrawlerPermissions.Arn
Description: Crawler to crawl Twitter data
Targets:
S3Targets:
- Path: !Sub s3://${TwitterBucket}/processed/entities/
- Path: !Sub s3://${TwitterBucket}/processed/sentiment/
- Path: !Sub s3://${TwitterBucket}/processed/keyphrases/
RecrawlPolicy:
RecrawlBehavior: CRAWL_NEW_FOLDERS_ONLY
回答済み 10ヶ月前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 3ヶ月前
- AWS公式更新しました 1年前
- AWS公式更新しました 3年前