Troubleshooting
Fix common AWS deployment issues.
AWS Troubleshooting
"Access Denied" on Bedrock
- Verify model access in the Bedrock Console
- Check IAM policy includes
bedrock:InvokeModel:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["bedrock:InvokeModel"],
"Resource": "*"
}
]
}
- Ensure the model ID in config matches an accessible model
"ResourceNotFoundException" on DynamoDB
The table doesn't exist or is in a different region:
aws dynamodb describe-table --table-name docket --region us-east-1
"Queue does not exist" on SQS
Verify the queue URL:
aws sqs get-queue-url --queue-name docket-jobs
Slow Bedrock responses
- Use a model in your closest region
- Reduce
maxTokensto limit generation time - Enable response streaming (future feature)
DynamoDB throttling
You're exceeding provisioned capacity:
- Switch to on-demand billing
- Or increase provisioned RCU/WCU
- Or add exponential backoff in your client
S3 "NoSuchBucket"
Bucket name is globally unique. If you get this error:
- Check the exact bucket name in config
- Verify the bucket exists:
aws s3 ls s3://your-bucket - Ensure the region in config matches the bucket region
High latency from outside AWS
If users are far from your AWS region:
- Deploy Docket closer to users (multi-region)
- Use CloudFront for S3 content
- Consider Cloudflare R2 for zero-egress blob storage