aws Errors
25 error patterns
Lambda Cold Start Timeout
Lambda cold start duration exceeded (\d+)ms
- •Enable provisioned concurrency
- •Reduce deployment package size
Lambda Function Timeout
Task timed out after (\d+\.\d+) seconds
- •Increase timeout in Lambda configuration
- •Optimize function code to reduce execution time
API Gateway Integration Timeout
Endpoint request timed out
- •Increase API Gateway timeout (max 29s)
- •Implement async pattern with SQS
DynamoDB Throughput Exceeded
ProvisionedThroughputExceededException
- •Enable auto-scaling on the table
- •Switch to on-demand capacity mode
S3 Access Denied
AccessDenied.*S3
- •Check bucket policy allows the IAM role
- •Verify object ACL permissions
CloudFormation Stack Rollback
UPDATE_ROLLBACK_COMPLETE|ROLLBACK_IN_PROGRESS
- •Check CloudFormation events for root cause
- •Fix the failing resource and redeploy
ECS Essential Container Failure
Essential container in task exited
- •Check container logs in CloudWatch
- •Verify health check configuration
RDS Connection Failure
Communications link failure.*RDS
- •Check security group inbound rules for DB port
- •Verify RDS instance is accessible from your VPC
SQS Visibility Timeout Expired
Message not visible, VisibilityTimeout expired
- •Increase visibility timeout to match processing time
- •Call ChangeMessageVisibility for long-running tasks
SNS Delivery Failure - Endpoint Disabled
SNS delivery failed.*EndpointDisabled
- •Re-enable the subscription endpoint
- •Implement dead-letter queue for failed deliveries
IAM Policy Deny - No Identity Policy
is not authorized to perform.*because no identity-based policy
- •Attach required IAM policy to the user/role
- •Use IAM Policy Simulator to debug permissions
Lambda Runtime Exit Error
Runtime\.ExitError
- •Check for unhandled exceptions in handler
- •Verify runtime compatibility with package
API Gateway Rate Limit Exceeded
429.*Too Many Requests.*API Gateway
- •Request throttle limit increase via Support
- •Implement retry with exponential backoff
DynamoDB Conditional Check Failed
ConditionalCheckFailedException
- •Review condition expression logic
- •Implement optimistic locking with version attribute
S3 Object Not Found
NoSuchKey.*The specified key does not exist
- •Verify the object key path and bucket name
- •Check if object was lifecycle-expired
CloudFormation Resource Creation Failed
CREATE_FAILED.*Resource handler returned message
- •Read the StatusReason in stack events
- •Validate template with cfn validate-template
ECS Cannot Pull Container Image
CannotPullContainerError
- •Verify ECR repository and image tag exist
- •Check task execution role has ecr:GetAuthorizationToken
RDS Max Connections Exceeded
too many connections.*RDS
- •Use RDS Proxy to pool connections
- •Increase max_connections in parameter group
SQS Invalid Message Body
InvalidParameterValue.*MessageBody
- •Ensure message body is valid UTF-8
- •Use SQS Extended Client for messages over 256KB
IAM Access Denied Exception
An error occurred \(AccessDeniedException\).*not authorized
- •Check for explicit Deny statements in policies
- •Verify resource-based policy allows cross-account
AWS Access Denied
AccessDenied|Access Denied|not authorized to perform|UnauthorizedAccess
- •Check IAM policy — use `aws sts get-caller-identity` to verify which role/user is being used
- •Add the required permission to the IAM policy and wait 1-2 minutes for propagation
AWS Region Not Configured
Missing region|could not determine region|Region .* not set|must specify a region
- •Set the region via environment variable: `export AWS_DEFAULT_REGION=us-east-1`
- •Add region to your AWS config: `aws configure set region us-east-1`
AWS Credentials Not Found or Expired
Unable to locate credentials|NoCredentialProviders|credential.*not found|ExpiredTokenException
- •Run `aws configure` to set up credentials or check `~/.aws/credentials` file exists
- •If using SSO, run `aws sso login --profile your-profile` to refresh the session
S3 Bucket Not Found
NoSuchBucket|The specified bucket does not exist|bucket.*not found
- •Verify the bucket name — S3 names are globally unique and case-sensitive (must be lowercase)
- •Check you're using the correct AWS account and region for the bucket
AWS Lambda Timeout
Task timed out after|Lambda.*timeout|execution timed out
- •Increase the timeout setting in the Lambda configuration (max 900 seconds)
- •Optimize cold start — reduce package size, use provisioned concurrency, or use ARM architecture