AWS appconfig documentation change
Summary
Updated deployment strategy description and added note about AWS AppConfig Agent version 2.0.136060+ supporting entity-based gradual deployments with session consistency
Security assessment
This change adds documentation about entity-based gradual deployments and session consistency features. While consistent user experiences during deployments can prevent user confusion or errors, there's no indication this addresses a security vulnerability. The change appears to be feature documentation rather than security documentation.
Diff
diff --git a/appconfig/latest/userguide/deploying-feature-flags.md b/appconfig/latest/userguide/deploying-feature-flags.md index b4a739515..220cfa77e 100644 --- a//appconfig/latest/userguide/deploying-feature-flags.md +++ b//appconfig/latest/userguide/deploying-feature-flags.md @@ -35 +35,5 @@ When you call the [StartDeployment](https://docs.aws.amazon.com/appconfig/2019-1 -You can mitigate situations where deploying configuration data causes errors in your application by using a combination of AWS AppConfig deployment strategies and automatic rollbacks based on Amazon CloudWatch alarms. A deployment strategy enables you to slowly release changes to production environments over minutes or hours. 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. For more information about deployment strategies, see [Working with deployment strategies](./appconfig-creating-deployment-strategy.html). For more information about automatic rollbacks, see [Monitoring deployments for automatic rollback](./monitoring-deployments.html). +You can mitigate situations where deploying configuration data causes errors in your application by using a combination of AWS AppConfig deployment strategies and automatic rollbacks based on Amazon CloudWatch alarms. A deployment strategy enables you to slowly release changes to all targets or specific segments over minutes or hours—either session-based or along your own target dimension by leveraging entity-based deployments. After you configure CloudWatch, if one or more alarms go into the alarm state during a deployment, AWS AppConfig automatically rolls back your configuration data to the previous version. For more information about deployment strategies, see [Working with deployment strategies](./appconfig-creating-deployment-strategy.html). For more information about automatic rollbacks, see [Monitoring deployments for automatic rollback](./monitoring-deployments.html). + +###### Note + +AWS AppConfig Agent (version 2.0.136060 or later) supports deploying feature flag or free-form configuration data to specific segments or individual users during a gradual rollout. Entity-based gradual deployments ensure that once a user or segment receives a configuration version, they continue to receive that same version throughout the deployment period, regardless of which compute resource serves their requests. For more information, see [Using AWS AppConfig Agent for user- or entity-based gradual deployments](./appconfig-agent-how-to-use.html#appconfig-entity-based-gradual-deployments).