Cloudformation & API Gateway V2 Errors in Jakarta and Hyderabad regions

Question

I'm setting up a latency based multi-region API stack using Cloudformation which works so far in multiple regions. I've encountered the following error when setting up via the Cloudformation console in Jakarta and Hyderabad.

Template format error: Unrecognized resource types: [AWS::ApiGatewayV2::Stage, AWS::ApiGatewayV2::Authorizer, AWS::ApiGatewayV2::Route, AWS::ApiGatewayV2::ApiMapping, AWS::ApiGatewayV2::DomainName, AWS::ApiGatewayV2::Integration, AWS::ApiGatewayV2::Api]

Does this mean API Gateway V2 is not available in these two regions or not available through Cloudformation? If so does AWS list which regions do not support V2?

FYI: I've used the same cloudformation templates in 9 other regions so far with no issues.

Edit: I'll follow this up with an error I just received in the Osaka region.

Resource handler returned message: "HTTP APIs are not available in this AWS region (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: 405a49e8-*-*-*-adb57d268591; Proxy: null)" (RequestToken: *-*-fd7b-*-7f4e76f0dd79, HandlerErrorCode: GeneralServiceException)

It looks like the error handling for missing functionality is inconsistent?

Accepted Answer

You can find out if a service is available using [Parameter Store public parameters](https://aws.amazon.com/blogs/aws/new-query-for-aws-regions-endpoints-and-more-using-aws-systems-manager-parameter-store/). Something like this:

```
aws ssm get-parameters-by-path \
  --path /aws/service/global-infrastructure/services/apigatewayv2/regions \
  --query Parameters[*].Value
```

Cloudformation & API Gateway V2 Errors in Jakarta and Hyderabad regions

Relevanter Inhalt