AWS CodePipeline Supports AWS AppConfig as a New Deploy Action type

Posted on: Jun 26, 2020

AWS CodePipeline announces integration with AWS AppConfig to enable AWS customers to deliver features and updates safely, rapidly and reliably to their applications. AWS customers can now deploy application configurations using AppConfig in a validated, controlled and monitored way and automate orchestration of these deployments across deploy stages with AWS CodePipeline.  

Teams often release new features by including application configuration into application code and deploying configuration with code deployments. Code deployments across multiple environments, applications or regions are time consuming and this process adds time to the release process and delays value to the end customers. AWS AppConfig allows customers to decouple their configuration changes from code deployments. This launch enables customers to deploy configuration changes across environments, applications and regions, without the need for deploying code. This reduces the duration of deployments while maintaining the same safeguards and the operational scrutiny as code deployments.  

With AppConfig’s integration with CodePipeline, customers can source configuration from AWS CodeCommit, S3 and GitHub and can deploy configurations to their applications at runtime. Customers can also validate configuration data to ensure that the data is syntactically and semantically correct before making it available to the application. With AppConfig, customers can define deployment strategies to roll out a configuration over a defined time period. Customers can then choose AppConfig as a deployment action within AWS CodePipeline and deploy configurations stored in source revision across environments within the specified application while monitoring the application to catch any errors. In case of an error, AppConfig rolls back the changes immediately to minimize the impact to the end users.  

This feature is available at no extra charge. Customers only pay for the resources they use. 

This feature is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), EU (Stockholm) and South America (São Paulo).  

To get started, see the following resources: