---
title: Unifying Ingress Across Distributed AWS Compute Environments
description: This guide helps you architect a hub-and-spoke pattern to unify ingress operations across EC2, ECS, and EKS compute environments.
image: https://info.traefik.io/hubfs/Unifying%20Ingress%20-%20Thumbnail@2x.jpg
---

[![containous-logo](https://info.traefik.io/hubfs/TraefikLabs-horizontal-logo-black@2x.png)](https://traefik.io)

Guide

# Unifying Ingress Across Distributed AWS Compute Environments

 How the Traefik AWS Elastic Provider Delivers Unified Ingress for EKS, EC2, and ECS at Scale

![Unifying Ingress Across Distributed AWS](https://info.traefik.io/hubfs/Unifying%20Ingress%20-%20Cover%20Image%20LP.png)

Running workloads across AWS EC2, EKS, and ECS shouldn't mean managing different ingress controllers in each environment. But that's exactly what many organizations find themselves doing.

### Introducing the Traefik Unified Ingress

We put together a builder's guide showing you exactly how to use Traefik as a Unified Ingress in a hub-and-spoke pattern to centralize traffic management and preserve platform independence.

In this guide, you'll explore:

- The ingress challenges of working in heterogeneous AWS environments
- How a hub-and-spoke pattern can solve these challenges
- How the Traefik AWS Elastic Provider makes this model possible out of the box
- Real-world use cases and sequence diagrams

Fill out the form now to get your copy.

### Download the Guide

- © Traefik Labs Inc. 2023
- [Privacy Policy](https://traefik.io/legal/privacy-and-cookie-policy/)

- [![black-envelope-symbol](https://info.traefik.io/hubfs/mail-black-envelope-symbol.svg)](mailto:sales@traefik.io)
- [![linkedin-logo](https://info.traefik.io/hubfs/linkedin-logo.svg)](https://www.linkedin.com/company/traefik/)
- [![twitter-logo](https://info.traefik.io/hubfs/twitter.svg)](https://twitter.com/traefik)

![](https://static.scarf.sh/a.png?x-pxid=81886af1-fa2a-4fcf-8d80-093fe6fd8a6e)