You use Virtual Private Cloud (VPC) peering to ensure that your Timescale Services are only accessible through your secured AWS infrastructure. This reduces the potential attack vector surface and improves security.

The data isolation architecture that ensures a highly secure connection between your apps and Timescale:

The AWS Security Groups dashboard

Your apps run inside your AWS Customer VPC, your Timescale Services always run inside the secure Timescale VPC. You control secure communication between apps in your VPC and your Timescale Services using a dedicated Peering VPC. The AWS PrivateLink connecting Timescale VPC to the dedicated Peering VPC gives the same level of protection as using a direct AWS PrivateLink connection. It only enables communication between your Customer VPC and your Timescale Services.

To configure this secure connection, you first create the Peering VPC with AWS PrivateLink in Timescale. After you have accepted and configured the peering connection to your Customer VPC, you use AWS Security Groups to restrict the services in your Customer VPC that are visible to the Peering VPC. The last step is to attach individual Timescale Services to the Peering VPC.

You can run three VPCs in each project, and each Timescale VPC can have as many peering connections as you need. If you need more VPCs click Support in Timescale Console and ask for a quota increase.

In order to set up VPC peering you need the following permissions in your AWS account:

  • Accept VPC peering requests
  • Configure route table rules
  • Configure security group and firewall rules

To connect to a Timescale Service using VPC peering, your apps and infrastructure must be already running in an Amazon Web Services (AWS) VPC. You can peer your VPC from any AWS region. However, your Timescale VPC must be within one of the Cloud-supported regions.

The stages to create a secured connection between Timescale Services and your AWS infrastructure are:

  1. Create a Peering VPC in Timescale
  2. Complete the VPC connection in your AWS
  3. Set up security groups in your AWS
  4. Attach a Timescale Service to the Peering VPC

Create the VPC and the peering connection that enables you to securely route traffic between Timescale and your own VPC in a logically isolated virtual network.

  1. In Timescale Console > VPC, click Create VPC.

  2. Choose your region and IP range, then click Create VPC.

    Create a new Timescale VPC
  3. For as many peering connections as you need:

    1. In the VPC Peering column, click Add.

    2. Enter information about your existing AWS VPC, then click Add Connection.

      Create a new Timescale VPC

Timescale sends a peering request to your AWS account so you can complete the VPC connection in AWS.

When you receive the Timescale peering request in AWS, edit your routing table to match the IP Range and CIDR block between your AWS and Timescale VPCs.

The request acceptance process is an important safety mechanism. Do not accept a peering request from an unknown account.

  1. In AWS > VPC Dashboard > Peering connections, select the peering connection request from Timescale.

    Copy the peering connection ID to the clipboard. The connection request starts with pcx-.

  2. In the peering connection, click Route Tables, then select the Route Table ID that corresponds to your VPC.

  3. In Routes, click Edit routes. You see the list of existing Destinations.

    Create a new VPC route

    If you do not already have a destination that corresponds to the IP range / CIDR block of your Timescale VPC:

    1. Click Add route, and set:
      • Destination: the CIDR block of your Timescale VPC. For example:
      • Target: the peering connection ID you copied to your clipboard.
    2. Click Save changes.

Network traffic is secured between your AWS account and Timescale for this project.

Security groups allow specific inbound and outbound traffic at the resource level. You can associate a VPC with one or more security groups and each instance in your VPC may belong to a different set of security groups. The security group choices for your VPC are:

  • Create a security group to use for your Timescale VPC only.
  • Associate your VPC with an existing security group.
  • Do nothing, your VPC is automatically associated with the default one.
To create a security group specific to your Timescale VPC:
  1. AWS > VPC Dashboard > Security Groups, click Create security group.

  2. Enter the rules for this security group:

    The AWS Security Groups dashboard
    • VPC: select the VPC that is peered with Timescale.
    • Inbound rules: leave empty.
    • Outbound rules:
      • Type: Custom TCP
      • Protocol: TCP
      • Port range: 5432
      • Destination: Custom
      • Info: the CIDR block of your Timescale VPC.
  3. Click Add rule, then click Create security group.

Now that Timescale is communicating securely with your AWS infrastructure, you can attach one or more Timescale Services to the VPC.

After you attach a Timescale Service to a VPC, you can only access it through the peered AWS VPC. It is no longer accessible using the public internet.

  1. In Timescale Console > Services select the Service you want to connect to the VPC.
  2. Click Operations > VPC.
  3. Select the VPC, then click Attach VPC.

And that is it, your Timescale Service is now securely communicating with your AWS account inside a VPC.

To ensure that your applications continue to run without interruption, you keep Timescale Services attached to the VPC. However, you can change the VPC your Timescale Service is attached to, or disconnect from a VPC and enable access to the Timescale Service from the public internet.


Timescale uses a different DNS for Timescale Services that are attached to a VPC. When you migrate a Timescale Service between public access and a VPC, you need to update your connection string.

  1. In Timescale Console > Services select the Service to migrate. If you don't have a Timescale Service, create a new one.
  2. Click Operations > VPC.
  3. Select the VPC, then click Attach VPC.

Migration takes a few minutes to complete and requires a change to DNS settings for the Service. The Service is not accessible during this time. If you receive a DNS error, allow some time for DNS propagation.


Found an issue on this page?Report an issue or Edit this page in GitHub.