aws-samples / aws-samples/sample-kiro-user-analytics-dashboard

deploy.sh fails in step 4 with crawler does not exist error because of missing AWS_REGION in AWS CLI command

Open Beginner friendly
#10 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
40
Forks
10
PR merge metrics
No merged PRs in 30d

Description

Hello,

I tested deployement on my MacBook

I put us-east-1 region in terraform.tfvars file.

While this region is used by Terraform, it is not used by rest of deploy.sh script (no --region in AWS CLI commands).
In my case, I have another default region, so script looked for crawler in the other region and failed with error message below:
```
🕷️ Step 4: Running Glue crawler

aws: [ERROR]: An error occurred (EntityNotFoundException) when calling the StartCrawler operation: Crawler with name kiro-user-report-dashboard-crawler does not exist
```

Solution: add correct --region to AWS CLI commands in deploy.sh or run "export AWS_REGION=xxx" before execution of the deploy.sh script.

Contributor guide

Open the contributing guide

Research direction

Read deploy.sh around step 4 and inspect how the region from terraform.tfvars relates to the AWS CLI commands. Run the deployment with a nonmatching default AWS region, then verify that the Glue crawler lookup uses the intended region and step 4 completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, shell, terraform
Domain
cloud, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
82/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.