serverless-domain-manager Deploying REGIONAL api fails with with error: BadRequestException: Only REGIONAL domain names can be managed through the API Gateway V2 API.

Deploying REGIONAL api fails with with error: BadRequestException: Only REGIONAL domain names can be managed through the API Gateway V2 API.

Open navrkald opened this issue 4 years ago • 3 comments

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 When deploying regional api with version serverless-domain-manager 5.1.0 it fails with error:

Only REGIONAL domain names can be managed through the API Gateway V2 API

However the version [email protected] is working correctly.

The error was also mentioned in #359.

Command Run sls deploy

Console Output

Serverless Domain Manager: Error: cenzored.domain.com:  BadRequestException: Only REGIONAL domain names can be managed through the API Gateway V2 API. For EDGE domain names, please use the API Gateway V1 API. Also note that only REST APIs can be attached to EDGE domain names.
Serverless Domain Manager: Error: cenzored.domain.com:  Error: cenzored.domain.com: Unable to update basepath mapping.

Domain Manager Configuration

  customDomain:
    domainName: cenzored.domain.com
    basePath: 'censoredBasePath'
    stage: ${self:provider.stage}
    createRoute53Record: false
    certificateName: '*.domain.com'
    endpointType: 'regional'

Versions

Domain Manager version(s): [5.1.0]
Node/npm version: [v12.18.3]
Serverless Version: [2.13.0]
Lambda Code [Typescript]

Possible Solution Pls compare what was changed between versions 3.3.0 and 5.1.0 and found out what change has broken creating regional API.

Dec 01 '20 13:12 navrkald

In my case, the error was due to an upgrade from TLS 1.0 to 1.2. As a workaround until it's fixed, you can change the Custom domain to TLS 1.2 manually in AWS console or CLI and you're good to go.