Skip to main content

AWS Transit Gateway

Suggest edit Updated on June 9, 2022

Beginning April 2022, Pega Cloud is ending support for all new configurations of the AWS Transit Gateway legacy connectivity option.

For more information, see Change of support for connectivity options, which includes a recommended alternative to an AWS Transit Gateway private connection.

Pega Cloud services supports attaching your Pega Cloud environment to an AWS Transit Gateway that you manage. Your Transit Gateway can then act as a central hub to easily route traffic between your external connections and your Pega Cloud environment.

Using Transit Gateway puts you in full control of connectivity to Pega Cloud from your on-premise datacenter and your cloud applications or services and allows you to more quickly and easily connect new applications with your Pega application. While Pega Cloud services can attach your Pega Cloud environment to an existing AWS Transit Gateway, Pega Cloud services does not provide the Transit Gateway as a service.

For more information about subscribing to AWS Transit Gateway, see the official AWS Transit Gateway landing page.

Note: Pega currently does not support integrating VPN attachments to a Transit Gateway.

After you subscribe to the AWS Transit Gateway service through your AWS account, you can request that Pega Cloud services provides the information you need to integrate your service with your Pega Cloud environments. The following figure provides a model of how your Pega Cloud services VPC integrates with your AWS Transit Gateway Service.

Sample Transit Gateway topology

Integrating Pega Cloud environments with your Transit Gateway can simplify your enterprise network topology by providing the following benefits:

  • Eliminating the need for complicated peering connections, especially in larger topologies, to let multiple environments communicate with one another
  • Removing the requirement for multiple VPN connections between each of your AWS VPCs, including your Pega VPC, and on-premises environments
  • Limiting traffic between your Pega Cloud environment and other VPCs
  • Scaling your enterprise network topology to your Pega Cloud networking demands
  • Responding to spikes in network traffic more resiliently through multiple interoperable VPCs

Implementing a Transit Gateway integration

Before you begin: Before Pega Cloud services can complete the integration, you must:
  • Ensure that you can access your AWS Resource Access Manager (RAM) and create a resource share for Pega Cloud services use.
  • Have a management account with sharing enabled for AWS organizations to create the Transit Gateway resource share.
Pega Cloud supports attaching your Pega Cloud environment to an AWS Transit Gateway that you manage. Your Transit Gateway can then act as a central hub to easily route traffic between your external connections and your Pega Cloud environment.

To implement a Transit Gateway integration, complete the following steps:

  1. Request a new service by selecting New request in My Support Portal, or by using Pega Support Contact Information to complete a request to integrate your Transit Gateway with your Pega Cloud environments. For the latest documentation on making requests, see My Support Portal: New design, streamlined features.
  2. Update your Transit Gateway service by allowing Pega Cloud services to access your Transit Gateway:
    1. In the AWS RAM console, create a resource share.
    2. From the response to the request, or the from the call with your Pega representative, note the account number Pega Cloud services shares with you.
    3. In your RAM console, in the Principals section, enter the account number that you receive from Pega Cloud services in response to your service request.
    4. Select Create resource share.
      Note: You can use the create-resource-share AWS API to enter the account number.

      For more information on how to create a resource share through the RAM console or by using the API, see the AWS Resource Management Documentation.

    After you create a resource share of your Transit Gateway, Pega Cloud services creates a resource share attachment of your Pega Cloud environment.

  3. Accept the resource share referencing your Pega Cloud environment.
    1. In your RAM console, select the Shared with me, Resource shares pane.
    2. On the Pending resource share page, add your Pega Cloud environment by selecting Accept Resource Share.
    For more information on receiving a resource share, see the AWS Resource Access Manager documentation.
Result: You integrated the Pega Cloud VPC and VPN service into your Transit Gateway, and can now use the Transit Gateway to connect your Pega Cloud VPC to the rest of your enterprise network topology.
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