AWS solutions documentation change
Summary
Added clarification to avoid confusing qualifier values in pipeline naming
Security assessment
Operational guidance to prevent naming conflicts, not directly security-related.
Diff
diff --git a/solutions/latest/landing-zone-accelerator-on-aws/external-pipeline-deployment.md b/solutions/latest/landing-zone-accelerator-on-aws/external-pipeline-deployment.md index 2de622180..9f984bd05 100644 --- a//solutions/latest/landing-zone-accelerator-on-aws/external-pipeline-deployment.md +++ b//solutions/latest/landing-zone-accelerator-on-aws/external-pipeline-deployment.md @@ -79 +79 @@ After you create the IAM role in the management account, synthesize the Landing - 1. **AcceleratorQualifier** \- Names the resources in the external deployment account. This must be unique for each Landing Zone Accelerator on AWS pipeline created in a single external deployment account. + 1. **AcceleratorQualifier** \- Names the resources in the external deployment account. This must be unique for each Landing Zone Accelerator on AWS pipeline created in a single external deployment account, for example "env2" or "app1." Do not use "aws-accelerator" or a similar value that could be confused with the prefix.