Missing AWS::EC2::VPCEndpointService ResourceType in CloudFormationResourceSpecification.json for Most Regions

[ScriptAutomate]

The AWS::EC2::VPCEndpointService is missing from most of the CloudFormationResourceSpecification.json files.

It only exists within the following spec files: eu-north-1, ap-northeast-3, ap-east-1, cn-north-1, cn-northwest-1

This will mean it will be left out if any automation tools are referring to us-east-1 as a master file for module / code generation.

"AWS::EC2::VPCEndpointService": {
  "Documentation": "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcendpointservice.html",
  "Properties": {
    "AcceptanceRequired": {
      "Documentation": "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcendpointservice.html#cfn-ec2-vpcendpointservice-acceptancerequired",
      "PrimitiveType": "Boolean",
      "Required": false,
      "UpdateType": "Mutable"
    },
    "NetworkLoadBalancerArns": {
      "Documentation": "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcendpointservice.html#cfn-ec2-vpcendpointservice-networkloadbalancerarns",
      "PrimitiveItemType": "String",
      "Required": true,
      "Type": "List",
      "UpdateType": "Mutable"
    }
  }
}

[PatMyron]

AWS PrivateLink is available in these AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), GovCloud (US-West), US West (N. California), EU (London), EU (Ireland), EU (Frankfurt), EU (Paris), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), South America (São Paulo), China (Beijing), operated by Sinnet, and China (Ningxia), operated by Ningxia Western Cloud Data Technology Co. Ltd. (NWCD).

CloudFormation support for AWS PrivateLink is available in US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), EU (Frankfurt), EU (Ireland), EU (London), and South America (Sao Paulo) Regions.

AWS PrivateLink only in the AWS GovCloud regions in the Region Table

AWS PrivateLink pricing pages show every region except Paris (Chinese pricing page)

[PatMyron]

Able to successfully create AWS::EC2::VPCEndpoint in us-east-1 with this template:

Resources:
  VPCEndpoint:
    Type: AWS::EC2::VPCEndpoint
    Properties:
      ServiceName: com.amazonaws.us-east-1.s3
      VpcId: !Ref VPC
  VPC:
    Type: AWS::EC2::VPC
    Properties: 
      CidrBlock: 10.0.0.0/16

AWS::EC2::VPCEndpoint is in the us-east-1 resource specification

[ScriptAutomate]

@PatMyron - AWS::EC2::VPCEndpoint is there but not AWS::EC2::VPCEndpointService

• AWS::EC2::VPCEndpoint
• AWS::EC2::VPCEndpointService

[PatMyron]

Good catch, I was suspicious about it making its way into the resource spec since your last run here

Able to create AWS::EC2::VPCEndpointService in us-east-1 as well with this template:

Resources:
  VPCEndpointService:
    Type: AWS::EC2::VPCEndpointService
    Properties:
      NetworkLoadBalancerArns:
        - !Ref LoadBalancer
  LoadBalancer:
    DependsOn: VPCGatewayAttachment
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    Properties:
      Type: network
      Subnets:
        - !Ref Subnet
  Subnet:
    Type: AWS::EC2::Subnet
    Properties:
      VpcId: !Ref VPC
      CidrBlock: 10.0.0.0/16
  VPC:
    Type: AWS::EC2::VPC
    Properties: 
      CidrBlock: 10.0.0.0/16
  InternetGateway:
    Type: AWS::EC2::InternetGateway
  VPCGatewayAttachment:
    Type: AWS::EC2::VPCGatewayAttachment
    Properties:
      VpcId: !Ref VPC
      InternetGatewayId: !Ref InternetGateway

[PatMyron]

AWS::EC2::VPCEndpointService is now in the us-east-1 resource specification

[ScriptAutomate]

Mission complete!