aws-cdk-lib/aws-ec2: Add DynamoDB Streams Endpoint to InterfaceVpcEndpointAwsService Class

[gerrardcowburn]

Describe the feature

DynamoDB launched PrivateLink support for Streams on March 26th. This needs accommodating in the aws-ec2.vpc-endpoint InterfaceVpcEndpointAwsService Class

Use Case

This will help make it easier for customers to adopt DynamoDB Streams with private VPC connectivity using CDK

Proposed Solution

Add `public static readonly DYNAMODB_STREAMS = new InterfaceVpcEndpointAwsService('dynamodb-streams');

Other Information

No response

Acknowledgements

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

AWS CDK Library version (aws-cdk-lib)

v2.195.0

AWS CDK CLI version

2.1016.0

Environment details (OS name and version, etc.)

MacOS

[ykethan]

Hey @gerrardcowburn , thank you for reaching and reporting this. On examining the code in packages/aws-cdk-lib/aws-ec2/lib/vpc-endpoint.ts, we would need to add a new constant for the DynamoDB Streams endpoint. The class currently contains DynamoDB related endpoints such as:

public static readonly DYNAMODB = new InterfaceVpcEndpointAwsService('dynamodb');
public static readonly DYNAMODB_FIPS = new InterfaceVpcEndpointAwsService('dynamodb-fips');

we will need to add a new constant to the InterfaceVpcEndpointAwsService class with the correct configuration:

// In packages/aws-cdk-lib/aws-ec2/lib/vpc-endpoint.ts
public static readonly DYNAMODB_STREAMS = new InterfaceVpcEndpointAwsService('dynamodb-streams');

Workaround

Until this is implemented, users can create the endpoint manually. For example:

const dynamodbStreamsEndpoint = new ec2.InterfaceVpcEndpoint(
  this,
  'DynamoDBStreamsEndpoint',
  {
    vpc,
    service: new InterfaceVpcEndpointAwsService('dynamodb-streams'),
    subnets: { subnetType: ec2.SubnetType.PRIVATE_WITH_EGRESS },
    privateDnsEnabled: false, // DynamoDB Streams doesn't support private DNS
  },
);

Marking this as P2 feature request.
We greatly appreciate community contributions! If you or someone else is interested in implementing this, we'd be happy to review a Pull Request. Please check our contribution guidelines. Meanwhile, welcome to add 👍 to help us prioritize.

[gerrardcowburn]

This has been covered in PR 34483