Deploying feature flags and configuration data in Amazon AppConfig - Amazon AppConfig
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Deploying feature flags and configuration data in Amazon 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 Amazon Key Management Service (Amazon KMS) key ID to encrypt the data using a customer managed key.

When you call the StartDeployment API action, Amazon 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.

Amazon AppConfig integrates with Amazon CloudWatch to monitor deployments. If a deployment triggers an alarm in CloudWatch, Amazon AppConfig automatically rolls back the deployment to minimize impact on your application users.