AWS managedservices documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in disaster recovery role deployment context
Security assessment
Update removes redundant AWS branding but doesn't alter security content about trusted accounts or failback roles deployment process.
Diff
diff --git a/managedservices/latest/onboardingguide/elastic-disaster-recovery.md b/managedservices/latest/onboardingguide/elastic-disaster-recovery.md index bbe25c34f..5e9d85846 100644 --- a//managedservices/latest/onboardingguide/elastic-disaster-recovery.md +++ b//managedservices/latest/onboardingguide/elastic-disaster-recovery.md @@ -37 +37 @@ There are no restrictions to use AWS Elastic Disaster Recovery in your AMS accou - * For cross-account, cross-Region disaster recovery, AMS must set up the source and target account as Trusted Accounts and deploy the [Failback and in-AWS right-sizing roles](https://docs.aws.amazon.com/drs/latest/userguide/trusted-accounts-failback-role.html) through AWS CloudFormation. + * For cross-account, cross-Region disaster recovery, AMS must set up the source and target account as Trusted Accounts and deploy the [Failback and in-AWS right-sizing roles](https://docs.aws.amazon.com/drs/latest/userguide/trusted-accounts-failback-role.html) through CloudFormation.