feat(ec2): add BEDROCK_AGENTCORE and BEDROCK_AGENTCORE_GATEWAY to InterfaceVpcEndpointAwsService

[tbrand]

AgentCore's VPC Endpoint support announced on Sep 25, 2025 was announced. The service names bedrock-agentcore and bedrock-agentcore.gateway mentioned in this document have been added to InterfaceVpcEndpointAwsService.

Reason for this change

New VPC Endpoints exist now.

Description of changes

Add the missing constants.

Describe any new or updated permissions being added

None.

Description of how you validated changes

The following code works as expected.

// Deploy on us-east-1
import * as cdk from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as ec2 from 'aws-cdk-lib/aws-ec2';

export class VpcEndpointTestStack extends cdk.Stack {
  constructor(scope: Construct, id: string, props?: cdk.StackProps) {
    super(scope, id, props);

    const vpc = new ec2.Vpc(this, 'Vpc', {
      availabilityZones: [
        'us-east-1a',
        'us-east-1c',
        'us-east-1d',
      ],
    });

    // AgentCore
    new ec2.InterfaceVpcEndpoint(this, 'AgentCore', {
      vpc,
      service: ec2.InterfaceVpcEndpointAwsService.BEDROCK_AGENTCORE,
    });

    // AgentCore Gateway
    new ec2.InterfaceVpcEndpoint(this, 'AgentCoreGateway', {
      vpc,
      service: ec2.InterfaceVpcEndpointAwsService.BEDROCK_AGENTCORE_GATEWAY,
    });
  }
}

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Yes, and I am an AWS employee.

[aws-cdk-automation]

(This review is outdated)

[tbrand]

I created this in the same way as this PR, so my understanding is that testing and documentation support are not necessary in the same manner.

[badmintoncryer]

@tbrand Thank you for your contribution. Could you please add a comment Exemption Request to pass all CI processes?

[tbrand]

Exemption Request

[badmintoncryer]

@tbrand Could you please update PR title? The 'needs-maintainer-review' label will be attached after that.

[tbrand]

Thanks @badmintoncryer. How should I update the title specifically?

[badmintoncryer]

As long as it’s updated, it’s fine. I think it’s okay to make some changes and then revert to the current title afterward!

[tbrand]

Got it. I upated and reverted it.

[badmintoncryer]

I’m not sure why, but it seems the build CI hasn’t been triggered.
It’s a simple change, so I believe a maintainer will approve it soon. Please wait a little while.

[alvazjor]

Thanks for the contribution

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Pull request has been modified.

Pull request has been modified.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.