ARCHLEXOSS

Cloudflare · Reliability & Scaling

Cloudflare AWS/GCP Origin Steering

Preferred AWS and fallback GCP origin intent, without asserting verified health or steering policy. This diagram is written in ArchLex and passes Cloudflare provider checks.

Edit in the playgroundCloudflare diagrams as code
Cloudflare AWS/GCP Origin Steering: Preferred AWS and fallback GCP origin intent, without asserting verified health or steering policyCloudflare AWS/GCP Origin Steering: Preferred AWS and fallback GCP origin intent, without asserting verified health or steering policy
provider cloudflare
direction LR
domain: dns["app.example.com"]
steering: load-balancing["Origin steering"]
aws-origin: aws.alb["AWS preferred endpoint"]
gcp-origin: gcp.cloud-run["GCP fallback endpoint"]
domain ->|DNS record selects entry point| steering
steering -[routes]->|Preferred pool endpoint; health unverified| aws-origin
steering -[routes]->|Fallback pool endpoint; policy unverified| gcp-origin

What is in this diagram.

Resources

Relationships

Render it yourself.

Save the source as cloudflare-aws-gcp-failover.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.

npx @archlex/cli render cloudflare-aws-gcp-failover.arch --output cloudflare-aws-gcp-failover.svg

All examples