Class: AWS.AppConfig
- Inherits:
-
AWS.Service
- Object
- AWS.Service
- AWS.AppConfig
- Identifier:
- appconfig
- API Version:
- 2019-10-09
- Defined in:
- (unknown)
Overview
Constructs a service interface object. Each API operation is exposed as a function on service.
Service Description
AppConfig feature flags and dynamic configurations help software builders quickly and securely adjust application behavior in production environments without full code deployments. AppConfig speeds up software release frequency, improves application resiliency, and helps you address emergent issues more quickly. With feature flags, you can gradually release new capabilities to users and measure the impact of those changes before fully deploying the new capabilities to all users. With operational flags and dynamic configurations, you can update block lists, allow lists, throttling limits, logging verbosity, and perform other operational tuning to quickly respond to issues in production environments.
Despite the fact that application configuration content can vary greatly from application to application, AppConfig supports the following use cases, which cover a broad spectrum of customer needs:
-
Feature flags and toggles - Safely release new capabilities to your customers in a controlled environment. Instantly roll back changes if you experience a problem.
-
Application tuning - Carefully introduce application changes while testing the impact of those changes with users in production environments.
-
Allow list or block list - Control access to premium features or instantly block specific users without deploying new code.
-
Centralized configuration storage - Keep your configuration data organized and consistent across all of your workloads. You can use AppConfig to deploy configuration data stored in the AppConfig hosted configuration store, Secrets Manager, Systems Manager, Parameter Store, or Amazon S3.
How AppConfig works
This section provides a high-level description of how AppConfig works and how you get started.
- 1. Identify configuration values in code you want to manage in the cloud
-
Before you start creating AppConfig artifacts, we recommend you identify configuration data in your code that you want to dynamically manage using AppConfig. Good examples include feature flags or toggles, allow and block lists, logging verbosity, service limits, and throttling rules, to name a few.
If your configuration data already exists in the cloud, you can take advantage of AppConfig validation, deployment, and extension features to further streamline configuration data management.
- 2. Create an application namespace
-
To create a namespace, you create an AppConfig artifact called an application. An application is simply an organizational construct like a folder.
- 3. Create environments
-
For each AppConfig application, you define one or more environments. An environment is a logical grouping of targets, such as applications in a
Beta
orProduction
environment, Lambda functions, or containers. You can also define environments for application subcomponents, such as theWeb
,Mobile
, andBack-end
.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.
- 4. Create a configuration profile
-
A configuration profile includes, among other things, a URI that enables AppConfig to locate your configuration data in its stored location and a profile type. AppConfig supports two configuration profile types: feature flags and freeform configurations. Feature flag configuration profiles store their data in the AppConfig hosted configuration store and the URI is simply
hosted
. For freeform configuration profiles, you can store your data in the AppConfig hosted configuration store or any Amazon Web Services service that integrates with AppConfig, as described in Creating a free form configuration profile in the the AppConfig User Guide.A configuration profile can also include optional validators to ensure your configuration data is syntactically and semantically correct. AppConfig performs a check using the validators when you start a deployment. If any errors are detected, the deployment rolls back to the previous configuration data.
- 5. Deploy configuration data
-
When you create a new deployment, you specify the following:
-
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
When you call the StartDeployment API action, 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.
-
- 6. Retrieve the configuration
-
You can configure AppConfig Agent as a local host and have the agent poll AppConfig for configuration updates. The agent calls the StartConfigurationSession and GetLatestConfiguration API actions and caches your configuration data locally. To retrieve the data, your application makes an HTTP call to the localhost server. AppConfig Agent supports several use cases, as described in Simplified retrieval methods in the the AppConfig User Guide.
If AppConfig Agent isn't supported for your use case, you can configure your application to poll AppConfig for configuration updates by directly calling the StartConfigurationSession and GetLatestConfiguration API actions.
This reference is intended to be used with the AppConfig User Guide.
Sending a Request Using AppConfig
var appconfig = new AWS.AppConfig();
appconfig.createApplication(params, function (err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});
Locking the API Version
In order to ensure that the AppConfig object uses this specific API, you can
construct the object by passing the apiVersion
option to the constructor:
var appconfig = new AWS.AppConfig({apiVersion: '2019-10-09'});
You can also set the API version globally in AWS.config.apiVersions
using
the appconfig service identifier:
AWS.config.apiVersions = {
appconfig: '2019-10-09',
// other service API versions
};
var appconfig = new AWS.AppConfig();
Constructor Summary collapse
-
new AWS.AppConfig(options = {}) ⇒ Object
constructor
Constructs a service object.
Property Summary collapse
-
endpoint ⇒ AWS.Endpoint
readwrite
An Endpoint object representing the endpoint URL for service requests.
Properties inherited from AWS.Service
Method Summary collapse
-
createApplication(params = {}, callback) ⇒ AWS.Request
Creates an application.
-
createConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Creates a configuration profile, which is information that enables AppConfig to access the configuration source.
-
createDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
Creates a deployment strategy that defines important criteria for rolling out your configuration to the designated targets.
-
createEnvironment(params = {}, callback) ⇒ AWS.Request
Creates an environment.
-
createExtension(params = {}, callback) ⇒ AWS.Request
Creates an AppConfig extension.
-
createExtensionAssociation(params = {}, callback) ⇒ AWS.Request
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.
-
createHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Creates a new configuration in the AppConfig hosted configuration store.
.
-
deleteApplication(params = {}, callback) ⇒ AWS.Request
Deletes an application.
-
deleteConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Deletes a configuration profile.
-
deleteDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
Deletes a deployment strategy.
-
deleteEnvironment(params = {}, callback) ⇒ AWS.Request
Deletes an environment.
-
deleteExtension(params = {}, callback) ⇒ AWS.Request
Deletes an AppConfig extension.
-
deleteExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Deletes an extension association.
-
deleteHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Deletes a version of a configuration from the AppConfig hosted configuration store.
.
-
getApplication(params = {}, callback) ⇒ AWS.Request
Retrieves information about an application.
.
-
getConfiguration(params = {}, callback) ⇒ AWS.Request
(Deprecated) Retrieves the latest deployed configuration.
Note the following important information.
-
This API action is deprecated.
-
-
getConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Retrieves information about a configuration profile.
.
-
getDeployment(params = {}, callback) ⇒ AWS.Request
Retrieves information about a configuration deployment.
.
-
getDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
Retrieves information about a deployment strategy.
-
getEnvironment(params = {}, callback) ⇒ AWS.Request
Retrieves information about an environment.
-
getExtension(params = {}, callback) ⇒ AWS.Request
Returns information about an AppConfig extension.
.
-
getExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Returns information about an AppConfig extension association.
-
getHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Retrieves information about a specific configuration version.
.
-
listApplications(params = {}, callback) ⇒ AWS.Request
Lists all applications in your Amazon Web Services account.
.
-
listConfigurationProfiles(params = {}, callback) ⇒ AWS.Request
Lists the configuration profiles for an application.
.
-
listDeployments(params = {}, callback) ⇒ AWS.Request
Lists the deployments for an environment in descending deployment number order.
.
-
listDeploymentStrategies(params = {}, callback) ⇒ AWS.Request
Lists deployment strategies.
.
-
listEnvironments(params = {}, callback) ⇒ AWS.Request
Lists the environments for an application.
.
-
listExtensionAssociations(params = {}, callback) ⇒ AWS.Request
Lists all AppConfig extension associations in the account.
-
listExtensions(params = {}, callback) ⇒ AWS.Request
Lists all custom and Amazon Web Services authored AppConfig extensions in the account.
-
listHostedConfigurationVersions(params = {}, callback) ⇒ AWS.Request
Lists configurations stored in the AppConfig hosted configuration store by version.
.
-
listTagsForResource(params = {}, callback) ⇒ AWS.Request
Retrieves the list of key-value tags assigned to the resource.
.
-
startDeployment(params = {}, callback) ⇒ AWS.Request
Starts a deployment.
.
-
stopDeployment(params = {}, callback) ⇒ AWS.Request
Stops a deployment.
-
tagResource(params = {}, callback) ⇒ AWS.Request
Assigns metadata to an AppConfig resource.
-
untagResource(params = {}, callback) ⇒ AWS.Request
Deletes a tag key and value from an AppConfig resource.
.
-
updateApplication(params = {}, callback) ⇒ AWS.Request
Updates an application.
.
-
updateConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Updates a configuration profile.
.
-
updateDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
Updates a deployment strategy.
.
-
updateEnvironment(params = {}, callback) ⇒ AWS.Request
Updates an environment.
.
-
updateExtension(params = {}, callback) ⇒ AWS.Request
Updates an AppConfig extension.
-
updateExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Updates an association.
-
validateConfiguration(params = {}, callback) ⇒ AWS.Request
Uses the validators in a configuration profile to validate a configuration.
.
Methods inherited from AWS.Service
makeRequest, makeUnauthenticatedRequest, waitFor, setupRequestListeners, defineService
Constructor Details
new AWS.AppConfig(options = {}) ⇒ Object
Constructs a service object. This object has one method for each API operation.
Property Details
Method Details
createApplication(params = {}, callback) ⇒ AWS.Request
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.
createConfigurationProfile(params = {}, callback) ⇒ AWS.Request
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.
createDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
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.
createEnvironment(params = {}, callback) ⇒ AWS.Request
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.
createExtension(params = {}, callback) ⇒ AWS.Request
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.
createExtensionAssociation(params = {}, callback) ⇒ AWS.Request
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.
createHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Creates a new configuration in the AppConfig hosted configuration store.
deleteApplication(params = {}, callback) ⇒ AWS.Request
Deletes an application. Deleting an application does not delete a configuration from a host.
deleteConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Deletes a configuration profile. Deleting a configuration profile does not delete a configuration from a host.
deleteDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
Deletes a deployment strategy. Deleting a deployment strategy does not delete a configuration from a host.
deleteEnvironment(params = {}, callback) ⇒ AWS.Request
Deletes an environment. Deleting an environment does not delete a configuration from a host.
deleteExtension(params = {}, callback) ⇒ AWS.Request
Deletes an AppConfig extension. You must delete all associations to an extension before you delete the extension.
deleteExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Deletes an extension association. This action doesn't delete extensions defined in the association.
deleteHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Deletes a version of a configuration from the AppConfig hosted configuration store.
getConfiguration(params = {}, callback) ⇒ AWS.Request
(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.
getConfigurationProfile(params = {}, callback) ⇒ AWS.Request
Retrieves information about a configuration profile.
getDeployment(params = {}, callback) ⇒ AWS.Request
Retrieves information about a configuration deployment.
getDeploymentStrategy(params = {}, callback) ⇒ AWS.Request
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.
getEnvironment(params = {}, callback) ⇒ AWS.Request
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.
getExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Returns information about an AppConfig extension association. For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.
getHostedConfigurationVersion(params = {}, callback) ⇒ AWS.Request
Retrieves information about a specific configuration version.
listApplications(params = {}, callback) ⇒ AWS.Request
Lists all applications in your Amazon Web Services account.
listConfigurationProfiles(params = {}, callback) ⇒ AWS.Request
Lists the configuration profiles for an application.
listDeployments(params = {}, callback) ⇒ AWS.Request
Lists the deployments for an environment in descending deployment number order.
listExtensionAssociations(params = {}, callback) ⇒ AWS.Request
Lists all AppConfig extension associations in the account. For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.
listExtensions(params = {}, callback) ⇒ AWS.Request
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.
listHostedConfigurationVersions(params = {}, callback) ⇒ AWS.Request
Lists configurations stored in the AppConfig hosted configuration store by version.
listTagsForResource(params = {}, callback) ⇒ AWS.Request
Retrieves the list of key-value tags assigned to the resource.
stopDeployment(params = {}, callback) ⇒ AWS.Request
Stops a deployment. This API action works only on deployments that have a status of DEPLOYING
. This action moves the deployment to a status of ROLLED_BACK
.
tagResource(params = {}, callback) ⇒ AWS.Request
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.
untagResource(params = {}, callback) ⇒ AWS.Request
Deletes a tag key and value from an AppConfig resource.
updateExtension(params = {}, callback) ⇒ AWS.Request
Updates an AppConfig extension. For more information about extensions, see Extending workflows in the AppConfig User Guide.
updateExtensionAssociation(params = {}, callback) ⇒ AWS.Request
Updates an association. For more information about extensions and associations, see Extending workflows in the AppConfig User Guide.