AWS managed policies for AWS Glue DataBrew - AWS Glue DataBrew
DataBrew updates to AWS managed policies

AWS managed policies for AWS Glue DataBrew

To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself. It takes time and expertise to create IAM customer managed policies that provide your team with only the permissions they need. To get started quickly, you can use our AWS managed policies. These policies cover common use cases and are available in your AWS account. For more information about AWS managed policies, see AWS managed policies in the IAM User Guide.

AWS services maintain and update AWS managed policies. You can't change the permissions in AWS managed policies. Services occasionally add additional permissions to an AWS managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions.

Additionally, AWS supports managed policies for job functions that span multiple services. For example, the ReadOnlyAccess AWS managed policy provides read-only access to all AWS services and resources. When a service launches a new feature, AWS adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see AWS managed policies for job functions in the IAM User Guide.

DataBrew updates to AWS managed policies

View details about updates to AWS managed policies for DataBrew since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the DataBrew Document history page. The managed policy can be found on the AWS IAM console at AwsGlueDataBrewFullAccessPolicy.

Change Description Date

AWSGlueDataBrewServiceRole – Read permission for AWS Glue was added.

This update adds glue:GetCustomEntityType. This permission is required to execute AWS Glue DataBrew profile jobs with PII-identification enabled.

March 20, 2024

AWSGlueDataBrewServiceRole - Read permission for AWS Glue was added.

This update adds glue:BatchGetCustomEntityTypes. This permission is required to execute AWS Glue DataBrew profile jobs with PII-identification enabled.

May 9, 2022

AwsGlueDataBrewFullAccessPolicy - Read permissions for Amazon Redshift-Data DescribeStatements and Amazon S3 GetLifecycleConfiguration were added.

This update adds redshift-data:DescribeStatement to support validating your SQL when creating an Amazon Redshift-based dataset. It also adds s3:GetLifecycleConfiguration to evaluate whether or not the Amazon S3 bucket prefix you are providing as a temporary directory has the lifecycle configured. Additionally, this change replaces "databrew:*" permissions with an explicit list of permissions including all DataBrew APIs.

February 4, 2022

AwsGlueDataBrewFullAccessPolicy - Read/write permissions for AWS Secrets Manager were added.

This update adds secretsmanager:CreateSecret and secretsmanager:GetSecretValue for a secret named databrew!default, a default secret for use with DataBrew transforms. Additionally, it adds permissions to CreateSecret for secrets prefixed with AwsGlueDataBrew- for creating secrets from the DataBrew console. GenerateRandom, described in the AWS Key Management Service API Reference, is used to generate a random byte string that is cryptographically secure.

November 18, 2021

AWSGlueDataBrewServiceRole - Read/write permissions for AWS Secrets Manager were added.

This update adds secretsmanager:GetSecretValue for a secret named databrew!default, a default secret for use with DataBrew transforms.

November 18, 2021

AwsGlueDataBrewFullAccessPolicy - Read/write permissions for AWS Secrets Manager were added.

This update adds secretsmanager:CreateSecret and secretsmanager:GetSecretValue for a secret named databrew!default, a default secret for use with DataBrew transforms. Additionally, it adds permissions to CreateSecret for secrets prefixed with AwsGlueDataBrew- for creating secrets from the DataBrew console. kms:GenerateRandom (https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateRandom.html) is used to generate a random byte string that is cryptographically secure.

November 18, 2021

AWSGlueDataBrewServiceRole - Read/write permissions for AWS Secrets Manager were added.

This update adds secretsmanager:GetSecretValue for a secret named databrew!default, a default secret for use with DataBrew transforms.

November 18, 2021

AwsGlueDataBrewFullAccessPolicy - Read permissions for AWS Glue catalog databases and create permissions for AWS Glue catalog table were added.

This update adds permissions to list AWS Glue Catalog databases and create new catalog tables under an existing database as part of configuring output to DataBrew jobs.

June 30, 2021

AwsGlueDataBrewFullAccessPolicy - Read/write permissions for Amazon AppFlow dataset feature were added.

This update adds permissions to read existing Amazon AppFlow flows and flow executions and to create flow executions.

April 28, 2021

AwsGlueDataBrewFullAccessPolicy - Read permissions for database datasets were added.

This update adds permissions to read existing AWS Glue connections and create new AWS Glue connections for use with DataBrew.

Also, to make the console experience of creating new connections easier, it allows listing of Amazon VPC resources and Amazon Redshift clusters. It also gives permission to list, but not read, AWS Secrets Manager secrets.

March 30, 2021

DataBrew started tracking changes

DataBrew started tracking changes for its AWS managed policies.

March 30, 2021