add: PreventNonVpcOnlySageMakerDomain #32
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The objective of this PR is to add the SCP statement
PreventNonVpcOnlySageMakerDomainto data_perimeter_governance_policy_2.json.The statement
PreventNonVpcOnlySageMakerDomainprevents users from creating and updating Amazon SageMaker domains that have non-EFS traffic going through a VPC managed by SageMaker instead of your VPC. By configuring your domains to route traffic through your VPC, you can inspect requests by using VPC endpoint policies (against identity and resource perimeter controls) and enforce the network perimeter.For more details, see the definition of the parameter
AppNetworkAccessTypein the Amazon SageMaker API Reference.