(ec2): Get ARN for VPC

[chelproc]

Use Case

PolicyStatement

const role = new Role(this, 'AcceptVpcPeeringRole', {
  assumedBy: new AccountPrincipal('********'),
});
const vpcArn = `arn:aws:ec2:${vpc.env.region}:${vpc.env.account}:vpc/${vpc.vpcId}`;
role.addToPolicy(
  new PolicyStatement({
    resources: [vpcArn],
    actions: ['ec2:AcceptVpcPeeringConnection'],
  }),
);
role.addToPolicy(
  new PolicyStatement({
    resources: ['*'],
    conditions: { StringEquals: { 'ec2:AccepterVpc': vpcArn } },
    actions: ['ec2:AcceptVpcPeeringConnection'],
  }),
);

Proposed Solution

Add vpcArn property for Vpc construct.

const vpc = new Vpc(self, 'Vpc');
// `arn:aws:ec2:${vpc.env.region}:${vpc.env.account}:vpc/${vpc.vpcId}`
vpc.vpcArn;

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[njlynch]

Thanks for this feature request. I can certainly see the use case, and it would be simple enough to add.

As an implementation note, using Arn.format would auto-detect several of those components and make it a bit easier, including handling partitions (which often is forgotten about).

We welcome community contributions! If you are able, we encourage you to contribute.

[github-actions]

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