AWS managedservices documentation change
Summary
Updated role deployment process with specific change type requirements
Security assessment
Clarifies access control procedures for Lake Formation but shows no evidence of addressing existing vulnerabilities. Improves security documentation around permission management.
Diff
diff --git a/managedservices/latest/onboardingguide/lake-formation.md b/managedservices/latest/onboardingguide/lake-formation.md index 973dd9721..7aab028a9 100644 --- a//managedservices/latest/onboardingguide/lake-formation.md +++ b//managedservices/latest/onboardingguide/lake-formation.md @@ -32 +32 @@ For admin permissions, you can choose to onboard the role `customer_lakeformatio -If you want to create Blueprints in the AWS Lake Formation Console, you need to submit a Management | Other | Other RFC (ct-1e1xtak34nx76) to deploy the `customer_lakeformation_workflow_role`. In the RFC, you must provide the S3 bucket name if the bucket is a source when Blueprints are created. S3 bucket is applicable if the Blueprint type is AWS CloudTrail, Classic Load Balancer Logs or Application Load Balancer Logs. +If you want to create Blueprints in the AWS Lake Formation Console, you need to submit a Management | AWS service | Self-provisioned service | Add (managed automation) (ct-3qe6io8t6jtny) change type and explicitly add to deploy the `customer_lakeformation_workflow_role`. In the RFC, you must provide the S3 bucket name if the bucket is a source when Blueprints are created. S3 bucket is applicable if the Blueprint type is AWS CloudTrail, Classic Load Balancer Logs or Application Load Balancer Logs.