Feature Description
Implement phased migration strategy allowing parallel operation of Lambda and container versions with shadow testing and gradual rollout capabilities.
Use Case
Organizations need risk-free adoption path to container version while maintaining existing Lambda deployments, enabling them to validate container performance before commitment.
Proposed Solution
Phase 1: Maintain Lambda unchanged, develop container with same inputs/outputs
Phase 2: Deploy container to non-production for shadow testing
Phase 3: Gradual rollout starting with non-critical Config rules
Phase 4: Optional Lambda decommissioning based on customer choice
Alternatives Considered
- Direct cutover - too risky
- Lambda-only approach - limits monetization opportunity
Additional Context
- Both versions remain available as deployment options
- Container version enables AWS Marketplace distribution
- 1-2 week monitoring per rule during migration
- Maintain rollback capability
Feature Description
Implement phased migration strategy allowing parallel operation of Lambda and container versions with shadow testing and gradual rollout capabilities.
Use Case
Organizations need risk-free adoption path to container version while maintaining existing Lambda deployments, enabling them to validate container performance before commitment.
Proposed Solution
Phase 1: Maintain Lambda unchanged, develop container with same inputs/outputs
Phase 2: Deploy container to non-production for shadow testing
Phase 3: Gradual rollout starting with non-critical Config rules
Phase 4: Optional Lambda decommissioning based on customer choice
Alternatives Considered
Additional Context