Amazon SageMaker Now Supports More Refined Access Control using Amazon SageMaker-specific Condition Keys
Amazon SageMaker now enables better control and access using Amazon SageMaker-specific condition keys. You can use these new keys in the Condition element of an Identity and Access Management (IAM) policy to further refine the conditions under which the policy statement applies.
Amazon SageMaker now enables better control and access using Amazon SageMaker-specific condition keys. You can use these new keys in the Condition element of an Identity and Access Management (IAM) policy to further refine the conditions under which the policy statement applies.
You can use Amazon SageMaker-specific condition keys to enforce best practices and compliance requirements. This includes encryption of data, encryption of storage volumes, network isolation, and controlled access to Amazon SageMaker resources. You can also enforce SageMaker resources to a specific Virtual Private Cloud (VPC) and disable Notebook Instance root access and internet access. Additionally, you can restrict the instance types that users can select when using SageMaker to manage costs.
This new feature is now available in a total of 18 AWS regions around the world. Visit the Amazon SageMaker developer guide and the AWS Identity and Access Management developer guide for more information.