01
Data-driven rollout
Change the active colour by updating a parameter.
Component 16
Shift CloudFront requests between deployments at the edge, without an apply.
Status
Available component
Deployment scope
Global edge
Inputs in, outputs out. Illustrative wiring, not a standalone deployment.
Supply the deployment names and an initial active deployment. The router manages the Parameter Store entry, the sync Lambda, the key-value store, and the CloudFront Function. Configure provider requirements and credentials in your root module; check the documentation for all required inputs and version changes.
module "edge_router" {
source = "pomo-studio/cloudfront-edge-router/aws"
version = "~> 0.1"
name = "orders"
deployments = ["blue", "green"]
active_deployment = "blue"
weight = 0
}Key inputs
Useful outputs
01
Change the active colour by updating a parameter.
02
Send a percentage to the next colour, or pin a viewer by cookie.
03
Route each request without a round trip to the origin.
Shift traffic between two backend deployments at the edge, with canary weighting and cookie pinning.
Keep routing and rollout configuration in Parameter Store and project it to the edge.
Built with