serverless-domain-manager: serverless create-domain results in "unable to create domain..." no matter what domain was supplied.

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

Error Description Running the command, “serverless create-domain” results in “unable to create domain…” no matter what domain was supplied.

Command Run sls create_domain

Console Output Error --------------------------------------------------

Error: Error: Unable to create domain api.highmynameis.com at ServerlessCustomDomain.<anonymous> (/Users/charvey/Dev/ucann-rest/hmni-serverless/node_modules/serverless-domain-manager/dist/index.js:80:27) at Generator.throw (<anonymous>) at rejected (/Users/charvey/Dev/ucann-rest/hmni-serverless/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: darwin Node Version: 12.16.1 Framework Version: 1.71.3 Plugin Version: 3.6.12 SDK Version: 2.3.1 Components Version: 2.30.11

Domain Manager Configuration Replace this with your own serverless.yml file (anonymized, of course) to help us better resolve your issue.

custom:
  customDomain:
    domainName: api.{goDaddy domain}.com
    basepath: api
    createRoute53Record: false

Versions

Node/npm version: Node 12/npm 6.14.5
Serverless Version: v1.71.1
Lambda Code: Javascript

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 28
Comments: 16

Most upvoted comments

I had the same issue but adding the certificateArn explicitly worked for me.

leoalbin on Jul 30, 2020

echoing with https://github.com/sharmashobhit

the 2 key elements in case you generated certificates with wilcards

certificateName: "*.domain.com"
hostedZoneId: ${opt:HOSTED_ZONE_ID}

devadyuti on Nov 10, 2020

Was struggling with this. The following seemed to work for me.

The certificate I was using was in a different region
Provided the hostedZoneId to the configuration. This ensures explicit discovery.

custom:
  customDomain:
    domainName: api.domain.com
    basePath: api
    certificateName: *.domain.com,
    hostedZoneId: <hostedZoneId>
    createRoute53Record: true
    endpointType: regional
    securityPolicy: tls_1_2
    apiType: rest

sharmashobhit on Jul 14, 2020