serverless-domain-manager: ConfigError: Missing region in config
Community Note
- Please vote on this issue by adding a π reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave β+1β or βme tooβ comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Bug Report
We have a deployment that relies on serverless-domain-manager which has worked happily for 2 years and then suddenly stopped. It is run locally and remotely on BitBucket Pipelines, which is where we see the failure. Has something changed about the handling of regions? Needless-to-say the region is defined in the serverless configuration.
provider:
name: aws
runtime: nodejs12.x
region: eu-west-2
tracing: true
>> serverless create_domain -s staging
Error --------------------------------------------------
Error: Error: 'www.mysite.world' was not created in API Gateway.
ConfigError: Missing region in config
at createDomainName.catch (/opt/atlassian/pipelines/agent/build/node_modules/serverless-domain-manager/index.js:108:15)
at <anonymous>
at process._tickDomainCallback (internal/process/next_tick.js:229:7)
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information ---------------------------
Operating System: linux
Node Version: 8.17.0
Framework Version: 1.61.2
Plugin Version: 3.2.7
SDK Version: 2.2.1
Components Core Version: 1.1.2
Components CLI Version: 1.4.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 24
- Comments: 23 (1 by maintainers)
Just encountered the same issue.
Got it fixed by bumping from
3.2.2
to3.3.2
.same here. bumping to 3.3.1 solved issue OS: MacOS 10.15.2
I just barely updated to v3.3.1 and it is working for me. @spotnape can you check if the latest version fix your issue?
Thanks @medikoo
AWS_REGION is missing in env.local causing issue on service like s3 getting used in the project.