After CI/CD, there's now Continuous Configuration
summary
Shows that runtime config is a distinct deployment axis: Amazon uses AWS AppConfig (internal since 2016, public 2019) to push JSON config and feature flags to services, used by 4,000 teams across Amazon. Demo uses a serverless API (API Gateway + Lambda with an AppConfig extension), shows staged deployments, bake time monitoring via CloudWatch and an auto-rollback on alarm. Validators catch syntax/semantic errors; configuration changes succeed and roll back when alarms fire.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:20Early days of Amazon
- 2:54Continuous Integration
- 4:40Continuous Delivery and Deployment
- 8:55Continuous Configuration
- 16:27App Configuration
- 17:27AWS App Configuration
- 18:19Validators
- 19:22Monitoring and rollback
- 20:18App config
- 22:09AWS Console
- 23:17AppConfig
- 24:48Configuration Profile
- 26:49New Version
- 27:27Deployment Strategy
- 29:43Alarms
- 30:37New Deployment
- 32:52Use AWS CLI
- 33:37Starting the final phase
- 34:07Starting the deployment
- 34:45CloudWatch Alarm
- 35:37Looking forward
- 37:35Additional resources
- 37:57Conclusion
- 38:39QA
related talks
28mContinuous everything: Moving to DevOps on AWS
23mCI/CD at Scale: Best practices with AWS DevOps Services
25mCI/CD in AWS Cloud
30mContinuous Integration and Delivery for serverless apps
27mLevel Up Your CI/CD With Smart AWS Feature Flags
41mCI/CD in the Serverless Era
41mAll Things Continuous
23mCI/CD at Scale: Best Practices with AWS DevOps Services