Hybrid cloud infrastructure
Anywhere Mesh
AWS, connected to where you run.
Connect AWS to containers on your own hardware. Host-based routing and health-aware proxying connect your local services to your AWS environment.
← All projects
Capabilities
What it does
- Terminates ALB HTTP on the ingress and registers clients over WebSockets
- Routes traffic by Host header to healthy, registered clients
- Proxies requests to your on-host services (e.g. http://127.0.0.1:3000)
- Exports health and metrics for observability
- Designed for ECS Anywhere tasks on your own networks
How it fits together
Architecture, at a glance.
Getting Started
- Deploy the ingress in AWS (ALB + service) using our CDK templates or your stack.
- Start the mesh client next to your service and register a host name.
- Point your DNS record to the ALB and route traffic by Host header.
- Verify health and metrics, then roll out to additional hosts.
FAQ
What environments does this support?
ECS Anywhere on your own hardware, edge sites, or other clouds. Keep compute where it makes sense, while using AWS networking and security at the edge.
How is traffic routed?
Clients register with the ingress over WebSockets and advertise a host. Incoming ALB traffic is routed by the Host header to the matching client and proxied to its local service.
Is this production ready?
The core is built in Rust with health checks and metrics. We provide guidance and support to harden for your environment.
Built by KloudCover