serverless-domain-manager
serverless-domain-manager copied to clipboard
working in region eu-west-3
Hello,
I've been struggling the whole day to deploy my serverless function. I realized that my difficulties were due to the region I was trying to deploy.
Hence my question:
- Is it possible to deploy on eu-west-3 (or anything else different than the default us-east-1)?
It's not clear to me whether the endpointType = edge/regional helps in this topic.
If it's possible (because I haven't managed to), what is the setup to do to get all my data stored in eu-west-3 ? I'm thinking of certificates, and then my serverless.yml. Maybe other stuff ?
For me, in the default us-east-1 it works perfectly. As soon as I pass a region in my serverless.yml and/or I put an endpointType = regional (after having read some threads) but to no avail.
When I do:
- serverless: region: eu-west-3 endpointType: regional
I have at the end:
Error --------------------------------------------------
Error: Error: Unable to get BasePathMappings for staging-serverless-main.***.com
at ServerlessCustomDomain.<anonymous> (/builds/***/main/app/node_modules/serverless-domain-manager/dist/index.js:475:23)
at Generator.throw (<anonymous>)
at rejected (/builds/***/main/app/node_modules/serverless-domain-manager/dist/index.js:5:65)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
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: 13.10.1
Framework Version: 1.65.0
Plugin Version: 3.4.1
SDK Version: 2.3.0
Components Version: 2.22.3
Thanks for your help
Regards,
What is the result of sls create_domain
?
I have similar issues with region not getting automatically resolved from provider-configuration. I could reproduce the issue by removing environment variable AWS_REGION.
Somehow it feels that domain-plugin is now using region set in the serverless.yml provider, but it tries to resolve it from AWS_REGION environment variable. Should it resolve region all cases from provider configuration?
Hi @yeyeric
Hope you have solved this issue.
We are not supporting version 3.x anymore please try our latest version 6.x and let us know in case any issues