AWS cli documentation change
Summary
Updated AWS CLI version reference from 2.35.11 to 2.35.13, rewrote AppConfig introduction for clarity, restructured workflow steps, added new experiment-related commands, and improved documentation flow.
Security assessment
Changes are editorial improvements and feature updates without evidence of addressing security vulnerabilities. The rewrite emphasizes safe deployment practices and risk reduction, but these are inherent service capabilities rather than new security features or vulnerability fixes. No CVE, vulnerability disclosure, or security-specific remediation is mentioned.
Diff
diff --git a/cli/latest/reference/appconfig/index.md b/cli/latest/reference/appconfig/index.md index f2995a6d2..778a6f4ae 100644 --- a//cli/latest/reference/appconfig/index.md +++ b//cli/latest/reference/appconfig/index.md @@ -15 +15 @@ - * [AWS CLI 2.35.11 Command Reference](../../index.html) » + * [AWS CLI 2.35.13 Command Reference](../../index.html) » @@ -55 +55 @@ First time using the AWS CLI? See the [User Guide](https://docs.aws.amazon.com/c -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. +AppConfig helps you safely change application behavior in production without redeploying code. Using feature flags and dynamic free-form configurations, you can control how your application runs in real time. This approach reduces risk, accelerates releases, and enables faster responses to issues. You can gradually roll out new features to specific users, monitor their impact, and expand availability with confidence. You can also update block lists, allow lists, throttling limits, and logging levels instantly, allowing you to mitigate issues and fine-tune performance without a deployment. @@ -57 +57 @@ AppConfig feature flags and dynamic configurations help software builders quickl -### Note +AppConfig supports a broad spectrum of use cases: @@ -59,8 +59,4 @@ AppConfig feature flags and dynamic configurations help software builders quickl -AppConfig is a tool in Amazon Web Services Systems Manager. - -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. + * **Feature flags and toggles** – Gradually release new capabilities to targeted users, monitor impact, and instantly roll back changes if issues occur. + * **Application tuning** – Introduce changes safely in production, measure their effects, and refine behavior without redeploying code. + * **Allow list or block list** – Control access to features or restrict specific users in real time, without modifying application code. + * **Centralized configuration storage** – Manage configuration data consistently across workloads. AppConfig can deploy configuration from the AppConfig hosted configuration store, Secrets Manager, Systems Manager, Systems Manager Parameter Store, or Amazon S3. @@ -74 +70 @@ This section provides a high-level description of how AppConfig works and how yo -> 1. Identify configuration values in code you want to manage in the cloud +> 1. Identify configuration data to manage in AppConfig @@ -78 +74 @@ This section provides a high-level description of how AppConfig works and how yo -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. +Before creating a configuration profile, identify the configuration data in your code that you want to manage dynamically using AppConfig. Common examples include feature flags, allow and block lists, logging levels, service limits, and throttling rules. These values tend to change frequently and can cause issues if misconfigured. @@ -80 +76 @@ Before you start creating AppConfig artifacts, we recommend you identify configu -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. +If your configuration data already exists in cloud services such as Systems Manager Parameter Store or Amazon S3, you can use AppConfig to validate, deploy, and manage that data more effectively. @@ -82 +78 @@ If your configuration data already exists in the cloud, you can take advantage o -> 2. Create an application namespace +> 2. Create a configuration profile in AppConfig @@ -86,4 +82 @@ If your configuration data already exists in the cloud, you can take advantage o -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 -> +A configuration profile defines how AppConfig locates and manages your configuration data. It includes a URI that points to the data source and a profile type. @@ -90,0 +84 @@ To create a namespace, you create an AppConfig artifact called an application. A +AppConfig supports two profile types @@ -92 +86,2 @@ To create a namespace, you create an AppConfig artifact called an application. A -For each AppConfig application, you define one or more environments. An environment is a logical grouping of targets, such as applications in a `Beta` or `Production` environment, Lambda functions, or containers. You can also define environments for application subcomponents, such as the `Web` , `Mobile` , and `Back-end` . + * **Feature flags** – Enable controlled feature releases, gradual rollouts, and testing in production. + * **Free-form configurations** – Store and retrieve configuration data from external sources and update it without redeploying code. @@ -94 +88,0 @@ For each AppConfig application, you define one or more environments. An environm -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. @@ -96,2 +89,0 @@ You can configure Amazon CloudWatch alarms for each environment. The system moni -> 4. Create a configuration profile -> @@ -98,0 +91 @@ You can configure Amazon CloudWatch alarms for each environment. The system moni +Both profile types help decouple configuration from code, support continuous delivery, and reduce deployment risk. @@ -100 +93 @@ You can configure Amazon CloudWatch alarms for each environment. The system moni -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](http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-free-form-configurations-creating.html) in the the _AppConfig User Guide_ . +You can also add optional validators to ensure that configuration data is syntactically and semantically correct. During deployment, AppConfig evaluates these validators and automatically rolls back changes if validation fails. @@ -102 +95 @@ A configuration profile includes, among other things, a URI that enables AppConf -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. +Each configuration profile is associated with an application, which acts as a logical container for your configuration resources. For more information about creating a configuration profile, see [Creating a configuration profile in AppConfig](http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-creating-configuration-profile.html) in the the _AppConfig User Guide_ . @@ -104 +97 @@ A configuration profile can also include optional validators to ensure your conf -> 5. Deploy configuration data +> 3. Deploy configuration data @@ -108 +101 @@ A configuration profile can also include optional validators to ensure your conf -When you create a new deployment, you specify the following: +When you start a deployment, AppConfig: @@ -110,5 +103,3 @@ 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 + * Retrieves configuration data from the source defined in the configuration profile + * Validates the data using the configured validators + * Delivers the validated configuration to AppConfig Agent @@ -118 +109 @@ When you create a new deployment, you specify the following: -When you call the [StartDeployment](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_StartDeployment.html) API action, AppConfig performs the following tasks: +The delivered configuration becomes the deployed version used by your application. For more information about deploying a configuration, see [Deploying feature flags and configuration data in AppConfig](http://docs.aws.amazon.com/appconfig/latest/userguide/deploying-feature-flags.html) . @@ -120,4 +111,2 @@ When you call the [StartDeployment](https://docs.aws.amazon.com/appconfig/2019-1 - * 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 +> 4. Retrieve configuration data +> @@ -125,0 +115 @@ When you call the [StartDeployment](https://docs.aws.amazon.com/appconfig/2019-1 +Your application retrieves configuration data by calling a local endpoint exposed by AppConfig Agent, which caches the deployed configuration. Retrieving data is a metered event. AppConfig Agent supports a variety of use cases, as described in [How to use AppConfig Agent to retrieve configuration data](http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-agent-how-to-use.html) . @@ -127 +117 @@ When you call the [StartDeployment](https://docs.aws.amazon.com/appconfig/2019-1 -You can configure AppConfig Agent as a local host and have the agent poll AppConfig for configuration updates. The agent calls the [StartConfigurationSession](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html) and [GetLatestConfiguration](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html) 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](http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-retrieving-simplified-methods.html) in the the _AppConfig User Guide_ . +If the agent is not suitable for your use case, your application can retrieve configuration data directly from AppConfig by calling the [StartConfigurationSession](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html) and [GetLatestConfiguration](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html) API actions. @@ -129 +119 @@ You can configure AppConfig Agent as a local host and have the agent poll AppCon -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](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html) and [GetLatestConfiguration](https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html) API actions. +For more information about retrieving a configuration, see [Retrieving feature flags and configuration data in AppConfig](http://docs.aws.amazon.com/appconfig/latest/userguide/retrieving-feature-flags.html) . @@ -138,0 +129 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [create-experiment-definition](create-experiment-definition.html) @@ -145,0 +137 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [delete-experiment-definition](delete-experiment-definition.html) @@ -154,0 +147,2 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [get-experiment-definition](get-experiment-definition.html) + * [get-experiment-run](get-experiment-run.html) @@ -162,0 +157,3 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [list-experiment-definitions](list-experiment-definitions.html) + * [list-experiment-run-events](list-experiment-run-events.html) + * [list-experiment-runs](list-experiment-runs.html) @@ -167,0 +165 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [start-experiment-run](start-experiment-run.html) @@ -168,0 +167 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [stop-experiment-run](stop-experiment-run.html) @@ -175,0 +175,2 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc + * [update-experiment-definition](update-experiment-definition.html) + * [update-experiment-run](update-experiment-run.html) @@ -193 +194 @@ This reference is intended to be used with the [AppConfig User Guide](http://doc - * [AWS CLI 2.35.11 Command Reference](../../index.html) » + * [AWS CLI 2.35.13 Command Reference](../../index.html) »