Viz Now Administrator Guide

Version 1.2 | Published April 09, 2024 ©

Working with VPC Peering

Viz Now allows you to connect different spaces or VPCs using the VPC peering service in AWS. This allows network traffic to be exchanged between the applications running within different spaces. This can also be used to let Viz Now spaces communicate with VPCs that are manually created within AWS.

Note: Peering can only be set up by the Organization Admin user or a Editor user with access to the Spaces to be peered. If a peering with a VPC that is not created by Viz Now some manual configuration is required. See AWS documentation regarding this.

Space Peering

You must have the necessary access rights to both spaces. In addition, you must have minimum Viz Now Editor or Admin privileges. It is possible to peer with several other Spaces. This can be useful if you want to have dedicated Spaces for contribution or limit for different Operators access into different Spaces. When peering spaces some manual configuration of the App configurations are usually required if you want them to communicate. This is depending on the Apps you use.

To peer with another Space

  1. Navigate to one of the Spaces.

  2. Click the dotted button.

    images/download/attachments/140805757/image2023-5-9_12-38-25.png
  3. Select Peer with VPC.

  4. The VPC Peering dialogue appears. Click the + icon at the bottom of the list and select Peer with Viz Now space.

    images/download/attachments/140805757/image-2024-1-2_8-16-29.png
  5. From the list of available spaces, select the Space you want to connect to.

  6. Give the peering an appropriate name.

    images/download/attachments/140805757/image-2024-1-2_8-19-0.png
  7. Click Create to start the peering.

  8. The peering should be automatically accepted within minutes.

Note: If the Space you want to connect to is not in the list, most likely you lack access rights or the space is unsuitable for peering.

To peer with an external account or custom VPC

Warning: If you wish to establish peering with custom Virtual Private Clouds (VPCs), ensure that the target VPC falls within the CIDR range defined for the organization, usually 10.0.0.0/8. Alternatively, you can consider using the 172.16.0.0/12 range, although this holds a lower priority and network traffic will be deprioritized.

images/download/attachments/140805757/image-2024-1-2_8-25-51.png

  1. From the VPC Peering dialogue - select Peer with external AWS VPC.

  2. Fill in the required fields.

  3. Click Create.
    This creates the peering request

  4. When connecting to custom VPCs some additional configuration from within the AWS Console is required for the peering to work.

    • Accepting the peering request.

    • Setting up the route table on the custom VPC to route traffic to the Viz Now VPC.

  5. Once the peering is complete, you should see the peering status below the title of the Space.

Warning: If the two spaces are in different regions, AWS transfer costs are added to your AWS bill.

To delete a VPC peering

  1. Open the Space where the peering is configured.

  2. Open the VPC Peering dialogue.

  3. Select the Active peering and click the red Delete button.

    images/download/attachments/140805757/image-2024-1-2_8-37-0.png
  4. Click Confirm to delete the peering.