AWS Direct Connect: launches, PoP expansion, and partner programs (2011–2021)

  1. AWS Direct Connect service is introduced

    Labels: AWS Direct, Equinix Ashburn

    AWS announced AWS Direct Connect as a way for enterprises to create a dedicated network connection from a data center, office, or colocation facility to AWS, instead of using the public internet. The first live location was Equinix in Ashburn, Virginia, providing connectivity to the US East (N. Virginia) Region. This launch set the foundation for later expansion in both global points of presence (PoPs) and partner-delivered connectivity models.

  2. First major global location expansion goes live

    Labels: Los Angeles, London PoP, Singapore PoP

    AWS added four new AWS Direct Connect locations: Los Angeles, London, Singapore, and Tokyo. These new sites extended Direct Connect beyond the initial Virginia location and provided dedicated connectivity paths into multiple AWS Regions in the US, Europe, and Asia Pacific. The expansion made Direct Connect more practical for organizations operating outside the US East region.

  3. Partner Network connectivity offerings broaden access

    Labels: AWS Partner, Telecom providers

    Telecom and network providers began packaging connectivity to AWS Direct Connect locations as a service, using the AWS Partner Network (APN). This helped customers procure and implement the “last mile” circuits from their own sites to an AWS Direct Connect facility. The growing partner ecosystem made Direct Connect accessible to more organizations that did not already have presence in major colocation hubs.

  4. Hosted connections become a common partner-led model

    Labels: Hosted connections, APN Partners

    AWS documented a model where customers can use an AWS Direct Connect Partner to obtain a hosted connection rather than ordering a dedicated port directly from AWS. Hosted connections let partners provision a range of bandwidth options for customers and deliver connectivity through partner-managed infrastructure at a Direct Connect location. This model became especially important for smaller or faster deployments that did not require a full dedicated port.

  5. Equinix expands Direct Connect availability in Europe

    Labels: Equinix, London PoP

    Equinix announced expanded AWS Direct Connect availability across its facilities, including London as another site in Europe offering native Direct Connect. The announcement also noted earlier availability in Frankfurt and described how customers could get more direct, consistent connectivity into AWS compared with indirect “tethered” approaches. Colocation expansions like this helped increase PoP density within key enterprise metros.

  6. Edge and metro PoPs extend Direct Connect reach

    Labels: Edge PoPs, EdgeConneX Portland

    AWS Direct Connect locations continued to spread beyond the earliest major hubs, including deployments in additional US metros. For example, EdgeConneX announced a Direct Connect location in Portland, Oregon, positioned as bringing cloud access closer to the “edge” of networks. As more metro sites came online, customers had more options to design lower-latency and more resilient connectivity.

  7. Link Aggregation Groups (LAG) are launched

    Labels: Link Aggregation, LACP

    AWS introduced Link Aggregation Groups (LAG) for 1 Gbps and 10 Gbps Direct Connect connections. LAG lets customers treat multiple physical connections as a single logical connection using LACP, which can simplify configuration and reduce the number of BGP sessions to manage. This feature supported scaling bandwidth while improving operational simplicity and visibility into redundancy.

  8. Direct Connect Gateway enables multi-Region VPC access

    Labels: Direct Connect, Multi-Region

    AWS announced Direct Connect Gateway to let customers connect from a Direct Connect location to VPCs across multiple AWS Regions (except China) using a single gateway construct. This reduced the need for separate BGP configurations per Region and helped customers build more global network designs. The gateway marked a shift from a region-by-region connectivity product toward a more globally managed service.

  9. Redesigned Direct Connect console supports global management

    Labels: Direct Connect, Global management

    AWS released a redesigned AWS Direct Connect console and described Direct Connect’s evolution from a regional service to a global one. The announcement highlighted that with Direct Connect gateway, customers could access any AWS Region (except China) from any Direct Connect location. The updated console aimed to make connections, gateways, and related resources easier to manage in one place.

  10. Service Delivery Program formalizes validated Direct Connect partners

    Labels: Service Delivery, Validated partners

    AWS introduced the AWS Direct Connect Service Delivery Program to identify partners that had been validated to deliver Direct Connect services. The program emphasized partner capability for higher-capacity hosted connections (greater than 500 Mbps) and monitoring of the partner-to-AWS interconnect. This milestone made partner roles clearer and gave customers a more structured way to choose providers for Direct Connect deployments.

  11. MACsec encryption support is added for Direct Connect

    Labels: MACsec, Layer 2

    AWS added support for MACsec (IEEE 802.1AE) on Direct Connect, enabling point-to-point Layer 2 encryption between customer equipment and AWS at select locations. The initial capability focused on dedicated connections at 10 Gbps and 100 Gbps, providing an option for customers with stronger on-the-wire security needs. This expanded Direct Connect from “private connectivity” toward “private connectivity with link-level encryption.”

  12. Direct Connect SiteLink is introduced

    Labels: Direct Connect, Private virtual

    AWS introduced Direct Connect SiteLink, an optional feature for private virtual interfaces that enables connectivity between Direct Connect PoPs using AWS’s network without requiring traffic to route through an AWS Region. This helped some customers use AWS’s backbone for site-to-site connectivity patterns while keeping traffic off the public internet. The release highlighted an additional evolution: Direct Connect was no longer only “to a Region,” but could also support certain PoP-to-PoP connectivity designs.

First
Last
StartEnd
Last Updated:Jan 1, 1980
Privacy Policy

AWS Direct Connect: launches, PoP expansion, and partner programs (2011–2021)