AWS::EC2::VPCEndpoint - Tags

[farski]

Add support for tags on AWS::EC2::VPCEndpoint resources

[AlbertZakharov]

+1

[gazzoy]

+1

[mattyboy84]

+1 How isn't this supported?

[adam-intel]

+1 Please add this feature

[dkAnBlWo]

+1

[seabyrn]

+1. IMO tag support should be table stakes for CFN resources.

[maherrj]

+1 Cost allocation tags are critical to us. VPC Endpoints have a non trivial cost, so really keen for this support so we can attribute cost correctly.

[koDaegon]

+1

[xWink]

Hi everyone, thank you for your patience! It's with great pleasure that I can say we are actively working on adding support for tagging VPC Endpoints, alongside supporting many other PrivateLink API features. Please keep your eyes peeled, as we'll provide more updates on our progress here!

[revamp-muto-kotaro]

This is The Best News of 2024 for me!

[takeda]

Judging on overall attention to such simple change and the age of the ticket I say this will also be best news of 2025 and 2026.

[ysa23]

+1

[minhio]

Judging on overall attention to such simple change and the age of the ticket I say this will also be best news of 2025 and 2026.

i just want to comment so i can come back here in a couple years

[princewadhwa]

+1

[craigbosco]

Definitely need this and much anticipating the update. Thank you!

[shaikegross]

Please release soon we want this 🙏

[tomdionysus]

Still an issue, please fix. CloudFormation doesn't support Tags in the resource, but it can be manually tagged.

[shendriksen]

+1

[nemeth]

+1

[tcmnal]

+1

[ThomasSteinbach]

What's so difficult on this?

[ryanwilliams83]

I deployed six more yesterday, and used this work-around in CDK to add the tags.

// import { AwsCustomResource, AwsCustomResourcePolicy, PhysicalResourceId } from 'aws-cdk-lib/custom-resources';

  new AwsCustomResource(this, 'VpcEndpointTags', {
    installLatestAwsSdk: false,
    onUpdate: {
      action: 'createTags',
      parameters: {
        Resources: [
          vpcEndpoint.vpcEndpointId
        ],
        Tags: [
          {
            Key: 'Name',
            Value: 'Cookie Monster'
          }
        ]
      },
      physicalResourceId: PhysicalResourceId.of(Date.now().toString()),
        service: 'EC2'
      },
      policy: AwsCustomResourcePolicy.fromSdkCalls({
        resources: AwsCustomResourcePolicy.ANY_RESOURCE,
      })
  });

[estanqueiroa]

+1

[Cumming5412]

+1

[davidgatti]

2024...

[kose-yusuke-ochi]

リリースされることを待望しております よろしくお願いいたします！

[mmieluch]

5 years for simple tagging support. This is ridiculous.

[m1g0r]

+1, сost allocation tags are very necessary for us

[estanqueiroa]

in the meantime, please check my github repo for a solution using lambda /awscode/cloudformation/vpc-endpoints-tags

[koen-venly]

Half of 2024... Jesus... It's just tags...

While in Terraform land... These are the things that make me wish I went the Terraform way... CloudFormation... AWS's own product, in their own environment... In something that they emphasize... Nope... to hard...

resource "aws_vpc_endpoint" "s3" {
  vpc_id       = aws_vpc.main.id
  service_name = "com.amazonaws.us-west-2.s3"

  tags = {
    Environment = "test"
  }
}

[SonyDavid]

Please add this

[amouly]

Any update?