Skip to main content

AWS Direct Connect Private Virtual Interface (VIF)

Suggest edit Updated on June 2, 2022

Beginning April 2022, Pega Cloud is ending support for all new configurations of the legacy AWS Direct Connect Private VIF connectivity option.

For more information, see Change of support for connectivity options, which includes a recommended alternative to an AWS Direct Private VIF connection.

Pega Cloud services allows clients to connect using Amazon Web Services (AWS) Direct Connect Private Virtual Interface (VIF) within a geographical region.

Use this AWS service to connect from the following types of endpoints:

  • A data center provider that is located within the same geographical region as your AWS service.
  • A multiprotocol label switching (MPLS) VPN or other type of wide area network (WAN).

Direct Connection options

Pega Cloud supports AWS Direct Connect Private VIF connectivity so you can access your Pega Cloud DevTest, Staging, and Production subnets using AWS Direct Connect Private VIF. AWS Direct Connect Private VIF provides connectivity between these environments through a virtual interface, which is then physically connected through the AWS network to the customer network through a virtual gateway (VGW).

Direct connection for Pega Cloud

Prerequisite

If you are not already an AWS customer, set up an AWS account for your enterprise. Your account includes an AWS console through which you can order services.

After setting up an AWS account, create an AWS Direct Connect Private VIF.

For more information, see the Amazon Web Services article AWS Direct Connect virtual interfaces.

Setting up AWS Direct Connect

Complete the following process to set up AWS Direct Connect for your Pega Cloud VPC:

  1. Provision Direct Connect ports in your AWS Console.
  2. In My Support Portal, open a Service Request (SR) to create the direct connect virtual interface to your Pega Cloud VPC. The SR tracks the provisioning process as well as the information provided to you by Pega Cloud for your request.

    Pega Cloud will provide your account and region information, which you need to complete your request.

  3. In your AWS Console, initiate a request for a virtual interface to Pega Cloud.
  4. Enter the Pega Cloud account and region information in your request and submit it.

After you submit the request in your AWS Console, Pega Cloud will receive the details and after approval, connects the virtual interface to your Pega Cloud VPC. Pega Cloud also sets up basic monitoring for the connection from your Pega Cloud VPC.

You can use a third-party portal to provision a direct network connection, such as one that is offered by your telecommunications provider. If you choose this option, consult the provider's support team about the request process.

Redundancy options for AWS Direct Connect

AWS Direct Connect Private VIF is a stand-alone connection, and you might want to configure a redundant connection to your network. Pega Cloud supports the following options for redundancy:

  • An additional AWS Direct Connect service (redundant direct connection).
  • Failover to customer VPN.

You can choose the option that works best for your requirements. You are responsible for the configuration and implementation of redundancy for AWS Direct Connect.

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