AWS appconfig documentation change
Summary
Removed '(Recommended)' label from CloudWatch rollback permissions reference
Security assessment
Formatting change that maintains existing security documentation without adding new security features or addressing vulnerabilities.
Diff
diff --git a/appconfig/latest/userguide/appconfig-deploying-reverting.md b/appconfig/latest/userguide/appconfig-deploying-reverting.md index 07641e4de..d7ca7ed43 100644 --- a//appconfig/latest/userguide/appconfig-deploying-reverting.md +++ b//appconfig/latest/userguide/appconfig-deploying-reverting.md @@ -9 +9 @@ During a deployment, you can mitigate situations where malformed or incorrect co -For automatic rollbacks, you can use a combination of AWS AppConfig [deployment strategies](https://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-creating-deployment-strategy.html) and Amazon CloudWatch alarms. Once configured, if one or more CloudWatch alarms go into the `ALARM` state during a deployment, AWS AppConfig automatically rolls back your configuration data to the previous version, thereby preventing application outages or errors. To get started, see [(Recommended) Configure permissions for automatic rollback](./setting-up-appconfig.html#getting-started-with-appconfig-cloudwatch-alarms-permissions). +For automatic rollbacks, you can use a combination of AWS AppConfig [deployment strategies](https://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-creating-deployment-strategy.html) and Amazon CloudWatch alarms. Once configured, if one or more CloudWatch alarms go into the `ALARM` state during a deployment, AWS AppConfig automatically rolls back your configuration data to the previous version, thereby preventing application outages or errors. To get started, see [Configure permissions for automatic rollback](./setting-up-appconfig.html#getting-started-with-appconfig-cloudwatch-alarms-permissions).