-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to select Security Group for existing VPC in config. step #512
Comments
Thanks @massi-ang. I tried with commenting out the last VPC component. It gave me a different error, with route tables this time:
|
Can you please provide some more information about what modification you did? Ideally, can you provide a forked repo with your modifications so that it is simpler to reproduce the error |
Hi @massi-ang,
Thank you for your continued guidance! |
This issue is stale because it has been open for 60 days with no activity. |
Enterprise customer doesn't allow
PRIVATE_ISOLATED
for ec2 SubnetType in their AWS account. So, need to pick the security group available in the existing VPC during the config step of deployment (Step 4), after changingPRIVATE_ISOLATED
toPRIVATE_WITH_EGRESS
in .ts files.Facing following error during deployment:
validation error detected: Value '[]' at 'vpcConfig.securityGroupIds' failed to satisfy constraint: Member must have length greater than or equal to 1 (Service: AmazonSageMaker; Status Code: 400; Error Code: ValidationException; Request ID: 0c2cdffd-07dc-4139-9f1c-3b9f4169c6aa...
The text was updated successfully, but these errors were encountered: