Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(ec2): add SageMaker Interface VPC Endpoint (#31538)
### Issue # (if applicable) None. ### Reason for this change SageMaker Experiments supports private link access but AWS CDK does not support creating an interface VPC endpoint for SageMaker Experiments. ### Description of changes Add Interface VPC Endpoint for AWS SageMaker Experiments. ### Description of how you validated changes I executed the AWS CLI command as shown below. ```sh $ aws ec2 describe-vpc-endpoint-services --filters Name=service-type,Values=Interface Name=owner,Values=amazon --region us-east-1 --query ServiceNames | grep sagemaker "aws.sagemaker.us-east-1.experiments", // added "aws.sagemaker.us-east-1.notebook", "aws.sagemaker.us-east-1.studio", "com.amazonaws.us-east-1.sagemaker.api", "com.amazonaws.us-east-1.sagemaker.featurestore-runtime", "com.amazonaws.us-east-1.sagemaker.metrics", "com.amazonaws.us-east-1.sagemaker.runtime", "com.amazonaws.us-east-1.sagemaker.runtime-fips", ``` ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
- Loading branch information