AWS::EC2::VPCEndpoint - ExistingAttribute-NewProperty - Tag Property for Resource

[tope-oyenuga]

1. Title -> AWS::EC2::VPCEndpoint-ExistingAttribute-NewProperty - Tag Property for Resource
2. Scope of request -> AWS::EC2::VPCEndpoint doesn't currently include the tag property. But the API includes this property.
3. Expected behavior -> In Create, it should include an ability to tag a VPC endpoint, like the console & API allows.
4. Links to existing API doc -> https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVpcEndpoint.html#API_CreateVpcEndpoint_RequestParameters
5. Category tag -> Compute
6. Any additional context

[pplu]

Was just going to open the same ticket due to not being able to tag Endpoints from CloudFormation. It's very hard to distinguish them when you have dozens, created by different stacks.

[hauntingEcho]

It looks like those tags aren't handled by any path in CFN - #196

[seemantk-schweitzer]

Hello,

Given how much AWS docs talk about Tags this is a rather unexpected omission. Honestly, one thinks that Tags would be a standard thing on all Resources. Can y'all help us understand why they aren't supported here, and what the effort is to address that?

Thank you,
Seemant

[Caesonia]

Definitely missing this item in Cloudformation. I try and keep my templates as simple as possible. The workarounds suggested are adding a lot of complexity. In the shorter term, it will be manually done until the CI/CD is updated and the CLI does it. I don't like doing stuff like that.