(aws-apigatewayv2): Specifying HttpMethod.ANY as allowMethod of CORS configuration causes deployment failure.

[acomagu]

new apigatewayv2.HttpApi(this, 'API', {
  corsPreflight: {
    allowMethods: [apigatewayv2.HttpMethod.ANY],
    allowOrigins: ['*'],
    allowHeaders: ['*'],
    maxAge: cdk.Duration.seconds(600),
  },
});

This generates such template:

"APIXXXXXX": {
  "Type": "AWS::ApiGatewayV2::Api",
  "Properties": {
    "CorsConfiguration": {
      "AllowMethods": [
        "ANY"
      ],
      ...

But deploying this fails with the error: Method ANY is not supported (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; ...)

What did you expect to happen?

What actually happened?

The below is correct CloudFormation template:

"APIXXXXXX": {
  "Type": "AWS::ApiGatewayV2::Api",
  "Properties": {
    "CorsConfiguration": {
      "AllowMethods": [
        "*"
      ],
      ...

So the beginning code should generate such YAML.

Environment

• CDK CLI Version:2.0.0-alpha.0 (build beadc66)
• Framework Version: 2.0.0-alpha.0
• Node.js Version: v15.10.0
• OS : Linux acm-envy2-win-wsl 5.4.72-microsoft-standard-WSL2 Initial external release #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 GNU/Linux
• Language (Version): TypeScript 4.2.3

---

This is 🐛 Bug Report

[robertd]

@acomagu Should be addressed by #13313.

[acomagu]

Oh sorry, I didn't notice that.

Thank you for great work! ❤️

[nija-at]

As noted by @robertd, we already have this issue - #13280.

Closing this as a duplicate.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.