Jakarta forced to use APIGatewayV2 for REGIONAL TLS 1.2

[Daniel Poon]

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

Hi,

Continuing this issue (#536), it seems that Jakarta does not support APIGatewayV2 yet.

The fix (#537) only applies to EDGE and TLS 1.0. However I would like to deploy a REGIONAL TLS 1.2 custom domain.

I have manually verified that this combination can be created through the AWS Console. The current identification mechanism to switch to APIGatewayV1 might not cover all valid cases. If Jakarta is known to not support APIGatewayV2 should we just toggle to APIGatewayV1 based on the ap-southeast-3 region?

Command Run
sls deploy

Console Output

Error: V2 - Unable to fetch information about '{domain}':
Bad Request
    at APIGatewayV2Wrapper.<anonymous> ({path}/node_modules/serverless-domain-manager/dist/src/aws/api-gateway-v2-wrapper.js:71:27)
    at Generator.throw (<anonymous>)
    at rejected ({path}/node_modules/serverless-domain-manager/dist/src/aws/api-gateway-v2-wrapper.js:6:65)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Exited with code exit status 1

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

custom:
  customDomain:
    enabled: true
    domainName: {domain}
    certificateArn: {arn}
    createRoute53Record: false
    createRoute53IPv6Record: false
    endpointType: regional
    securityPolicy: tls_1_2
    apiType: rest
    autoDomain: true

Versions

• Domain Manager version(s): 6.4.1
• Node/npm version: 16.13.1/8.1.2
• Serverless Version: 3.26.0
• Lambda Code: Go

Possible Solution
If Jakarta is known to not support APIGatewayV2 should we just toggle to APIGatewayV1 based on the ap-southeast-3 region?

Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.