Table of Contents

Network migrations: benefits and impacts

The latest Pega Cloud Services infrastructure supports an enhanced network topology that uses allow list configurations for your Virtual Private Cloud (VPC).

The new network topology enables you to scale by adding new networks and environments without requiring subsequent allow list reconfigurations on your enterprise network. This requires a one-time Pega Cloud network migration for your environments, allowing you to take advantage of the Pega seamless infrastructure maintenance using the new network topology.

Old network architecture with static IPs attached to each Pega node

New network architecture with static IPs attached to NAT Gateway

The network migration does not impact you if you do not add connections to your firewall allow list in your enterprise network or if you do not use certain allow list configurations. For more information, see the section Network migration planning considerations below.

If you are an existing client, you must provide information about your Pega SFTP service connections. If you are a new client, you automatically receive the new network topology with no action required.

Pega Cloud Services will work with you to ensure that your environment connectivity meets its required reconfiguration. After you verify that your allow list reconfigurations meet the requirements for the new network topology and consent to the migration, Pega Cloud Services completes the migration using a zero-downtime process.

For more information about allow list configurations, see Configuring public access between your Pega Cloud environment and your enterprise network.

Benefits of Pega Cloud Services network migration

Changes to your environments take effect following the network migration. The benefits of the enhanced network to the infrastructure include the items detailed below:

  • Use of a more reliable and scalable Pega Cloud network infrastructure
  • Enhances security of your underlying network infrastructure
  • Enhances the stability of the software upgrade and patch and infrastructure update processes

For more information, see Pega Cloud Services maintenance and types of system updates.

Network migration planning considerations

The Pega Cloud network migration impacts you if you have the following allow list configurations:

  • Outbound traffic from your enterprise network to the Pega Cloud SFTP service to your Pega Cloud environment.

Pega Cloud Services proactively contacts you to plan the network migration to the new network topology. In order for the migration to proceed, you must reconfigure your previous enterprise-network allow lists.

For more information about allow list configurations, see Configuring public access between your Pega Cloud environment and your enterprise network.

Pega Cloud environments no longer supports placing individual environments of the same type (Devtest1, Devtest2) on separate allow lists after the network migration. For more information, see Network migration Frequently Asked Questions.

You should plan to complete the following processes in order to proceed with the migration:

  • Plan for the zero-downtime network migration to proceed within your next standard maintenance window.
  • If you must reconfigure any of your allow lists, you must complete the following tasks:
    • Reconfigure your allow lists using the new Pega-provided static IP addresses.
    • Confirm with Pega Cloud Services that you updated your allow lists.
    • Remove previously-used IP addresses for your Pega Cloud environment from the allow list.

Pega responsibilities

During a network migration, Pega Cloud Services performs the following tasks:
  • Coordinates with you to facilitate any required client-side networking changes to support the network migration.
  • If you must reconfigure your allow list, Pega accomplishes the following tasks:
    • If you added your SFTP connection to an allow list, provides you with a new static IP address for your SFTP service.
    • Confirms with you that new static IP addresses are placed on an allow list.
    • After the migration, shares a list of static IP addresses with you that are no longer associated with the Pega Cloud environment for you to remove from your enterprise network allow list.

Client responsibilities

To ensure the process maintains zero-downtime to transfer Pega Cloud environments to the new network topology, you must perform the following tasks:

References to client enterprise networks include integrations with third-party vendors and partners.
  • Open a change request by selecting New Request in My Support Portal to open the discussion regarding migration.
  • Respond to Pega Cloud Services SFTP questionnaire that asks for the required enterprise network information.
  • Confirm a standard maintenance window with Pega Cloud Services to execute the network migration.
  • For all of your environments that require an allow list reconfiguration, complete the following tasks:
    • Obtain necessary approvals from network administrators and other relevant stakeholders regarding inbound allow list changes to Pega Cloud environments.
    • If you added your SFTP connection to an allow list, update the allow list with the new SFTP static IP address.
    • Prior to the migration, update the allow list with the new Pega-provided static IP addresses.
    • Confirm with Pega that you updated your allow lists.
    • After completing the migration, remove the static IP addresses provided by Pega Cloud Services in the correspondence from your enterprise network inbound allow list.

If you have any additional questions please contact Pega Cloud Services or see the Network migration FAQ.

Pega SFTP Service questionnaire

Pega Cloud Services sends a questionnaire to clients who use the Pega SFTP service. The following table presents the content of the questionnaire and the implication of your reply to the email correspondence. You should review the table to understand which scenarios require network reconfigurations for the SFTP service, and what actions you must complete before Pega Cloud proceeds with the migration.

Question If yes: If no:
Does your outbound allow list from your enterprise network include your Pega-provided SFTP service IP address? Pega Cloud Services sends you a new static IP address for your SFTP connection.

After receiving the SFTP static IP address, perform the following tasks:

  1. Prior to the migration, reconfigure your SFTP connection to a new Pega-provided SFTP static IP addresses.
  2. Confirm with Pega Cloud Services via that you added the connection to your allow list to the request that Pega sent you.
Pega can perform the network migration without any further changes on your behalf.

For frequently asked questions about the network migration, see Network migration Frequently Asked Questions.

Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

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