1 Answer
- Newest
- Most votes
- Most comments
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
answered 9 months ago
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago