---
title: "AWS configuration for London POP"
canonical: "https://docs.aryaka.com/space/KNOW/1294761994/AWS%20configuration%20for%20London%20POP"
format: markdown
---
Amazon's AWS Direct Connect is used to connect the Amazon Web Services (AWS) instance to a customer branch office, datacenter, or other geographic location using a dedicated network connection. Aryaka offers optimized access to AWS resources by providing Direct Connect at our POPs. This AWS integration is typically achieved using a third-party solution from Equinix known as the Equinix Cloud Exchange (ECX) except for implementations that use the EU West (Ireland) AWS region and Aryaka's London POP. The following table lists all Aryaka POPs offering Direct Connect and the corresponding AWS region: Amazon AWS Region Nearest Aryaka POP Location Integration Type US West (Northern California) San Jose, CA ECX US East (Northern Virginia) Ashburn, VA ECX EU West (Ireland) London Direct L2 link Asia Pacific (Singapore) Singapore ECX Asia Pacific (Tokyo) Tokyo ECX This document describes the procedures that Aryaka customers must perform to enable Direct Connect peering for their configuration instance when connecting to London. Prerequisites To configure an AWS instance to connect to Aryaka with Direct Connect using ECX, you must provide the following information to Aryaka technical support team: Amazon AWS location Amazon AWS account number Amazon AWS local subnets This information is used by Aryaka to configure a hosted connection and two virtual interfaces, which are then visible on the AWS Direct Connect console with the state  Pending Acceptance . While we have made every effort possible to ensure accurate descriptions and screen captures at time of publication, updates to the third-party UI are beyond our control. Refer to the third-party documentation to ensure you have the most recent information. Accept the virtual interface Log in to the AWS Direct Connect console at  https://console.aws.amazon.com/directconnect/v2/home . Click  Virtual Interfaces  in the left navigation pane, click the Aryaka virtual interfaces, and then select  View Details . Click  Accept . The Accept Virtual Interface dialog appears. Select a virtual private gateway that maps to the VPC to be accessed, and then click  Accept virtual interface . The accepted virtual interface appears with its state as Down until Aryaka completes the configuration. Contact  support@aryaka.com , and inform them that you are done with AWS virtual interface configuration. After Aryaka support completes the configuration, the virtual interface becomes accessible.  See the  AWS documentation  for additional information and possible UI updates. Continue to the next section to route traffic to the virtual interface. Route traffic to remote sites To route traffic to the remote sites and the virtual interface Log in to the AWS Direct Connect console at  https://console.aws.amazon.com/directconnect/v2/home . Click  Services  >  VPC  in the navigation pane. Click  Route Tables  and select the route table for the VPC that is being accessed through Aryaka. Select  Routes  in the lower panel and add the routes for the remote offices. Select the virtual gateway that was set up for Aryaka as the target.    In this topic Related topics Accepting a hosted virtual interface  ( AWS Direct Connect User Guide )