# Amazon AppConfig User Guide document history
The following table describes the important changes to the documentation since the last release of Amazon AppConfig.
**Current API version: 2019-10-09**
| Change | Description | Date |
| --- |--- |--- |
| [New version of Amazon AppConfig Agent Lambda extension](#doc-history) | The agent has been updated with minor enhancements and bug fixes. To view the new Amazon Resource Names (ARNs) for the extension, see [Available versions of the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | June 22, 2026 |
| [Launch of Amazon AppConfig experimentation](#doc-history) | Application experimentation is the systematic process of testing hypotheses on software applications using A/B testing, feature flags, and analytics to measure user behavior, optimize performance, and drive data-driven product decisions. Experimentation enables teams to validate changes, such as new features or UI changes, before a full rollout, thereby reducing risk and improving engagement.
Built with the expertise of more than 20 years of software experimentation on Amazon.com, Amazon AppConfig experimentation integrates seamlessly with your existing Amazon AppConfig workflows, providing a comprehensive solution for feature management and experimentation in cloud-native applications. Amazon AppConfig experimentation offers the following features: Support for multiple feature and test types – A/B tests, multivariate tests, and gradual feature rollouts. Easy experiment setup and management through the Amazon Web Services Management Console. Powerful and flexible segmentation options for experiment participants. Data portability – use your existing data warehouses and analytics tools for experiments or use an Amazon-native service like [Amazon CloudWatch RUM](https://docs.amazonaws.cn/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.html).
Additionally, Amazon AppConfig experimentation includes automatic rollback capabilities that can revert to a safe configuration if predefined thresholds are exceeded. For example, you can monitor key metrics like page load, conversion rate, or page errors during an experiment. If a threshold is breached, the experiment will be stopped. You can set these safety monitoring capabilities using Amazon CloudWatch, Datadog, New Relic, Dynatrace, and more. For more information, see [Amazon AppConfig experimentation](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-experimentation.html). | June 12, 2026 |
| [Entity-based targeting](#doc-history) | Amazon AppConfig Agent (version 2.0.136060 or later) 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 Amazon AppConfig Agent for user- or entity-based gradual deployments](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-entity-based-gradual-deployments.html). | March 26, 2026 |
| [New version of Amazon AppConfig Agent Lambda extension](#doc-history) | The agent has been updated with minor enhancements and bug fixes. To view the new Amazon Resource Names (ARNs) for the extension, see [Available versions of the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | February 20, 2026 |
| [Deprecated: Amazon AppConfig extension for CloudWatch Evidently](#doc-history) | The Amazon AppConfig extension for CloudWatch Evidently is no longer supported. | February 20, 2026 |
| [IPv6 support](#doc-history) | All Amazon AppConfig APIs now fully support IPv4 and IPv6 calls. For more information, see [Understanding IPv6 support](https://docs.amazonaws.cn/appconfig/latest/userguide/setting-up-IPv6.html). | April 23, 2025 |
| [New topic: Saving a previous feature flag version to a new version](#doc-history) | When you update a feature flag, Amazon AppConfig automatically saves your changes to a new version. If you want to use a previous feature flag version, you must copy it to a draft version and then save it. You can't edit and save changes to a previous flag version without saving it to a new version. For more information, see [Saving a previous feature flag version to a new version](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-configuration-profile-feature-flags-editing-version.html). | April 15, 2025 |
| [New topic: Feature flag samples for Amazon AppConfig Agent local development mode](#doc-history) | Amazon AppConfig Agent supports a [local development mode](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-agent-how-to-use-local-development.html). If you enable local development mode, the agent reads configuration data from a specified directory on disk. It doesn't retrieve configuration data from Amazon AppConfig. To help you better understand how to use local development mode, this guide now contains a topic with feature flag samples. For more information, see [Feature flag samples for Amazon AppConfig Agent local development mode](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-agent-how-to-use-local-development-samples.html). | February 18, 2025 |
| [New topic: Creating a configuration profile for non-native data sources](#doc-history) | The topic describes the high level process for using an Amazon AppConfig extension to retrieve configuration data from sources that are not natively supported, including other Amazon services like Amazon RDS and Amazon DynamoDB, as well as 3rd-party sources like GitHub, GitLab, or a local repo. For more information, see [Creating a configuration profile for non-native data sources](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-configuration-profile-other-data-sources.html) | December 19, 2024 |
| [Updated topic: Fixed regex in feature flags type reference](#doc-history) | The json schema in the feature flag type reference previously showed the following regex pattern in various places: `"^[a-z][a-zA-Z\\d-_]{0,63}$"`. The correct regex pattern is `"^[a-z][a-zA-Z\\d_-]{0,63}$"`. The hyphen is listed after the underscore. For more information, see [Understanding the type reference for AWS.AppConfig.FeatureFlags](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-type-reference-feature-flags.html) | December 18, 2024 |
| [Updated topics: Environment variable samples added](#doc-history) | The tables describing environment variable in the following topics were updated to include samples: [(Optional) Using environment variables to configure Amazon AppConfig Agent for Amazon ECS and Amazon EKS](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-containers-agent-configuring.html) [(Optional) Using environment variables to configure Amazon AppConfig Agent for Amazon EC2](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-ec2.html#appconfig-integration-ec2-configuring) [Configuring the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-containers-agent-configuring.html) | December 12, 2024 |
| [New section: Understanding the split operator](#doc-history) | A new section uses examples to explain how the `split` operator works for a multi-variant feature flag rule. For more information, see [Understanding multi-variant feature flag rules](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-multi-variant-feature-flags-rules.html). | November 22, 2024 |
| [New extension action point: AT\_DEPLOYMENT\_TICK](#doc-history) | Amazon AppConfig launched a new action point for users who create custom extensions. The `AT_DEPLOYMENT_TICK` action point supports third-party monitoring integration. `AT_DEPLOYMENT_TICK` is invoked during configuration deployment processing orchestration. If you use a third-party monitoring solution (for example, Datadog), you can create an Amazon AppConfig extension that checks for alarms at the `AT_DEPLOYMENT_TICK` action point and, as a safety guardrail, rolls back the deployment if it triggered an alarm. For more information about Amazon AppConfig extensions, see [Extending Amazon AppConfig workflows using extensions](https://docs.amazonaws.cn/appconfig/latest/userguide/working-with-appconfig-extensions.html). For more information about custom extensions, see [Walkthrough: Creating custom Amazon AppConfig extensions](https://docs.amazonaws.cn/appconfig/latest/userguide/working-with-appconfig-extensions-creating-custom.html). To view a code sample of an Amazon AppConfig extension that uses the `AT_DEPLOYMENT_TICK` action point to integrate with Datadog, see [aws-samples / aws-appconfig-tick-extn-for-datadog](https://github.com/aws-samples/aws-appconfig-tick-extn-for-datadog) on GitHub. | November 22, 2024 |
| [New topic: Amazon AppConfig mobile use considerations](#doc-history) | A new topic in this guide describes important considerations for using Amazon AppConfig feature flags with mobiles devices. For more information, see [Amazon AppConfig mobile use considerations](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-retrieving-mobile.html). | November 21, 2024 |
| [New feature: Amazon AppConfig Deletion Protection](#doc-history) | Amazon AppConfig now provides an account setting to help prevent users from unintentionally deleting actively-used environments and configuration profiles. For more information, see [Configuring Amazon AppConfig deletion protection](https://docs.amazonaws.cn/appconfig/latest/userguide/deletion-protection.html). | August 28, 2024 |
| [New version of Amazon AppConfig Agent Lambda extension](#doc-history) | The agent has been updated with minor enhancements and bug fixes. To view the new Amazon Resource Names (ARNs) for the extension, see [Available versions of the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | August 9, 2024 |
| [New code samples for retrieving flag variants](#doc-history) | For more information, see [Using Amazon AppConfig Agent to retrieve a feature flag with variants](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-code-samples-agent-read-feature-flag-with-variants.html). | August 9, 2024 |
| [New version of Amazon AppConfig Agent Lambda extension](#doc-history) | The agent has been updated to support feature flag targets, variants, and splits. To view the new Amazon Resource Names (ARNs) for the extension, see [Available versions of the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | July 23, 2024 |
| [New feature: Multi-variant feature flags](#doc-history) | Multi-variant feature flags enable you to define a set of possible flag values to return for a request. You can also configure different statuses (enabled or disabled) for multi-variant flags. When requesting a flag configured with variants, your application provides context that Amazon AppConfig evaluates against a set of user-defined rules. Depending on the context specified in the request and the rules defined for the variant, Amazon AppConfig returns different flag values to the application. For more information, see [Creating multi-variant feature flags](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-multi-variant-feature-flags.html). | July 23, 2024 |
| [New version of Amazon AppConfig Agent Lambda extension](#doc-history) | The agent has been updated with minor enhancements and bug fixes. To view the new Amazon Resource Names (ARNs) for the extension, see [Available versions of the Amazon AppConfig Agent Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | February 28, 2024 |
| [Amazon AppConfig custom extension samples](#doc-history) | The [Walkthrough: Creating custom Amazon AppConfig extensions](https://docs.amazonaws.cn/appconfig/latest/userguide/working-with-appconfig-extensions-creating-custom.html) topic now includes links to the following sample extensions on GitHub: [Sample extension that prevents deployments with a `blocked day` moratorium calendar using Systems Manager Change Calendar](https://github.com/aws-samples/aws-appconfig-change-calendar-extn) [Sample extension that prevents secrets from leaking into configuration data using git-secrets](https://github.com/aws-samples/aws-appconfig-git-secrets-extn) [Sample extension that prevents personally identifiable information (PII) from leaking into configuration data using Amazon Comprehend](https://github.com/aws-samples/aws-appconfig-pii-extn) | February 28, 2024 |
| [New topic: Logging Amazon AppConfig API calls using Amazon CloudTrail](#doc-history) | Amazon AppConfig is integrated with Amazon CloudTrail, a service that provides a record of actions taken by a user, role, or an Amazon service in Amazon AppConfig. CloudTrail captures all API calls for Amazon AppConfig as events. This new topic provides Amazon AppConfig-specific content rather than linking to the corresponding content in the *Amazon Systems Manager User Guide*. For more information, see [Logging Amazon AppConfig API calls using Amazon CloudTrail](https://docs.amazonaws.cn/appconfig/latest/userguide/logging-using-cloudtrail.html). | January 18, 2024 |
| [Amazon AppConfig now supports Amazon PrivateLink](#doc-history) | You can use Amazon PrivateLink to create a private connection between your VPC and Amazon AppConfig. You can access Amazon AppConfig as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Amazon Direct Connect connection. Instances in your VPC don't need public IP addresses to access Amazon AppConfig. For more information, see [Access Amazon AppConfig using an interface endpoint (Amazon PrivateLink)](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-security.html#vpc-interface-endpoints). | December 6, 2023 |
| [Additional Amazon AppConfig Agent retrieval features and a new local development mode](#doc-history) | Amazon AppConfig Agent offers the following additional features to help you retrieve configurations for your applications.
[Additional retrieval features](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-agent-how-to-use-additional-features.html) *Multi-account retrieval*: Use Amazon AppConfig Agent from a primary or *retrieval* Amazon Web Services account to retrieve configuration data from multiple vendor accounts. *Write configuration copy to disk*: Use Amazon AppConfig Agent to write configuration data to disk. This feature enables customers with applications that read configuration data from disk to integrate with Amazon AppConfig. *Write configuration to disk* is not designed as a configuration backup feature. Amazon AppConfig Agent doesn't read from the configuration files copied to disk. If you want to back up configurations to disk, see the `BACKUP_DIRECTORY` and `PRELOAD_BACKUP` environment variables for [Using Amazon AppConfig Agent with Amazon EC2](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-ec2.html#appconfig-integration-ec2-configuring) or [Using Amazon AppConfig Agent with Amazon ECS and Amazon EKS](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-containers-agent.html#appconfig-integration-containers-agent-configuring).
[Local development mode](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-agent-how-to-use-local-development.html)
Amazon AppConfig Agent supports a *local development mode*. If you enable local development mode, the agent reads configuration data from a specified directory on disk. It doesn't retrieve configuration data from Amazon AppConfig. You can simulate configuration deployments by updating files in the specified directory. We recommend local development mode for the following use cases: Test different configuration versions before deploying them using Amazon AppConfig. Test different configuration options for a new feature before commiting changes to your code repository. Test different configuration scenarios to verify they work as expected. | December 1, 2023 |
| [New code samples topic](#doc-history) | Added a new [code samples](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-code-samples.html) topic to this guide. The topic includes examples in Java, Python, and JavaScript for programmatically performing six common Amazon AppConfig actions. | November 17, 2023 |
| [Revised table of contents to better reflect Amazon AppConfig workflow](#doc-history) | Content in this user guide is now grouped under the headings Creating, Deploying, Retrieving, and Extending workflows. This organization better reflects the workflow for using Amazon AppConfig and aims to help make content more discoverable. | November 7, 2023 |
| [Payload reference added](#doc-history) | The [Creating a Lambda function for a custom Amazon AppConfig extension](https://docs.amazonaws.cn/appconfig/latest/userguide/working-with-appconfig-extensions-creating-custom-lambda) topic now includes a request and response payload reference. | November 7, 2023 |
| [New Amazon predefined deployment strategy](#doc-history) | Amazon AppConfig now offers and recommends the `AppConfig.Linear20PercentEvery6Minutes` predefined deployment strategy. For more information, see [Predefined deployment strategies](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-deployment-strategy.html#appconfig-creating-deployment-strategy-predefined). | August 11, 2023 |
| [Amazon AppConfig integration with Amazon EC2](#doc-history) | You can integrate Amazon AppConfig with applications running on your Amazon Elastic Compute Cloud (Amazon EC2) Linux instances by using Amazon AppConfig Agent. The agent supports x86\_64 and ARM64 architectures for Amazon EC2. For more information, see [Amazon AppConfig integration with Amazon EC2](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-ec2.html). | July 20, 2023 |
| [Amazon CloudFormation support for new Amazon AppConfig resources and a feature flag example](#doc-history) | Amazon CloudFormation now supports the [AWS::AppConfig::Extension](https://docs.amazonaws.cn/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-extension.html) and [AWS::AppConfig::ExtensionAssociation](https://docs.amazonaws.cn/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-extensionassociation.html) resources to help you get started with Amazon AppConfig extensions.
The [AWS::AppConfig::ConfigurationProfile](https://docs.amazonaws.cn/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-configurationprofile.html) and [AWS::AppConfig::HostedConfigurationVersion](https://docs.amazonaws.cn/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-hostedconfigurationversion.html) resources now include an example for creating a feature flag configuration profile in the Amazon AppConfig hosted configuration store. | April 12, 2023 |
| [Amazon AppConfig integration with Amazon Secrets Manager](#doc-history) | Amazon AppConfig integrates with Amazon Secrets Manager. Secrets Manager helps you to securely encrypt, store, and retrieve credentials for your databases and other services. Instead of hardcoding credentials in your apps, you can make calls to Secrets Manager to retrieve your credentials whenever needed. Secrets Manager helps you protect access to your IT resources and data by enabling you to rotate and manage access to your secrets.
When you create a freeform configuration profile, you can choose Secrets Manager as the source of your configuration data. You must onboard with Secrets Manager and create a secret before you create the configuration profile. For more information about Secrets Manager, see [What is Amazon Secrets Manager?](https://docs.amazonaws.cn/secretsmanager/latest/userguide/intro.html) in the *Amazon Secrets Manager User Guide*. For information about creating a configuration profile, see [Creating a freeform configuration profile](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-configuration-and-profile.html#appconfig-creating-configuration-and-profile-free-form-configurations). | February 2, 2023 |
| [Amazon AppConfig integration with Amazon ECS and Amazon EKS](#doc-history) | You can integrate Amazon AppConfig with Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Kubernetes Service (Amazon EKS) by using the Amazon AppConfig agent. The agent functions as a sidecar container running alongside your Amazon ECS and Amazon EKS container applications. The agent enhances containerized application processing and management in the following ways: The agent calls Amazon AppConfig on your behalf by using an Amazon Identity and Access Management (IAM) role and managing a local cache of configuration data. By pulling configuration data from the local cache, your application requires fewer code updates to manage configuration data, retrieves configuration data in milliseconds, and isn't affected by network issues that can disrupt calls for such data. The agent offers a native experience for retrieving and resolving Amazon AppConfig feature flags. Out of the box, the agent provides best practices for caching strategies, polling intervals, and local configuration data availability while tracking the configuration tokens needed for subsequent service calls. While running in the background, the agent periodically polls the Amazon AppConfig data plane for configuration data updates. Your containerized application can retrieve the data by connecting to localhost on port 2772 (a customizable default port value) and calling HTTP GET to retrieve the data. The Amazon AppConfig agent updates configuration data in your containers without having to restart or recycle those containers.
For more information, see [Amazon AppConfig integration with Amazon ECS and Amazon EKS](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-containers-agent.html). | December 2, 2022 |
| [New extension: Amazon AppConfig extension for CloudWatch Evidently](#doc-history) | You can use Amazon CloudWatch Evidently to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to your users. This helps you reduce risk and identify unintended consequences before you fully launch the feature. You can also conduct A/B experiments to make feature design decisions based on evidence and data.
The Amazon AppConfig extension for CloudWatch Evidently allows your application to assign variations to user sessions locally instead of by calling the [EvaluateFeature](https://docs.amazonaws.cn/cloudwatchevidently/latest/APIReference/API_EvaluateFeature.html) operation. A local session mitigates the latency and availability risks that come with an API call. For information about how to configure and use the extension, see [Perform launches and A/B experiments with CloudWatch Evidently](https://docs.amazonaws.cn/AmazonCloudWatch/latest/monitoring/CloudWatch-Evidently.html) in the *Amazon CloudWatch User Guide*. | September 13, 2022 |
| [Deprecation of the `GetConfiguration` API action](#doc-history) | On Nov 18, 2021, Amazon AppConfig released a new data plane service. This service replaces the previous process of retrieving configuration data by using the `GetConfiguration` API action. The data plane service uses two new API actions, [StartConfigurationSession](https://docs.amazonaws.cn/appconfig/2019-10-09/APIReference/API_appconfigdata_StartConfigurationSession.html) and [GetLatestConfiguration](https://docs.amazonaws.cn/appconfig/2019-10-09/APIReference/API_appconfigdata_GetLatestConfiguration.html). The data plane service also uses [new endpoints](https://docs.amazonaws.cn/general/latest/gr/appconfig.html#appconfigdata_data_plane).
For more information, see [About the Amazon AppConfig data plane service](https://docs.amazonaws.cn/appconfig/latest/userguide/about-data-plane.html). | September 13, 2022 |
| [New version of the Amazon AppConfig Agent Lambda extension](#doc-history) | Version 2.0.122 of the Amazon AppConfig Agent Lambda extension is now available. The new extension uses different Amazon Resource Names (ARNs). For more information, see [Amazon AppConfig Agent Lambda extension release notes](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html#appconfig-integration-lambda-extensions-versions-release-notes). | August 23, 2022 |
| [Launch of Amazon AppConfig extensions](#doc-history) | An extension augments your ability to inject logic or behavior at different points during the Amazon AppConfig workflow of creating or deploying a configuration. You can use Amazon-authored extensions or create your own. For more information, see [Working with Amazon AppConfig extensions](https://docs.amazonaws.cn/appconfig/latest/userguide/working-with-appconfig-extensions.html). | July 12, 2022 |
| [New version of the Amazon AppConfig Agent Lambda extension](#doc-history) | Version 2.0.58 of the Amazon AppConfig Agent Lambda extension is now available. The new extension uses different Amazon Resource Names (ARNs). For more information, see [Available versions of the Amazon AppConfig Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | May 3, 2022 |
| [Amazon AppConfig integration with Atlassian Jira](#doc-history) | Integrating with Atlassian Jira allows Amazon AppConfig to create and update issues in the Atlassian console whenever you make changes to a [feature flag](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-configuration-and-profile.html#appconfig-creating-configuration-and-profile-feature-flags) in your Amazon Web Services account for the specified Amazon Web Services Region. Each Jira issue includes the flag name, application ID, configuration profile ID, and flag values. After you update, save, and deploy your flag changes, Jira updates the existing issues with the details of the change. For more information, see [Amazon AppConfig integration with Atlassian Jira](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-jira.html). | April 7, 2022 |
| [General availability of feature flags and Lambda extension support for ARM64 (Graviton2) processors](#doc-history) | With Amazon AppConfig feature flags, you can develop a new feature and deploy it to production while hiding the feature from users. You start by adding the flag to Amazon AppConfig as configuration data. Once the feature is ready to be released, you can update the flag configuration data without deploying any code. This feature improves the safety of your dev-ops environment because you don't need to deploy new code to release the feature. For more information, see [Creating a feature flag configuration profile](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-configuration-and-profile.html#appconfig-creating-configuration-and-profile-feature-flags).
General availability of feature flags in Amazon AppConfig includes the following enhancements: The console includes an option to designate a flag as a *short term* flag. You can filter and sort the list of flags on short-term flags. For customers using feature flags in Amazon Lambda, the new Lambda extension allows you to call individual feature flags by using an HTTP endpoint. For more information, see see [Retrieving one or more flags from a feature flag configuration](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-retrieving-flags.html).
This update also provides support for Amazon Lambda extensions developed for ARM64 (Graviton2) processors. For more information, see see [Available versions of the Amazon AppConfig Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions-versions.html). | March 15, 2022 |
| [The GetConfiguration API action is deprecated](#doc-history) | The `GetConfiguration` API action is deprecated. Calls to receive configuration data should use the `StartConfigurationSession` and `GetLatestConfiguration` APIs instead. For more information about these APIs and how to use them, see [Retrieving the configuration](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-retrieving-the-configuration.html). | January 28, 2022 |
| [New region ARN for Amazon AppConfig Lambda extension](#doc-history) | Amazon AppConfig Lambda extension is available in the new Asia Pacific (Osaka) region. The Amazon Resource Name (ARN) is required to create a Lambda in the region. For more information about the Asia Pacific (Osaka) region ARN, see [Adding the Amazon AppConfig Lambda extension](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions.html#appconfig-integration-lambda-extensions-enabling). | March 4, 2021 |
| [Amazon AppConfig Lambda extension](#doc-history) | If you use Amazon AppConfig to manage configurations for a Lambda function, then we recommend that you add the Amazon AppConfig Lambda extension. This extension includes best practices that simplify using Amazon AppConfig while reducing costs. Reduced costs result from fewer API calls to the Amazon AppConfig service and, separately, reduced costs from shorter Lambda function processing times. For more information, see [Amazon AppConfig integration with Lambda extensions](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-integration-lambda-extensions.html). | October 8, 2020 |
| [New section](#doc-history) | Added a new section that provides instructions for setting up Amazon AppConfig. For more information, see [Setting up Amazon AppConfig](https://docs.amazonaws.cn/appconfig/latest/userguide/setting-up-appconfig.html). | September 30, 2020 |
| [Added commandline procedures](#doc-history) | Procedures in this user guide now include commandline steps for the Amazon Command Line Interface (Amazon CLI) and Tools for Windows PowerShell. For more information, see [Working with Amazon AppConfig](https://docs.amazonaws.cn/appconfig/latest/userguide/appconfig-creating-application.html). | September 30, 2020 |
| [Launch of Amazon AppConfig user guide](#doc-history) | Use Amazon AppConfig, a tool in Amazon Systems Manager, to create, manage, and quickly deploy application configurations. Amazon AppConfig supports controlled deployments to applications of any size and includes built-in validation checks and monitoring. You can use Amazon AppConfig with applications hosted on EC2 instances, Amazon Lambda, containers, mobile applications, or IoT devices. | July 31, 2020 |