--- title: "Cloud Services Extension (CSX) with Equinix Fabric" canonical: "https://docs.aryaka.com/space/KNOW/1294762051/Cloud%20Services%20Extension%20(CSX)%20with%20Equinix%20Fabric" format: markdown --- Equinix Fabric is a multi-cloud digital infrastructure service that allows secure, software-defined connectivity between any cloud or on-premises devices to any other cloud. Aryaka leverages Equinix Fabric at most of our POPs to provide access to cloud providers and other Equinix customers. Aryaka refers to this capability as  Cloud Services Extension (CSX) and offers it to customers under the SmartCloud product category.  Extending Aryaka using Equinix Fabric provides the following benefits: Increased reach—Currently Aryaka is limited to providing local connectivity to cloud providers in geographic areas where we have a physical presence in the region. With Equinix Fabric we can reach far more locations. This is particularly significant in regions where Aryaka has few or no POPs. Reduced dependency on adding new POPs—Building a POP is a capital- and time-intensive activity. It takes us a minimum of six months after a location is identified to bring a POP into production. This includes legal clearance and permissions, hardware shipment and provisioning, circuit provisioning, and testing. In many instances there is not be enough customer demand to justify a POP in a region.  Equinix Fabric supports the following connection types:  Local Fabric connection—Virtual private connection to a service provider that is present in the same Equinix Fabric geographic location. Remote Fabric connection—Virtual private connection to a service provider that is present in a different Equinix Fabric geographic location. Equinix Fabric locations Aryaka is colocated with Equinix at the following POP locations. Note that not all Aryaka POPs colocated in Equinix are enabled for Fabric connectivity. The remote Equinix locations that can be accessed by the POP/Fabric pair are also listed. Aryaka POP Location Equinix Fabric Location Fabric Enabled? Remote Equinix Locations Ashburn (ASH1) Washington D.C Yes Atlanta, Miami Amsterdam (AMS1) Amsterdam Yes Manchester, Dublin, Stockholm, Helsinki Chicago (ORD1) Chicago Yes Toronto, Atlanta, Miami Dallas (DFW1) Dallas Yes Houston, Culpeper Hong Kong (HKG1) Hong Kong Yes Melbourne, Canberra, Perth London (LHR1) London Yes Manchester, Stockholm, Helsinki New Jersey (EWR1) New York Yes Boston Frankfurt (FRA1) Frankfurt Yes Dusseldorf, Hamburg, Munich, Madrid, Barcelona, Milan, Geneva, Zurich, Brussels, Sofia, Istanbul, Warsaw Sao Paulo (GRU1) Sao Paulo Yes Rio de Janeiro Seattle (SEA1) Seattle Yes Vancouver, Kamloops San Jose (SJC1) Silicon Valley Yes Los Angeles, Denver Singapore (SIN1) Singapore Yes Melbourne, Canberra, Perth Tokyo (NRT1) Tokyo Yes Osaka, Seoul Dublin (DUB1) Dublin Yes Manchester, Dublin, Stockholm, Helsinki Sydney (SYD1) Sydney Yes Melbourne, Canberra, Perth, Brisbane Miami (MIA1) Miami No n/a Toronto (YTO1) Toronto No n/a Dubai (DXB1) Dubai No n/a Paris (CDG1) Paris Yes Dusseldorf, Hamburg, Munich, Madrid, Barcelona, Milan, Geneva, Zurich, Brussels, Sofia, Istanbul, Warsaw At all locations where Aryaka is Fabric-enabled, there are dual connections to Equinix Fabric, which ensures 99.999% (also known as fine-nines) connectivity to Equinix Fabric. Aryaka offers unlimited connections to Equinix at all Fabric-enabled POPs. This means there is no cost to Aryaka for originating local Fabric connections to cloud providers or other Equinix customers. But for all remote Fabric connections, Aryaka incurs a monthly recurring charge from Equinix.  The following graphic shows local and remote CSX connections using Equinix Fabric, the billing implications, and the Aryaka SKUs (product offerings) required. Equinix Fabric with Aryaka CSX An Equinix Fabric connection with Aryaka POPs can provide end-to-end L2 connectivity for customers' remote sites over Aryaka Core. Customers with devices located in an Equinix data center can connect to Aryaka POPs using a dedicated, logical L2 path created on top of Equinix Fabric. Customers can create local and remote virtual connections on the Aryaka POP. For all remote connections, an additional cost is incurred and the Equinix portal displays the exact amount during the provisioning process. Use cases This section describes a number of uses cases for connectivity between Equinix Fabric and Aryaka CSX. It also lists the Aryaka SKUs (product offerings) required to facilitate the connection. CSX Remote as primary IaaS You want to connect to an IaaS site from an Aryaka POP. But the region where the IaaS site is located does not have an Aryaka POP. The connectivity can be facilitated using an Equinix Fabric remote connection. Required Aryaka SKU's for this connection: IaaS site license SmartCloud SBW CSX Remote CSX Remote as backup IaaS You require a primary and backup connection from an Aryaka POP to an IaaS site. Primary connection—From Aryaka POP to IaaS over a local Equinix Fabric connection. Backup connection—From a different Aryaka POP to the same IaaS over a remote Equinix Fabric connection. Required Aryaka SKUs for the primary connection: IaaS site license SmartCloud SBW  Required Aryaka SKUs for the backup connection: IaaS site license CSX Remote CSX Remote for data center connectivity You have devices in an Equinix data center location where Aryaka does not have a POP. You can place an Aryaka Network Access Point (ANAP) device in your Equinix cage. The ANAP connects to an Aryaka POP using a remote Equinix Fabric connection instead of over IPSec. This is similar to a customer site connecting to Aryaka POP using CSX. If you prefer to not place an ANAP at the Equinix data center, then it is bring-your-own (BYO) scenario where you provide a device and connect to the Aryaka POP using a remote Equinix Fabric connection. Required Aryaka SKUs for these connections: SmartManage site license SmartConnect SBW CSX Remote The following graphic shows a customer site with an Aryaka ANAP deployed at an Equinix data center connecting to Aryaka using CSX and remote a Fabric connection: The following graphic shows customer premises equipment (CPE) deployed at an Equinix data center connecting to Aryaka using CSX and remote a Fabric connection: Inbound CSX Remote from a customer to Aryaka POP Your customer site is located in an Equinix data center where Aryaka does not have a POP. As an existing Equinix customer, you can initiate a remote Equinix Fabric connection to the closest Aryaka POP and be billed per Equinix pricing policies. Aryaka is not be billed as we are only accepting the remote connection. Required Aryaka SKUs for this connection: IaaS site license SmartCloud SBW In this topic Related topics Equinix Fabric connectivity with Aryaka Equinix Fabric - FAQs Equinix Fabric - Documentation Equinix Fabric - Provider Availability