@aws-sdk/client-appconfig 3.1075.0 → 3.1076.0

package/dist-types/AppConfig.d.ts

@@ -5,6 +5,7 @@ import { type CreateApplicationCommandInput, type CreateApplicationCommandOutput
 import { type CreateConfigurationProfileCommandInput, type CreateConfigurationProfileCommandOutput } from "./commands/CreateConfigurationProfileCommand";
 import { type CreateDeploymentStrategyCommandInput, type CreateDeploymentStrategyCommandOutput } from "./commands/CreateDeploymentStrategyCommand";
 import { type CreateEnvironmentCommandInput, type CreateEnvironmentCommandOutput } from "./commands/CreateEnvironmentCommand";
+import { type CreateExperimentDefinitionCommandInput, type CreateExperimentDefinitionCommandOutput } from "./commands/CreateExperimentDefinitionCommand";
 import { type CreateExtensionAssociationCommandInput, type CreateExtensionAssociationCommandOutput } from "./commands/CreateExtensionAssociationCommand";
 import { type CreateExtensionCommandInput, type CreateExtensionCommandOutput } from "./commands/CreateExtensionCommand";
 import { type CreateHostedConfigurationVersionCommandInput, type CreateHostedConfigurationVersionCommandOutput } from "./commands/CreateHostedConfigurationVersionCommand";
@@ -12,6 +13,7 @@ import { type DeleteApplicationCommandInput, type DeleteApplicationCommandOutput
 import { type DeleteConfigurationProfileCommandInput, type DeleteConfigurationProfileCommandOutput } from "./commands/DeleteConfigurationProfileCommand";
 import { type DeleteDeploymentStrategyCommandInput, type DeleteDeploymentStrategyCommandOutput } from "./commands/DeleteDeploymentStrategyCommand";
 import { type DeleteEnvironmentCommandInput, type DeleteEnvironmentCommandOutput } from "./commands/DeleteEnvironmentCommand";
+import { type DeleteExperimentDefinitionCommandInput, type DeleteExperimentDefinitionCommandOutput } from "./commands/DeleteExperimentDefinitionCommand";
 import { type DeleteExtensionAssociationCommandInput, type DeleteExtensionAssociationCommandOutput } from "./commands/DeleteExtensionAssociationCommand";
 import { type DeleteExtensionCommandInput, type DeleteExtensionCommandOutput } from "./commands/DeleteExtensionCommand";
 import { type DeleteHostedConfigurationVersionCommandInput, type DeleteHostedConfigurationVersionCommandOutput } from "./commands/DeleteHostedConfigurationVersionCommand";
@@ -22,6 +24,8 @@ import { type GetConfigurationProfileCommandInput, type GetConfigurationProfileC
 import { type GetDeploymentCommandInput, type GetDeploymentCommandOutput } from "./commands/GetDeploymentCommand";
 import { type GetDeploymentStrategyCommandInput, type GetDeploymentStrategyCommandOutput } from "./commands/GetDeploymentStrategyCommand";
 import { type GetEnvironmentCommandInput, type GetEnvironmentCommandOutput } from "./commands/GetEnvironmentCommand";
+import { type GetExperimentDefinitionCommandInput, type GetExperimentDefinitionCommandOutput } from "./commands/GetExperimentDefinitionCommand";
+import { type GetExperimentRunCommandInput, type GetExperimentRunCommandOutput } from "./commands/GetExperimentRunCommand";
 import { type GetExtensionAssociationCommandInput, type GetExtensionAssociationCommandOutput } from "./commands/GetExtensionAssociationCommand";
 import { type GetExtensionCommandInput, type GetExtensionCommandOutput } from "./commands/GetExtensionCommand";
 import { type GetHostedConfigurationVersionCommandInput, type GetHostedConfigurationVersionCommandOutput } from "./commands/GetHostedConfigurationVersionCommand";
@@ -30,12 +34,17 @@ import { type ListConfigurationProfilesCommandInput, type ListConfigurationProfi
 import { type ListDeploymentsCommandInput, type ListDeploymentsCommandOutput } from "./commands/ListDeploymentsCommand";
 import { type ListDeploymentStrategiesCommandInput, type ListDeploymentStrategiesCommandOutput } from "./commands/ListDeploymentStrategiesCommand";
 import { type ListEnvironmentsCommandInput, type ListEnvironmentsCommandOutput } from "./commands/ListEnvironmentsCommand";
+import { type ListExperimentDefinitionsCommandInput, type ListExperimentDefinitionsCommandOutput } from "./commands/ListExperimentDefinitionsCommand";
+import { type ListExperimentRunEventsCommandInput, type ListExperimentRunEventsCommandOutput } from "./commands/ListExperimentRunEventsCommand";
+import { type ListExperimentRunsCommandInput, type ListExperimentRunsCommandOutput } from "./commands/ListExperimentRunsCommand";
 import { type ListExtensionAssociationsCommandInput, type ListExtensionAssociationsCommandOutput } from "./commands/ListExtensionAssociationsCommand";
 import { type ListExtensionsCommandInput, type ListExtensionsCommandOutput } from "./commands/ListExtensionsCommand";
 import { type ListHostedConfigurationVersionsCommandInput, type ListHostedConfigurationVersionsCommandOutput } from "./commands/ListHostedConfigurationVersionsCommand";
 import { type ListTagsForResourceCommandInput, type ListTagsForResourceCommandOutput } from "./commands/ListTagsForResourceCommand";
 import { type StartDeploymentCommandInput, type StartDeploymentCommandOutput } from "./commands/StartDeploymentCommand";
+import { type StartExperimentRunCommandInput, type StartExperimentRunCommandOutput } from "./commands/StartExperimentRunCommand";
 import { type StopDeploymentCommandInput, type StopDeploymentCommandOutput } from "./commands/StopDeploymentCommand";
+import { type StopExperimentRunCommandInput, type StopExperimentRunCommandOutput } from "./commands/StopExperimentRunCommand";
 import { type TagResourceCommandInput, type TagResourceCommandOutput } from "./commands/TagResourceCommand";
 import { type UntagResourceCommandInput, type UntagResourceCommandOutput } from "./commands/UntagResourceCommand";
 import { type UpdateAccountSettingsCommandInput, type UpdateAccountSettingsCommandOutput } from "./commands/UpdateAccountSettingsCommand";
@@ -43,6 +52,8 @@ import { type UpdateApplicationCommandInput, type UpdateApplicationCommandOutput
 import { type UpdateConfigurationProfileCommandInput, type UpdateConfigurationProfileCommandOutput } from "./commands/UpdateConfigurationProfileCommand";
 import { type UpdateDeploymentStrategyCommandInput, type UpdateDeploymentStrategyCommandOutput } from "./commands/UpdateDeploymentStrategyCommand";
 import { type UpdateEnvironmentCommandInput, type UpdateEnvironmentCommandOutput } from "./commands/UpdateEnvironmentCommand";
+import { type UpdateExperimentDefinitionCommandInput, type UpdateExperimentDefinitionCommandOutput } from "./commands/UpdateExperimentDefinitionCommand";
+import { type UpdateExperimentRunCommandInput, type UpdateExperimentRunCommandOutput } from "./commands/UpdateExperimentRunCommand";
 import { type UpdateExtensionAssociationCommandInput, type UpdateExtensionAssociationCommandOutput } from "./commands/UpdateExtensionAssociationCommand";
 import { type UpdateExtensionCommandInput, type UpdateExtensionCommandOutput } from "./commands/UpdateExtensionCommand";
 import { type ValidateConfigurationCommandInput, type ValidateConfigurationCommandOutput } from "./commands/ValidateConfigurationCommand";
@@ -71,6 +82,12 @@ export interface AppConfig {
     createEnvironment(args: CreateEnvironmentCommandInput, options?: __HttpHandlerOptions): Promise<CreateEnvironmentCommandOutput>;
     createEnvironment(args: CreateEnvironmentCommandInput, cb: (err: any, data?: CreateEnvironmentCommandOutput) => void): void;
     createEnvironment(args: CreateEnvironmentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateEnvironmentCommandOutput) => void): void;
+    /**
+     * @see {@link CreateExperimentDefinitionCommand}
+     */
+    createExperimentDefinition(args: CreateExperimentDefinitionCommandInput, options?: __HttpHandlerOptions): Promise<CreateExperimentDefinitionCommandOutput>;
+    createExperimentDefinition(args: CreateExperimentDefinitionCommandInput, cb: (err: any, data?: CreateExperimentDefinitionCommandOutput) => void): void;
+    createExperimentDefinition(args: CreateExperimentDefinitionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateExperimentDefinitionCommandOutput) => void): void;
     /**
      * @see {@link CreateExtensionCommand}
      */
@@ -113,6 +130,12 @@ export interface AppConfig {
     deleteEnvironment(args: DeleteEnvironmentCommandInput, options?: __HttpHandlerOptions): Promise<DeleteEnvironmentCommandOutput>;
     deleteEnvironment(args: DeleteEnvironmentCommandInput, cb: (err: any, data?: DeleteEnvironmentCommandOutput) => void): void;
     deleteEnvironment(args: DeleteEnvironmentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteEnvironmentCommandOutput) => void): void;
+    /**
+     * @see {@link DeleteExperimentDefinitionCommand}
+     */
+    deleteExperimentDefinition(args: DeleteExperimentDefinitionCommandInput, options?: __HttpHandlerOptions): Promise<DeleteExperimentDefinitionCommandOutput>;
+    deleteExperimentDefinition(args: DeleteExperimentDefinitionCommandInput, cb: (err: any, data?: DeleteExperimentDefinitionCommandOutput) => void): void;
+    deleteExperimentDefinition(args: DeleteExperimentDefinitionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteExperimentDefinitionCommandOutput) => void): void;
     /**
      * @see {@link DeleteExtensionCommand}
      */
@@ -174,6 +197,18 @@ export interface AppConfig {
     getEnvironment(args: GetEnvironmentCommandInput, options?: __HttpHandlerOptions): Promise<GetEnvironmentCommandOutput>;
     getEnvironment(args: GetEnvironmentCommandInput, cb: (err: any, data?: GetEnvironmentCommandOutput) => void): void;
     getEnvironment(args: GetEnvironmentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetEnvironmentCommandOutput) => void): void;
+    /**
+     * @see {@link GetExperimentDefinitionCommand}
+     */
+    getExperimentDefinition(args: GetExperimentDefinitionCommandInput, options?: __HttpHandlerOptions): Promise<GetExperimentDefinitionCommandOutput>;
+    getExperimentDefinition(args: GetExperimentDefinitionCommandInput, cb: (err: any, data?: GetExperimentDefinitionCommandOutput) => void): void;
+    getExperimentDefinition(args: GetExperimentDefinitionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetExperimentDefinitionCommandOutput) => void): void;
+    /**
+     * @see {@link GetExperimentRunCommand}
+     */
+    getExperimentRun(args: GetExperimentRunCommandInput, options?: __HttpHandlerOptions): Promise<GetExperimentRunCommandOutput>;
+    getExperimentRun(args: GetExperimentRunCommandInput, cb: (err: any, data?: GetExperimentRunCommandOutput) => void): void;
+    getExperimentRun(args: GetExperimentRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetExperimentRunCommandOutput) => void): void;
     /**
      * @see {@link GetExtensionCommand}
      */
@@ -224,6 +259,25 @@ export interface AppConfig {
     listEnvironments(args: ListEnvironmentsCommandInput, options?: __HttpHandlerOptions): Promise<ListEnvironmentsCommandOutput>;
     listEnvironments(args: ListEnvironmentsCommandInput, cb: (err: any, data?: ListEnvironmentsCommandOutput) => void): void;
     listEnvironments(args: ListEnvironmentsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListEnvironmentsCommandOutput) => void): void;
+    /**
+     * @see {@link ListExperimentDefinitionsCommand}
+     */
+    listExperimentDefinitions(): Promise<ListExperimentDefinitionsCommandOutput>;
+    listExperimentDefinitions(args: ListExperimentDefinitionsCommandInput, options?: __HttpHandlerOptions): Promise<ListExperimentDefinitionsCommandOutput>;
+    listExperimentDefinitions(args: ListExperimentDefinitionsCommandInput, cb: (err: any, data?: ListExperimentDefinitionsCommandOutput) => void): void;
+    listExperimentDefinitions(args: ListExperimentDefinitionsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListExperimentDefinitionsCommandOutput) => void): void;
+    /**
+     * @see {@link ListExperimentRunEventsCommand}
+     */
+    listExperimentRunEvents(args: ListExperimentRunEventsCommandInput, options?: __HttpHandlerOptions): Promise<ListExperimentRunEventsCommandOutput>;
+    listExperimentRunEvents(args: ListExperimentRunEventsCommandInput, cb: (err: any, data?: ListExperimentRunEventsCommandOutput) => void): void;
+    listExperimentRunEvents(args: ListExperimentRunEventsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListExperimentRunEventsCommandOutput) => void): void;
+    /**
+     * @see {@link ListExperimentRunsCommand}
+     */
+    listExperimentRuns(args: ListExperimentRunsCommandInput, options?: __HttpHandlerOptions): Promise<ListExperimentRunsCommandOutput>;
+    listExperimentRuns(args: ListExperimentRunsCommandInput, cb: (err: any, data?: ListExperimentRunsCommandOutput) => void): void;
+    listExperimentRuns(args: ListExperimentRunsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListExperimentRunsCommandOutput) => void): void;
     /**
      * @see {@link ListExtensionAssociationsCommand}
      */
@@ -256,12 +310,24 @@ export interface AppConfig {
     startDeployment(args: StartDeploymentCommandInput, options?: __HttpHandlerOptions): Promise<StartDeploymentCommandOutput>;
     startDeployment(args: StartDeploymentCommandInput, cb: (err: any, data?: StartDeploymentCommandOutput) => void): void;
     startDeployment(args: StartDeploymentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: StartDeploymentCommandOutput) => void): void;
+    /**
+     * @see {@link StartExperimentRunCommand}
+     */
+    startExperimentRun(args: StartExperimentRunCommandInput, options?: __HttpHandlerOptions): Promise<StartExperimentRunCommandOutput>;
+    startExperimentRun(args: StartExperimentRunCommandInput, cb: (err: any, data?: StartExperimentRunCommandOutput) => void): void;
+    startExperimentRun(args: StartExperimentRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: StartExperimentRunCommandOutput) => void): void;
     /**
      * @see {@link StopDeploymentCommand}
      */
     stopDeployment(args: StopDeploymentCommandInput, options?: __HttpHandlerOptions): Promise<StopDeploymentCommandOutput>;
     stopDeployment(args: StopDeploymentCommandInput, cb: (err: any, data?: StopDeploymentCommandOutput) => void): void;
     stopDeployment(args: StopDeploymentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: StopDeploymentCommandOutput) => void): void;
+    /**
+     * @see {@link StopExperimentRunCommand}
+     */
+    stopExperimentRun(args: StopExperimentRunCommandInput, options?: __HttpHandlerOptions): Promise<StopExperimentRunCommandOutput>;
+    stopExperimentRun(args: StopExperimentRunCommandInput, cb: (err: any, data?: StopExperimentRunCommandOutput) => void): void;
+    stopExperimentRun(args: StopExperimentRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: StopExperimentRunCommandOutput) => void): void;
     /**
      * @see {@link TagResourceCommand}
      */
@@ -305,6 +371,18 @@ export interface AppConfig {
     updateEnvironment(args: UpdateEnvironmentCommandInput, options?: __HttpHandlerOptions): Promise<UpdateEnvironmentCommandOutput>;
     updateEnvironment(args: UpdateEnvironmentCommandInput, cb: (err: any, data?: UpdateEnvironmentCommandOutput) => void): void;
     updateEnvironment(args: UpdateEnvironmentCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateEnvironmentCommandOutput) => void): void;
+    /**
+     * @see {@link UpdateExperimentDefinitionCommand}
+     */
+    updateExperimentDefinition(args: UpdateExperimentDefinitionCommandInput, options?: __HttpHandlerOptions): Promise<UpdateExperimentDefinitionCommandOutput>;
+    updateExperimentDefinition(args: UpdateExperimentDefinitionCommandInput, cb: (err: any, data?: UpdateExperimentDefinitionCommandOutput) => void): void;
+    updateExperimentDefinition(args: UpdateExperimentDefinitionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateExperimentDefinitionCommandOutput) => void): void;
+    /**
+     * @see {@link UpdateExperimentRunCommand}
+     */
+    updateExperimentRun(args: UpdateExperimentRunCommandInput, options?: __HttpHandlerOptions): Promise<UpdateExperimentRunCommandOutput>;
+    updateExperimentRun(args: UpdateExperimentRunCommandInput, cb: (err: any, data?: UpdateExperimentRunCommandOutput) => void): void;
+    updateExperimentRun(args: UpdateExperimentRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateExperimentRunCommandOutput) => void): void;
     /**
      * @see {@link UpdateExtensionCommand}
      */
@@ -358,6 +436,27 @@ export interface AppConfig {
      * @returns AsyncIterable of {@link ListEnvironmentsCommandOutput}.
      */
     paginateListEnvironments(args: ListEnvironmentsCommandInput, paginationConfig?: Omit<PaginationConfiguration, "client">): Paginator<ListEnvironmentsCommandOutput>;
+    /**
+     * @see {@link ListExperimentDefinitionsCommand}
+     * @param args - command input.
+     * @param paginationConfig - optional pagination config.
+     * @returns AsyncIterable of {@link ListExperimentDefinitionsCommandOutput}.
+     */
+    paginateListExperimentDefinitions(args?: ListExperimentDefinitionsCommandInput, paginationConfig?: Omit<PaginationConfiguration, "client">): Paginator<ListExperimentDefinitionsCommandOutput>;
+    /**
+     * @see {@link ListExperimentRunEventsCommand}
+     * @param args - command input.
+     * @param paginationConfig - optional pagination config.
+     * @returns AsyncIterable of {@link ListExperimentRunEventsCommandOutput}.
+     */
+    paginateListExperimentRunEvents(args: ListExperimentRunEventsCommandInput, paginationConfig?: Omit<PaginationConfiguration, "client">): Paginator<ListExperimentRunEventsCommandOutput>;
+    /**
+     * @see {@link ListExperimentRunsCommand}
+     * @param args - command input.
+     * @param paginationConfig - optional pagination config.
+     * @returns AsyncIterable of {@link ListExperimentRunsCommandOutput}.
+     */
+    paginateListExperimentRuns(args: ListExperimentRunsCommandInput, paginationConfig?: Omit<PaginationConfiguration, "client">): Paginator<ListExperimentRunsCommandOutput>;
     /**
      * @see {@link ListExtensionAssociationsCommand}
      * @param args - command input.
@@ -393,47 +492,24 @@ export interface AppConfig {
     waitUntilEnvironmentReadyForDeployment(args: GetEnvironmentCommandInput, waiterConfig: number | Omit<WaiterConfiguration<AppConfig>, "client">): Promise<WaiterResult<GetEnvironmentCommandOutput>>;
 }
 /**
- * <p>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.</p>
- *          <note>
- *             <p>AppConfig is a tool in Amazon Web Services Systems Manager.</p>
- *          </note>
- *          <p>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:</p>
+ * <p>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.</p>
+ *          <p>AppConfig supports a broad spectrum of use cases:</p>
  *          <ul>
  *             <li>
  *                <p>
- *                   <b>Feature flags and toggles</b> - Safely release new
- *                capabilities to your customers in a controlled environment. Instantly roll back
- *                changes if you experience a problem.</p>
+ *                   <b>Feature flags and toggles</b> – Gradually release new capabilities to targeted users, monitor impact, and instantly roll back changes if issues occur.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>Application tuning</b> - Carefully introduce
- *                application changes while testing the impact of those changes with users in
- *                production environments.</p>
+ *                   <b>Application tuning</b> – Introduce changes safely in production, measure their effects, and refine behavior without redeploying code.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>Allow list or block list</b> - Control access to
- *                premium features or instantly block specific users without deploying new code.
- *             </p>
+ *                   <b>Allow list or block list</b> – Control access to features or restrict specific users in real time, without modifying application code. </p>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>Centralized configuration storage</b> - 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.</p>
+ *                   <b>Centralized configuration storage</b> – 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.</p>
  *             </li>
  *          </ul>
  *          <p>
@@ -442,103 +518,50 @@ export interface AppConfig {
  *          <p>This section provides a high-level description of how AppConfig works and how
  *          you get started.</p>
  *          <dl>
- *             <dt>1. Identify configuration values in code you want to manage in the cloud</dt>
- *             <dd>
- *                <p>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.</p>
- *                <p>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.</p>
- *             </dd>
- *             <dt>2. Create an application namespace</dt>
+ *             <dt>1. Identify configuration data to manage in AppConfig</dt>
  *             <dd>
- *                <p>To create a namespace, you create an AppConfig artifact called an
- *                   application. An application is simply an organizational construct like a
- *                   folder.</p>
+ *                <p>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.</p>
+ *                <p>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.</p>
  *             </dd>
- *             <dt>3. Create environments</dt>
+ *             <dt>2. Create a configuration profile in AppConfig</dt>
  *             <dd>
- *                <p>For each AppConfig application, you define one or more environments.
- *                   An environment is a logical grouping of targets, such as applications in a
- *                      <code>Beta</code> or <code>Production</code> environment, Lambda functions,
- *                   or containers. You can also define environments for application subcomponents,
- *                   such as the <code>Web</code>, <code>Mobile</code>, and
- *                   <code>Back-end</code>.</p>
- *                <p>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.</p>
- *             </dd>
- *             <dt>4. Create a configuration profile</dt>
- *             <dd>
- *                <p>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 <code>hosted</code>. 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 <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-free-form-configurations-creating.html">Creating
- *                      a free form configuration profile</a> in the the <i>AppConfig User Guide</i>.</p>
- *                <p>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.</p>
- *             </dd>
- *             <dt>5. Deploy configuration data</dt>
- *             <dd>
- *                <p>When you create a new deployment, you specify the following:</p>
+ *                <p>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.</p>
+ *                <p>AppConfig supports two profile types</p>
  *                <ul>
  *                   <li>
- *                      <p>An application ID</p>
- *                   </li>
- *                   <li>
- *                      <p>A configuration profile ID</p>
+ *                      <p>
+ *                         <b>Feature flags</b> – Enable controlled feature releases, gradual rollouts, and testing in production.</p>
  *                   </li>
  *                   <li>
- *                      <p>A configuration version</p>
- *                   </li>
- *                   <li>
- *                      <p>An environment ID where you want to deploy the configuration data</p>
- *                   </li>
- *                   <li>
- *                      <p>A deployment strategy ID that defines how fast you want the changes to
- *                         take effect</p>
+ *                      <p>
+ *                         <b>Free-form configurations</b> – Store and retrieve configuration data from external sources and update it without redeploying code.</p>
  *                   </li>
  *                </ul>
- *                <p>When you call the <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_StartDeployment.html">StartDeployment</a> API action, AppConfig performs the following
- *                   tasks:</p>
+ *                <p>Both profile types help decouple configuration from code, support continuous delivery, and reduce deployment risk.</p>
+ *                <p>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.</p>
+ *                <p>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 <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-creating-configuration-profile.html">Creating a configuration profile in AppConfig</a> in the the <i>AppConfig User Guide</i>.</p>
+ *             </dd>
+ *             <dt>3. Deploy configuration data</dt>
+ *             <dd>
+ *                <p>When you start a deployment, AppConfig:</p>
  *                <ol>
  *                   <li>
- *                      <p>Retrieves the configuration data from the underlying data store by using
- *                         the location URI in the configuration profile.</p>
+ *                      <p>Retrieves configuration data from the source defined in the configuration profile</p>
  *                   </li>
  *                   <li>
- *                      <p>Verifies the configuration data is syntactically and semantically correct
- *                         by using the validators you specified when you created your configuration
- *                         profile.</p>
+ *                      <p>Validates the data using the configured validators</p>
  *                   </li>
  *                   <li>
- *                      <p>Caches a copy of the data so it is ready to be retrieved by your
- *                         application. This cached copy is called the <i>deployed
- *                            data</i>.</p>
+ *                      <p>Delivers the validated configuration to AppConfig Agent</p>
  *                   </li>
  *                </ol>
+ *                <p>The delivered configuration becomes the deployed version used by your application. For more information about deploying a configuration, see <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/deploying-feature-flags.html">Deploying feature flags and configuration data in AppConfig</a>.</p>
  *             </dd>
- *             <dt>6. Retrieve the configuration</dt>
+ *             <dt>4. Retrieve configuration data</dt>
  *             <dd>
- *                <p>You can configure AppConfig Agent as a local host and have the agent
- *                   poll AppConfig for configuration updates. The agent calls the <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html">StartConfigurationSession</a> and <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html">GetLatestConfiguration</a> 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 <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-retrieving-simplified-methods.html">Simplified
- *                      retrieval methods</a> in the the <i>AppConfig User
- *                      Guide</i>.</p>
- *                <p>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 <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html">StartConfigurationSession</a> and <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html">GetLatestConfiguration</a> API actions. </p>
+ *                <p>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 <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-agent-how-to-use.html">How to use AppConfig Agent to retrieve configuration data</a>.</p>
+ *                <p>If the agent is not suitable for your use case, your application can retrieve configuration data directly from AppConfig by calling the <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html">StartConfigurationSession</a> and <a href="https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html">GetLatestConfiguration</a> API actions. </p>
+ *                <p>For more information about retrieving a configuration, see <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/retrieving-feature-flags.html">Retrieving feature flags and configuration data in AppConfig</a>.</p>
  *             </dd>
  *          </dl>
  *          <p>This reference is intended to be used with the <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html">AppConfig User