lakeformation:GetDataAccess
Literal appearances in AWS managed IAM policies. Statements that use wildcards (for example s3:*) are not counted here. This is not an IAM authorization simulation.
Policies (any)
16
Allow (Action)
15
Deny (Action)
0
NotAction
5
Index generated 5/22/2026, 8:10:29 PM. 562 policies include at least one wildcard action string (any service).
Action reference
SAR-style (unofficial)Service: AWS Lake Formation
Access level
WriteDescription
Grants permission to virtual data lake access
Allow (Action)
- AWSGlueDataBrewServiceRole
- AWSQuicksightAthenaAccess
- AmazonAthenaFullAccess
- AmazonDataZoneEnvironmentRolePermissionsBoundary
- AmazonDataZoneGlueManageAccessRolePolicy
- AmazonDataZoneProjectRolePermissionsBoundary
- AmazonDataZoneSageMakerEnvironmentRolePermissionsBoundary
- AmazonRedshiftServiceLinkedRolePolicy
- SageMakerStudioAdminIAMDefaultExecutionPolicy
- SageMakerStudioAdminIAMPermissiveExecutionPolicy
- SageMakerStudioProjectProvisioningRolePolicy
- SageMakerStudioProjectUserRolePermissionsBoundary
- SageMakerStudioProjectUserRolePolicy
- SageMakerStudioUserIAMDefaultExecutionPolicy
- SageMakerStudioUserIAMPermissiveExecutionPolicy
Deny (Action)
None
Thanks to Ian McKay for iam-dataset (MIT), structured data derived from the AWS Service Authorization Reference. Not maintained by AWS and not guaranteed current. IAMTrail's managed policy archive is separate.
Definitions bundle generated 5/22/2026, 8:10:29 PM