Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Deploying feature flags and configuration data in AWS AppConfig

Focus mode
Deploying feature flags and configuration data in AWS AppConfig - 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:

  1. Retrieves the configuration data from the underlying data store by using the location URI in the configuration profile.

  2. Verifies the configuration data is syntactically and semantically correct by using the validators you specified when you created your configuration profile.

  3. 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.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.