You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The SageMaker Notebook Interface VPC Endpoint does not deploy. The service name is incorrect.
When deploying I receive the following error
The Vpc Endpoint Service 'aws.sagemaker.us-west-2.sagemaker' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidServiceName; Request ID: bb11fb4a-b775-49b3-958c-f75cc8dcd63c)
Tested the changes and the recommended change to line 208 of file aws-cdk/packages/@aws-cdk/aws-ec2/lib/vpc-endpoint.ts deployed the endpoint successfully.
Describe the bug
The SageMaker Notebook Interface VPC Endpoint does not deploy. The service name is incorrect.
When deploying I receive the following error
The Vpc Endpoint Service 'aws.sagemaker.us-west-2.sagemaker' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidServiceName; Request ID: bb11fb4a-b775-49b3-958c-f75cc8dcd63c)
To Reproduce
Create directory SagemakerWorkflow
cd SagemakerWorkflow
cdk init --language typescript
below is the sagemaker_workflow-stack.ts file
import cdk = require('@aws-cdk/cdk');
import ec2 = require('@aws-cdk/aws-ec2');
export class SagemakerWorkflowStack extends cdk.Stack {
constructor(scope: cdk.Construct, id: string, props?: cdk.StackProps) {
super(scope, id, props);
const vpc = new ec2.VpcNetwork(this, 'sagemakerVpc', {
maxAZs: 2,
natGateways: 1,
gatewayEndpoints: {
S3: {
service: ec2.GatewayVpcEndpointAwsService.S3
}
}
});
const sageMakerNotebookEndpoint = vpc.addInterfaceEndpoint('sageMakerNotebookEndpoint', {
service: ec2.InterfaceVpcEndpointAwsService.SageMakerNotebook
});
sageMakerNotebookEndpoint.connections.allowDefaultPortFromAnyIpv4();
}
}
Expected behavior
When creating a SageMaker Notebook Interface VPC Endpoint, it should deploy
Version:
The text was updated successfully, but these errors were encountered: