# Equal-Cost Multipath Routing

Equal-Cost Multipath Routing distributes traffic across multiple eligible network paths that have equal routing preference to the same destination.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/equal-cost-multipath-routing

> Equal-Cost Multipath Routing, commonly called ECMP, allows a router to use several equivalent next hops rather than selecting only one. It can improve aggregate bandwidth utilization and resilience, but it does not normally combine multiple links into a faster path for a single traffic flow.

Practice exams covering Equal-Cost Multipath Routing: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of Equal-Cost Multipath Routing

ECMP combines equally preferred routes for aggregate capacity and resilience, subject to flow hashing, routing eligibility, failure capacity, and end-to-end platform support.

1. **Equal routing preference**: Only routes that qualify as equally preferred under the platform’s routing rules can share traffic. Matching destination prefixes, routing metrics, and relevant BGP attributes matter; equal link speeds alone do not establish ECMP.
2. **Flow-based traffic distribution**: Most implementations hash flow attributes to select a next hop and keep that flow on one path. Aggregate throughput can increase across many flows, but an individual flow generally cannot exceed one path’s capacity.
3. **Active-active bandwidth utilization**: ECMP can use several eligible paths concurrently instead of reserving all secondary paths for standby operation. Verify actual per-path utilization because hashing does not guarantee equal bandwidth consumption.
4. **Failure-aware capacity planning**: When a route is withdrawn, traffic can move to remaining eligible paths after failure detection and routing convergence. Provision enough surviving capacity to handle the required workload, rather than assuming successful failover prevents congestion.
5. **End-to-end implementation requirements**: Cloud gateways, customer routers, route advertisements, and security appliances must support the intended design. Forward and return path selection can differ, which matters when traffic crosses stateful devices.
6. **Workload-driven cost optimization**: Compare multiple smaller paths with a higher-capacity path using aggregate demand, single-flow requirements, and total connectivity charges. Additional tunnels or circuits increase useful capacity only when routing eligibility and workload parallelism allow them to be used.

## Cloud services for Equal-Cost Multipath Routing

AWS Site-to-Site VPN provides encrypted hybrid paths, while AWS Transit Gateway can distribute traffic across eligible BGP-advertised VPN paths using ECMP. AWS Direct Connect offers private connectivity whose port capacity and supported multipath arrangements provide another bandwidth-sizing option. Compare these designs using aggregate throughput, individual-flow requirements, resilience, and total charges. Customer routers must advertise compatible routes and support the intended forwarding behavior. A virtual private gateway is not interchangeable with Transit Gateway for VPN bandwidth aggregation because it does not support VPN ECMP.

- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: AWS Transit Gateway supports ECMP across eligible BGP-based Site-to-Site VPN tunnels when VPN ECMP support is enabled. It provides the cloud-side routing capability needed to use multiple qualifying VPN paths concurrently rather than relying only on standby connectivity.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: AWS Site-to-Site VPN supplies encrypted tunnels that can participate in ECMP through Transit Gateway when dynamic routing and the required route attributes are configured. VPN connections attached to a virtual private gateway do not support ECMP, and static-routing VPN connections do not provide Transit Gateway VPN ECMP.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: AWS Direct Connect provides private connectivity with provisioned bandwidth, and multiple connections can support active-active ECMP in supported gateway and virtual-interface configurations. Eligible routes require compatible BGP attributes; purchasing additional circuits alone does not guarantee traffic sharing or increased single-flow throughput.

## Equal-Cost Multipath Routing exam questions

Real practice exam questions on Equal-Cost Multipath Routing, with the correct answer and its explanation.

### Question 1 (SAA-C03)

**Question:**

A company uses two AWS Site-to-Site VPN connections with standard tunnels to connect its data center to an AWS Transit Gateway. VPN ECMP support is enabled, and all four tunnels are operational. The customer routers advertise 10.40.0.0/16 through every tunnel with identical BGP path attributes. They also advertise 10.40.8.0/24 through both tunnels of only the first VPN connection. All these routes propagate into the transit gateway route table used by the application VPCs.

An application sends data from AWS to hundreds of servers in 10.40.8.0/24 through thousands of independent TCP connections. Monitoring shows that only the first VPN connection carries this traffic. Testing confirms that each tunnel can sustain 800 Mbps for this workload and that traffic distributes effectively among eligible paths. The internet circuits, customer routers, and application endpoints have sufficient capacity.

The company needs 2 Gbps of aggregate throughput during normal operation. The more-specific route is not required for traffic isolation or another routing policy. Which change meets the requirement with the lowest additional recurring network cost?

**Correct answer:** Remove the advertisements for 10.40.8.0/24 while retaining the identical 10.40.0.0/16 advertisements through all four tunnels.

**Explanation:** The /24 route currently takes precedence over the /16 routes, restricting this traffic to the first VPN connection. Removing the unnecessary /24 advertisements makes the equally preferred /16 paths eligible across all four tunnels. The tested aggregate capacity is 3.2 Gbps across many independent flows, exceeding the 2 Gbps requirement without adding connections.

### Question 2 (ANS-C01)

**Question:**

A company has two 10-Gbps AWS Direct Connect connections on separate AWS devices at the same Direct Connect location. Each connection has a private virtual interface connected to the same Direct Connect gateway, which is associated with the company's VPC virtual private gateway. Both virtual interfaces advertise the same on-premises prefixes and receive the same VPC prefixes.

The company currently uses the connections in an active/passive configuration. Its routers prepend the customer ASN three additional times when advertising on-premises prefixes over the standby connection. Advertisements over both connections carry BGP community 7224:7200. The customer routers assign equal local preference to received VPC routes, but BGP multipath is disabled. All other relevant BGP attributes are equal.

The company wants both connections to carry traffic concurrently in both directions. Its workload contains thousands of independent flows, and aggregate demand can exceed 10 Gbps. Either connection must continue providing connectivity if the other fails. The customer routers support BGP multipath.

Which routing change meets these requirements?

**Correct answer:** Remove the AS_PATH prepending from the standby connection, retain community 7224:7200 on both connections, and enable BGP multipath on the customer routers for the equally preferred VPC routes.

**Explanation:** Removing the prepending makes the advertised AS_PATH attributes equal. With equal Direct Connect local-preference communities and otherwise equal attributes, the paths are eligible for AWS-side ECMP. Enabling BGP multipath on the customer routers allows the equally preferred VPC routes to support load sharing in the opposite direction. Many independent flows can use aggregate capacity across both connections, while BGP route withdrawal provides failover. An individual flow is not guaranteed to exceed one connection's capacity.

## Practice Equal-Cost Multipath Routing in a full exam

Questions on Equal-Cost Multipath Routing in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 4 questions

## What is Equal-Cost Multipath Routing

Equal-Cost Multipath Routing is a forwarding technique that uses multiple equally preferred routes to the same destination prefix. Here, “cost” means routing preference or metric, not the financial price of a connection. Depending on the routing protocol and implementation, routes must have compatible metrics and path attributes before they can participate in ECMP. Two connections reaching the same network do not automatically form an ECMP group.

Most implementations distribute traffic using a hash of packet fields, such as source and destination addresses, protocol, and transport ports. Packets belonging to a flow normally follow the same path, reducing packet reordering. With enough independent flows, several links can carry traffic simultaneously. However, traffic distribution is not necessarily even: a few large transfers can saturate one path while another remains underused.

For example, two eligible 1 Gbps paths can provide close to 2 Gbps of aggregate capacity under favorable conditions when many flows are distributed across them. A single TCP connection usually remains limited to one path’s capacity. Protocol overhead, packet loss, latency, encryption processing, and endpoint performance can reduce achieved throughput further. Adding paths therefore helps a workload containing many independent connections more predictably than a workload consisting of one large transfer.

In cloud networks, ECMP commonly applies to hybrid connectivity through multiple VPN tunnels or private connectivity circuits. Dynamic routing, frequently using Border Gateway Protocol, advertises destination prefixes and withdraws routes when connectivity fails. The cloud routing service and the customer router must both support the intended multipath behavior. Forward and return traffic are selected independently, so engineers must also consider asymmetric routing through stateful firewalls or other appliances.

For AWS architectures, AWS Transit Gateway supports ECMP across eligible dynamically routed AWS Site-to-Site VPN tunnels when VPN ECMP support is enabled. Static-routing VPN connections do not support this ECMP capability. A virtual private gateway does not support ECMP for Site-to-Site VPN, so simply adding VPN connections to that gateway does not aggregate their bandwidth. The two tunnels included with a VPN connection provide redundancy, but their presence alone does not establish that both will carry traffic concurrently.

Bandwidth selection should start with aggregate demand, largest-flow requirements, and the capacity required during a failure. Multiple VPN paths can be appropriate when parallel application traffic needs more aggregate throughput than one tunnel provides. A higher-speed private connection, such as AWS Direct Connect, may be more appropriate when a workload needs greater per-path capacity or more consistent network performance. Multiple Direct Connect connections can also support ECMP in supported configurations, but their routing attributes and gateway topology must qualify.

Cost optimization requires comparing the complete architecture rather than counting links alone. Include VPN connection charges, transit processing, private circuit and port charges, data transfer, customer equipment, and operational effort. Also avoid provisioning only enough combined capacity for normal operation: if two paths are both nearly full, losing one causes congestion even though routing successfully fails over. Validate the design with multiple concurrent flows, inspect utilization per path, and test route withdrawal and recovery before relying on the advertised aggregate bandwidth.

## Learn Equal-Cost Multipath Routing in lessons

1 short lesson on Equal-Cost Multipath Routing in 1 certification course.

- SAA-C03: Equal-Cost Multipath Routing: aggregate bandwidth across VPN paths (Premium), https://app.blowstack.com/lessons/equal-cost-multipath-routing-aggregate-bandwidth-across-vpn-paths-saa-c03
