You must specify a region. You can also configure your region by running "aws configure" (NoRegionError)
No region is configured for the CLI/SDK call.
You must specify a regionRegion is missingConfigError: Missing region in config Meaning
The region comes from --region, AWS_REGION/AWS_DEFAULT_REGION, or the profile in ~/.aws/config. CI jobs, containers and new profiles often lack it. SDKs raise NoRegionError / “Region is missing”.
Common causes
- Profile without region
- No AWS_REGION in CI/container
- Using a named profile but region set only on default
⚡ Quick fix
- Pass --region or set AWS_REGION
- aws configure set region eu-west-1 --profile name
- Set region in SDK client constructors
Detailed fix by platform
Shell
- bash
aws configure set region eu-west-1 --profile prod export AWS_REGION=eu-west-1
How to diagnose
- Sources — aws configure list
- Profile — Which profile is active?
🔧 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
Most viewed in AWS
- SignatureDoesNotMatch AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
- NoSuchKey AWS S3: NoSuchKey / NoSuchBucket — The specified key/bucket does not exist
- Runtime.ImportModuleError Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'x'
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 12 Oct 2026