--- title: "AWS ECX configuration" canonical: "https://docs.aryaka.com/space/KNOW/1294663693/AWS%20ECX%20configuration" 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 and providing integration using a third-party solution from Equinix known as the Equinix Cloud Exchange (ECX). Direct Connect is available through Aryaka for the following AWS regions: Amazon AWS Region Nearest Aryaka POP Location US East -N. Virginia (us-east-1) Ashburn US East -N. Virginia (us-east-1) Dallas New Jersey US-East-Ohio (us-east-2) Chicago US West (Oregon) (us-west-2) Seattle US West -N. California (us-west-1) San Jose São Paulo São Paulo Amsterdam-EU-Frankfurt (eu-central-1) Amsterdam EU-Dublin Dublin Frankfurt (eu-central-1) Frankfurt EU-London London Sydney (ap-southeast-2) Sydney Tokyo Asia Pacific-North East (ap-northeast-1) Tokyo China (Beijing) (cn-north-1) Beijing Singapore-Asia Pacific-South East (ap-southeast-1) Singapore This document describes the procedures that Aryaka customers must perform to enable Direct Connect peering for their configuration instance when connecting through ECX. 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 two hosted connections, which are then visible on the AWS management 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 hosted connection Log in to the AWS Direct Connect console at  https://console.aws.amazon.com/directconnect/v2/home . Click Connections in the left navigation pane, then click the Aryaka hosted connections. Click the checkbox for each Aryaka connection, then select Accept Connection .  See the AWS documentation  for additional information and possible UI updates. Continue to the next section to add a virtual interface to each of the accepted hosted connections. Create a hosted 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, then click Create Virtual Interface . Select Public , Transit or Private for the virtual interface type. Complete the following fields in the Virtual Interface Settings and Additional Settings panes: Virtual Interface Name—Enter a descriptive interface name. Virtual Interface Owner—Enter a user name, user ID, or something else to identify this as your AWS account. VGW—Enter the virtual gateway of the VPC that you want to attach. BGP ASN—Enter 11179. Auto-generate peer IPs—Clear this checkbox. Your router peer IP—Enter the first IP of /30 subnet. Amazon router peer IP—Enter the second IP of /30 subnet. Use the default settings for the remaining attributes. See the AWS Documentation  for additional information and possible UI updates. Continue to the next section to send the virtual interface configuration to Aryaka support. Send router configuration to Aryaka After the virtual interface is configured, its status is Down (unavailable) until Aryaka support completes the corresponding configuration. 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, then click Create Virtual Interface . Click Download Router Configuration in the Virtual Interface pane, then email the configuration file to  support@aryaka.com team. After Aryaka completes the configuration, the virtual interface's status is Up (available). Route traffic to remote sites Traffic to the remote sites must now the directed to the virtual interface and its gateway that was just configured for Aryaka. Log in to the AWS Direct Connect console at   https://console.aws.amazon.com/directconnect/v2/home . Click Services in the left navigation pane, then click VPC . Click Route Tables and select the route table for the VPC that is being accessed through Aryaka. Select Routes in the lower pane and add the routes for the remote offices. Set the target for these routes as the VGW that was configured for Aryaka.    In this topic Related topics Accepting a hosted connection ( AWS Direct Connect User Guide )