InvalidAMIID.NotFound: The image id '[ami-xxxx]' does not exist
The AMI ID isn’t available in this region/account — AMI IDs are regional and private AMIs must be shared.
Seen on:
AWS
Meaning
Copy-pasted AMI IDs from tutorials belong to another region, AMIs get deprecated/deregistered, and private AMIs need explicit sharing (plus KMS key sharing when encrypted).
Common causes
- AMI from another region
- AMI deregistered/deprecated
- Private AMI not shared with this account
- Encrypted AMI whose KMS key isn’t shared
⚡ Quick fix
- Look up the current AMI with SSM public parameters
- Copy the AMI to this region
- Share the AMI (and KMS key) with the account
Detailed fix by platform
AWS CLI
aws ssm get-parameter --name /aws/service/ami-amazon-linux-latest/al2023-ami-kernel-default-x86_64 --region eu-west-1 --query Parameter.Value --output text
How to diagnose
- Region — Same as the AMI?
- Owner — Shared with your account?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AWS.SimpleQueueService.NonExistentQueue SQS: The specified queue does not exist (AWS.SimpleQueueService.NonExistentQueue / QueueDoesNotExist)
- Instance reachability check failed EC2 status check failed: Instance reachability check failed (1/2 checks passed)
- InsufficientInstanceCapacity InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested
Most viewed in AWS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026