Level Up Your CI/CD With Smart AWS Feature Flags
summary
Claim: dynamic feature flags reduce rollback time and enable canary and A/B flows. Implementation uses AWS AppConfig for managed, FedRAMP High configuration with JSON schema validation and canary deploys, and an SDK in Lambda Powertools that adds an in‑memory cache and evaluation engine. Built smart rules that match request context for A/B tests, supports Lambda and containers, trades cache TTL against freshness, and proves safe automatic rollback and easy retirement of flags.
AI-written summary · about
chapters (13)
- 0:00Smart feature flags on AWS
- 1:39Feature flags in CI/CD
- 3:47Robust feature flag solution
- 6:57Static vs dynamic config
- 9:47AWS App Config setup
- 12:40App Config console walkthrough
- 13:22Evaluating flags with Lambda Powertools
- 15:08Feature flags implementation
- 16:34Smart flags for A/B testing
- 21:10Caching and cost optimization
- 22:16Best practices for feature flags
- 25:46Retiring feature flags
- 26:30Summary
related talks
08mThe Art of Feature Flagging
41mFeature Flags: Separate Deployment from Feature Release
45mAfter CI/CD, there's now Continuous Configuration
44mFlagging features — a DevOps approach to continuous release
50mThe Story of One Feature Flag
01h 09mFeature flags: the toggle, the A/B test and the canary
07mKeep Calm and Deploy On: Creating Safer Releases with Feature Flags
40mContinuous Delivery for Python with Feature Flags