Creates an application.

In AppConfig, an application is simply an organizational construct like a folder. This organizational construct has a relationship with some unit of executable code. For example, you could create an application called MyMobileApp to organize and manage configuration data for a mobile application installed by your users.

Creates a configuration profile, which is information that enables AppConfig to access the configuration source.

Valid configuration sources include the following:

* Configuration data in YAML, JSON, and other formats stored in the AppConfig hosted configuration store

* Configuration data stored as objects in an Amazon Simple Storage Service (Amazon S3) bucket

* Pipelines stored in CodePipeline

* Secrets stored in Secrets Manager

* Standard and secure string parameters stored in Amazon Web Services Systems Manager Parameter Store

* Configuration data in SSM documents stored in the Systems Manager document store

A configuration profile includes the following information:

* The URI location of the configuration data.

* The Identity and Access Management (IAM) role that provides access to the configuration data.

* A validator for the configuration data. Available validators include either a JSON Schema or an Amazon Web Services Lambda function.

For more information, see Create a Configuration and a Configuration Profile in the AppConfig User Guide.

Creates a deployment strategy that defines important criteria for rolling out your configuration to the designated targets.

A deployment strategy includes the overall duration required, a percentage of targets to receive the deployment during each interval, an algorithm that defines how percentage grows, and bake time.

Creates an environment.

For each application, you define one or more environments. An environment is a deployment group of AppConfig targets, such as applications in a Beta or Production environment. You can also define environments for application subcomponents such as the Web, Mobile and Back-end components for your application. You can configure Amazon CloudWatch alarms for each environment. The system monitors alarms during a configuration deployment. If an alarm is triggered, the system rolls back the configuration.

Creates an experiment definition in AppConfig.

An experiment definition describes the purpose, scope, and operational configuration of an experiment, including the target audience, feature flag, and treatment configurations.

Creates an AppConfig extension.

An extension augments your ability to inject logic or behavior at different points during the AppConfig workflow of creating or deploying a configuration.

You can create your own extensions or use the Amazon Web Services authored extensions provided by AppConfig. For an AppConfig extension that uses Lambda, you must create a Lambda function to perform any computation and processing defined in the extension. If you plan to create custom versions of the Amazon Web Services authored notification extensions, you only need to specify an Amazon Resource Name (ARN) in the Uri field for the new extension version.

* For a custom EventBridge notification extension, enter the ARN of the EventBridge default events in the Uri field.

* For a custom Amazon SNS notification extension, enter the ARN of an Amazon SNS topic in the Uri field.

* For a custom Amazon SQS notification extension, enter the ARN of an Amazon SQS message queue in the Uri field.

For more information about extensions, see Extending workflows in the AppConfig User Guide.

When you create an extension or configure an Amazon Web Services authored extension, you associate the extension with an AppConfig application, environment, or configuration profile.

For example, you can choose to run the

AppConfig
deployment events to Amazon SNS

Amazon Web Services authored extension and receive notifications on an Amazon SNS topic anytime a configuration deployment is started for a specific application. Defining which extension to associate with an AppConfig resource is called an extension association. An extension association is a specified relationship between an extension and an AppConfig resource, such as an application or a configuration profile. For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.

Creates a new configuration in the AppConfig hosted configuration store.

If you're creating a feature flag, we recommend you familiarize yourself with the JSON schema for feature flag data. For more information, see Type reference for AWS.AppConfig.FeatureFlags in the AppConfig User Guide.

Deletes an application.

Deletes a configuration profile.

To prevent users from unintentionally deleting actively-used configuration profiles, enable deletion protection.

Deletes a deployment strategy.

Deletes an environment.

To prevent users from unintentionally deleting actively-used environments, enable deletion protection.

Deletes an experiment definition.

You can archive the definition to hide it from the active list while preserving it for future reference, or permanently delete it along with all associated run history.

Deletes an AppConfig extension.

You must delete all associations to an extension before you delete the extension.

Deletes an extension association.

This action doesn't delete extensions defined in the association.

Deletes a version of a configuration from the AppConfig hosted configuration store.

Returns information about the status of the DeletionProtection parameter.

Retrieves information about an application.

(Deprecated) Retrieves the latest deployed configuration.

Note the following important information.

This API action is deprecated. Calls to receive configuration data should use the StartConfigurationSession and GetLatestConfiguration APIs instead.

GetConfiguration is a priced call. For more information, see Pricing.

Retrieves information about a configuration profile.

Retrieves information about a configuration deployment.

Retrieves information about a deployment strategy.

A deployment strategy defines important criteria for rolling out your configuration to the designated targets. A deployment strategy includes the overall duration required, a percentage of targets to receive the deployment during each interval, an algorithm that defines how percentage grows, and bake time.

Retrieves information about an environment.

An environment is a deployment group of AppConfig applications, such as applications in a Production environment or in an EU_Region environment. Each configuration deployment targets an environment. You can enable one or more Amazon CloudWatch alarms for an environment. If an alarm is triggered during a deployment, AppConfig roles back the configuration.

Retrieves information about an experiment definition.

Retrieves information about an experiment run, including its status, start time, and exposure settings.

Returns information about an AppConfig extension.

Returns information about an AppConfig extension association.

For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.

Retrieves information about a specific configuration version.

Lists all applications in your Amazon Web Services account.

Lists the configuration profiles for an application.

Lists deployment strategies.

Lists the deployments for an environment in descending deployment number order.

Lists the environments for an application.

Lists the experiment definitions for an account.

You can filter results by application, configuration profile, environment, or status.

Lists the events for a specified experiment run.

Events provide a timeline of actions and state changes that occurred during the run.

Lists the experiment runs for a specified experiment definition.

You can filter by status.

Lists all AppConfig extension associations in the account.

For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.

Lists all custom and Amazon Web Services authored AppConfig extensions in the account.

For more information about extensions, see Extending workflows in the AppConfig User Guide.

Lists configurations stored in the AppConfig hosted configuration store by version.

Retrieves the list of key-value tags assigned to the resource.

Starts a deployment.

AppConfig Agent 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 AppConfig Agent for user-based or entity-based gradual deployments

Starts an experiment run for the specified experiment definition.

An experiment run delivers treatments to the target audience and collects metrics. You can start multiple experiment runs from the same experiment definition.

Stops a deployment.

This API action works only on deployments that have a status of DEPLOYING, unless an AllowRevert parameter is supplied. If the AllowRevert parameter is supplied, the status of an in-progress deployment will be ROLLED_BACK. The status of a completed deployment will be REVERTED. AppConfig only allows a revert within 72 hours of deployment completion.

Stops a running experiment.

Stopping an experiment run ends audience exposure and returns users to the currently deployed feature flag configuration.

Assigns metadata to an AppConfig resource.

Tags help organize and categorize your AppConfig resources. Each tag consists of a key and an optional value, both of which you define. You can specify a maximum of 50 tags for a resource.

Deletes a tag key and value from an AppConfig resource.

Updates the value of the DeletionProtection parameter.

Updates an application.

Updates a configuration profile.

Updates a deployment strategy.

Updates an environment.

Updates an experiment definition.

You can update treatments, the control, audience rules, and other properties. You cannot update an experiment definition while an experiment run is active.

Updates a running experiment.

Use this operation to increase audience exposure, modify treatment assignment overrides, or update the description of an active experiment run. Audience exposure can only be increased, not decreased.

Updates an AppConfig extension.

For more information about extensions, see Extending workflows in the AppConfig User Guide.

Updates an association.

For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.

Uses the validators in a configuration profile to validate a configuration.