Skip to main content

Public connectivity using Cloud Exchange

Suggest edit Updated on June 2, 2022

Pega Cloud Connect enables the use of Cloud Exchanges from industry-leading providers such as Equinix Fabric, Megaport MCR, and many others to integrate your enterprise networks with Pega Cloud over public connections.

Cloud Exchanges provide a cost-effective and reliable connectivity option to establish a dedicated network connection from your enterprise and connected networks to the Pega Cloud services running in AWS over public networks. Depending on your Cloud Exchange provider's available offerings, you may also be able to use this connection to access other public resources from multiple cloud providers.

Cloud Exchange providing public connectivity between your enterprise and connected networks and Pega Cloud
A Cloud Exchange provider can help you connect Pega Cloud to your enterprise and connected networks over a public network.

Benefits include:

  • Short implementation time, leveraging your established IaaS relationships.
  • High bandwidth, exceeding one Gbps, depending on your provider and location of choice.
  • Diverse access to many services and other cloud-based systems throughout your corporate estate.

Client responsibilities:

  • Purchase Pega Cloud Connect from Pega to enable support.
  • Identify and select a Cloud Exchange provider if your Enterprise has no provider.

    “Cloud Exchange” is the industry-standard name for services that offer dedicated, highly available connectivity to many cloud services providers. However, your provider might use a different term, such as "Cloud Connectivity".

  • Configure a Cloud Exchange connection to AWS with your provider.

    Pega does not support connections directly to Pega Cloud environments over RFC 1918 space. For details, see Public connectivity using AWS Direct Connect public virtual interface.

  • Design and configure your network and equipment to leverage the Cloud Exchange connection, including but not limited to, IP addressing, routing, and Border Gateway Protocol (BGP).
  • Maintain the uptime and availability of your Cloud Exchange connection to AWS.

Design Patterns: For guidance on best practices and options for controlling access between your enterprise network and Pega Cloud over these public peering options, see Controlling Public Peering Access to Pega Cloud with BGP.

  • Previous topic Public connectivity using AWS Direct Connect public virtual interface
  • Next topic Private connectivity using AWS PrivateLink
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us