[aws-ec2] Interface endpoints are incorrect in China

We are trying to create a VPC endpoint to ECR in china region (cn-north-1).

The service that comes back when running the code below is “com.amazonaws.cn-north-1.ecr.dkr”. However upon looking at aws console when manually adding a vpc ecr endpoint the service name is “cn.com.amazonaws.cn-north-1.ecr.dkr”.

As a result of the incorrect service name cloudformation throws an error stating it can’t find the service/it does not exist.

Reproduction Steps

ecr_endpoint = self.vpc.add_interface_endpoint("%s-ECREndpoint" % namespace, service= ec2.InterfaceVpcEndpointAwsService.ECR_DOCKER)

What did you expect to happen?

The right service name to be returned “cn.com.amazonaws.cn-north-1.ecr.dkr”

What actually happened?

The wrong service name came back “com.amazonaws.cn-north-1.ecr.dkr”. As a result cloudformation cannot create the vpc endpoint

Environment

• CLI Version : 1.54.0 (build c01b9b9)
• Framework Version:
• Node.js Version: v12.18.3
• OS : mac
• Language (Version): Python (3.7.3)

Other

---

This is 🐛 Bug Report

[ZeBidule]

Hi, I have the same issue with the terraform data aws_vpc_endpoint_service in china :

Code

provider "aws" {
  region  = "cn-north-1"
  profile = "china"
}

data "aws_vpc_endpoint_service" "sqs" {
  service = "sqs"
}

output "sqs_endpoint_service" {
  value = data.aws_vpc_endpoint_service.sqs
}

Output

> terraform apply                                                          
data.aws_vpc_endpoint_service.sqs: Refreshing state...

Error: error reading VPC Endpoint Service (com.amazonaws.cn-north-1.sqs): InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.cn-north-1.sqs' does not exist
        status code: 400, request id: 5fb025e4-5aa5-4ba1-975e-055c98d66830

Expected result

cn.com.amazonaws.cn-north-1.sts

[github-actions[bot]]

⚠️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.