Docket Docs

Troubleshooting

Fix common AWS deployment issues.

AWS Troubleshooting

"Access Denied" on Bedrock

  1. Verify model access in the Bedrock Console
  2. Check IAM policy includes bedrock:InvokeModel:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["bedrock:InvokeModel"],
      "Resource": "*"
    }
  ]
}
  1. 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 maxTokens to limit generation time
  • Enable response streaming (future feature)

DynamoDB throttling

You're exceeding provisioned capacity:

  1. Switch to on-demand billing
  2. Or increase provisioned RCU/WCU
  3. Or add exponential backoff in your client

S3 "NoSuchBucket"

Bucket name is globally unique. If you get this error:

  1. Check the exact bucket name in config
  2. Verify the bucket exists: aws s3 ls s3://your-bucket
  3. Ensure the region in config matches the bucket region

High latency from outside AWS

If users are far from your AWS region:

  1. Deploy Docket closer to users (multi-region)
  2. Use CloudFront for S3 content
  3. Consider Cloudflare R2 for zero-egress blob storage

On this page