Deploying feature flags and configuration data in AWS AppConfig
After you create required artifacts for working with feature flags and freeform configuration data, you can create a new deployment. When you create a new deployment, you specify the following information:
-
An application ID
-
A configuration profile ID
-
A configuration version
-
An environment ID where you want to deploy the configuration data
-
A deployment strategy ID that defines how fast you want the changes to take effect
-
An AWS Key Management Service (AWS KMS) key ID to encrypt the data using a customer managed key.
When you call the StartDeployment API action, AWS AppConfig performs the following tasks:
-
Retrieves the configuration data from the underlying data store by using the location URI in the configuration profile.
-
Verifies the configuration data is syntactically and semantically correct by using the validators you specified when you created your configuration profile.
-
Caches a copy of the data so it is ready to be retrieved by your application. This cached copy is called the deployed data.
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. For more information about automatic rollbacks, see Monitoring deployments for automatic rollback.
Topics
