feat(ec2): support the new ServiceRegion property for AWS::EC2::VPCEndpoint

[richarddotcodes]

Issue # (if applicable)

Closes #32785

Reason for this change

Supporting the new L1 property in the L2 construct. AWS::EC2::VPCEndpointService support was added in #33959, so this should complete support for cross-region vpc private links.

Description of changes

Added a new L2 prop - serviceRegion - which is of type string. It gets passed to the L1 ServiceRegion property when present.

Describe any new or updated permissions being added

None

Description of how you validated changes

Added unit tests

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

[aws-cdk-automation]

(This review is outdated)

[richarddotcodes]

Clarification request

I believe the failed build is expected since the new snapshot doesn't match the current one.

[richarddotcodes]

Relevant build messages: https://github.com/aws/aws-cdk/actions/runs/16430953967/job/46432096614?pr=35025#step:9:6412

[richarddotcodes]

Exemption request

I believe the failed build is expected since the new snapshot doesn't match the current one. Is anyone able to help?

[Abogical]

Hi @richarddotcodes , Thank you for your contribution!

You are correct that the build fails due to integration test snapshots not being updated. However, this change should be done and committed on this PR.

If you can, follow this guide to run and update the integration snapshots, which suggests to run the following to update the snapshots:

yarn integ-runner --directory packages/@aws-cdk --update-on-failed

The snapshots will then be updated. Commit those changes once this is done.

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

[richarddotcodes]

@Abogical Thanks for the help! I've submitted the snapshot changes and the build is now passing.

Pull request has been modified.

[Abogical]

Thank you!

[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).

[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.

[Abogical]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/request-cli-integ-test.yml without workflows permission

[Abogical]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 522c588
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[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.