No base path mapping is being set

Hello,

First, thanks for your great work on this! It makes a custom domain much easier.

I’m having a problem I can’t figure out. No matter what I put into basePath and stage, no path mapping are showing in the API Gateway custom domain configuration in AWS (and so all requests to the custom domain get 403s).

My configuration is:

custom:
  customDomain:
    domainName: sub.domain.com
    certificateName: domain.com
    basePath: ''
    stage: production
    createRoute53Record: true

The custom domain and route53 dns record properly get made. The only thing is the “base path mappings” are totally blank. I tried putting anything into basePath, such as 'test', but still nothing. If I manually create it in AWS then everything works properly but obviously I don’t want to have to do that.

I’m sorry if I’m missing something obvious and this isn’t urgent. But let me know how I can help debug. And thanks again for sharing this with the community!

[uscheller]

I tried several times, but could not find it anywhere in my update-stack.json

• set basePath to “asdf”
• sls deploy (will return: An error occurred: pathmapping - Only one base path mapping is allowed if the base path is empty)
• When searching for “asdf” in update-stack.json it is not found

[majones-amplify]

Also, in our experience it’s best never to go behind CloudFormation’s back… as more often than not it won’t realize that changes have been made. If you do need to change the base path, I’d recommend removing it with sls remove