Skip to content

update SCP/PreventNonVPCDeploymentSageMaker #30

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

Merged

Conversation

ach-mk
Copy link
Contributor

@ach-mk ach-mk commented Feb 24, 2025

As described in the service authorization reference for Amazon SageMaker the following IAM actions support the condition key sagemaker:VpcSubnets:

  • sagemaker:CreateAutoMLJob
  • sagemaker:CreateAutoMLJobV2
  • sagemaker:CreateDataQualityJobDefinition
  • sagemaker:CreateDomain
  • sagemaker:CreateHyperParameterTuningJob
  • sagemaker:CreateModel
  • sagemaker:CreateModelBiasJobDefinition
  • sagemaker:CreateModelExplainabilityJobDefinition
  • sagemaker:CreateModelQualityJobDefinition
  • sagemaker:CreateMonitoringSchedule
  • sagemaker:CreateNotebookInstance
  • sagemaker:CreateProcessingJob
  • sagemaker:CreateTrainingJob
  • sagemaker:UpdateDomain
  • sagemaker:UpdateMonitoringSchedule

The objective of this pull request is to align the SCP data_perimeter_governance_policy_2.json with this list of actions.
These actions have been tested to verify their compatibility with the condition key.

@liwadman liwadman merged commit 05e750e into aws-samples:main Feb 24, 2025
1 check failed
@liwadman
Copy link
Contributor

-Policy Lints
-Trusted submitter self-attesting to testing correctness
-Service authorization reference checks out.

LGTM, Ship it!

@liwadman liwadman self-assigned this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants