Table of Contents

Network migration FAQs

This content applies only to Cloud environments.

To return to the overview article, see Network migrations: benefits and impacts.

Frequently Asked Questions

Does the environment network migration impact the networking of my Pega Cloud environment?

If you have not placed your inbound traffic from your Pega Cloud environment or outbound traffic from your network to the Pega Cloud SFTP service on an allow list, the environment network migration will not impact your Pega Cloud environment in any way.

If you have placed your inbound traffic from your Pega Cloud environment or outbound traffic from your network to the Pega Cloud SFTP service on an allow list, please see Network migrations: benefits and impacts to view reconfigurations of your Pega Cloud environment. Pega Cloud Services performs the migration with zero-downtime.

Will the environment network migration impact the performance of my environment?

The network migration to the new Pega Cloud network topology does not impact the performance of your environment.

Should I expect downtime during the migration for my Pega Cloud environment?

No. The environment network migration process does not require downtime for your Pega Cloud environment. Pega performs the migration after you complete the questionnaire and determines the compatibility of your environment with the new network topology. After you provide consent, Pega Cloud Services performs the network migration during your defined maintenance window. For details about maintenance windows, see Pega Cloud Services maintenance and types of system updates

Do I need to prepare for the environment for the network migration?

Existing allow lists for non-SFTP traffic outbound to your Pega Cloud environment do not require enterprise network changes before or after the network migration.

Pega Cloud Services must review existing allow lists for inbound traffic from your Pega Cloud environment and outbound traffic to the Pega Cloud SFTP service before Pega initiates an environment network migration.  For more information, see Network migrations: benefits and impacts.

Will my existing allow lists used to access my Pega application remain valid after the network migration?

Pega Cloud Services must review allow lists for inbound traffic from your Pega Cloud environment and outbound traffic to the Pega Cloud SFTP service before Pega initiates the network migration. Depending upon your environment, you may have to place Pega-provided static IP addresses for inbound connections from your Pega Cloud environment on an allow list. After the upgrade, you will receive a list of static IPs addresses no longer associated with the Pega Cloud environment to remove from their enterprise network firewall to avoid IP address conflict. For more information, see Network migrations: benefits and impacts.

Can I configure my allow list to distinguish between different environment types (dev, staging, production) after the environment network migration?

Yes. You can still add different environment types on allow lists in the upgraded infrastructure model. You must explicitly request placing environments of different types which will be evaluated by Pega Cloud Services

Can I configure my allow list to distinguish between different environments of the same type (Devtest 1, Devtest 2)?

No. The enhanced infrastructure model does not support adding different Pega Cloud environments of the same type on an allow list. You must reconfigure enterprise network allow lists to permit traffic using the new Pega-provided IP addresses from environments of the same type.

Does the enhanced environment impact my VPN gateway connection? Do I need to reconfigure my VPN gateway connection after an upgrade to the latest infrastructure?

No. Pega Cloud environment network migration do not impact the VPN connectivity for inbound and outbound traffic to and from your Pega Cloud environment. All existing VPN configurations are preserved after the network migration.

Does the enhanced environment network migration impact my peering connections to Amazon VPCs? Do I need to reconfigure my VPC peering connections following an environment network migration?

No. The Pega Cloud environment network migration does not impact the Pega Cloud environment peering connection to client-owned Amazon VPCs. For more information, see Requesting a virtual private cloud (VPC) peering connection.

Suggest Edit

0% found this useful

Have a question? Get answers now.

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