---
title: Integrate Your Data Center with Tiger Cloud | Tiger Data Docs
description: Connect your on-premise infrastructure to Tiger Cloud using AWS Transit Gateway
---

This page explains how to integrate your corporate on-premise infrastructure with Tiger Cloud using [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/).

## Prerequisites

To follow the steps on this page:

- Create a target [Tiger Cloud service](/docs/get-started/quickstart/create-service/index.md) with the Real-time analytics capability.

  You need your [connection details](/docs/integrate/find-connection-details/index.md).

* Set up [AWS Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html).

Note

This feature is currently not supported for Tiger Cloud on Microsoft Azure.

## Connect your on-premise infrastructure to your services

To connect to Tiger Cloud, first establish connectivity between your on-premise infrastructure and AWS. See [Centralize network connectivity using AWS Transit Gateway](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/centralize-network-connectivity-using-aws-transit-gateway.html). Then:

1. **Create a Peering VPC in [Tiger Console](https://console.cloud.tigerdata.com/)**

   1. In `Security` > `VPC`, click `Create a VPC`:

      ![Creating a new peering VPC in Tiger Console](/docs/_astro/add-peering-vpc-tiger-cloud.BHFW98a8_Hcuw1.webp)

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

      ![Configuring VPC region, IP range, and name](/docs/_astro/configure-peering-vpc-tiger-cloud.DZom78te_Zspfuq.webp)

      Your service and Peering VPC must be in the same AWS region. The number of Peering VPCs you can create in your project depends on your [pricing plan](/docs/deploy/tiger-cloud/tiger-cloud-aws/pricing-and-account-management/index.md). If you need another Peering VPC, either contact <support@tigerdata.com> or change your plan in [Tiger Console](https://console.cloud.tigerdata.com/).

   3. Add a peering connection:

      1. In the `VPC Peering` column, click `Add`.
      2. Provide your AWS account ID, Transit Gateway ID, CIDR ranges, and AWS region. Tiger Cloud creates a new isolated connection for every unique Transit Gateway ID.

      ![Adding a peering connection with AWS account ID and Transit Gateway details](/docs/_astro/add-peering-tiger-cloud.9tTfnXvs_Z1YfI1i.webp)

      1. Click `Add connection`.

2. **Accept and configure peering connection in your AWS account**

   Once your peering connection appears as `Processing`, you can accept and configure it in AWS:

   1. Accept the peering request coming from Tiger Cloud. The request can take up to 5 min to arrive. Within 5 more minutes after accepting, the peering should appear as `Connected` in Tiger Console.

   2. Configure at least the following in your AWS account networking:

      - Your subnet route table to route traffic to your Transit Gateway for the Peering VPC CIDRs.
      - Your Transit Gateway route table to route traffic to the newly created Transit Gateway peering attachment for the Peering VPC CIDRs.
      - Security groups to allow outbound TCP 5432.

3. **Attach a Tiger Cloud service to the Peering VPC In [Tiger Console](https://console.cloud.tigerdata.com/dashboard/services)**

   1. Select the service you want to connect to the Peering VPC.
   2. Click `Operations` > `Security` > `VPC`.
   3. Select the VPC, then click `Attach VPC`.

   You cannot attach a Tiger Cloud service to multiple Tiger Cloud VPCs at the same time.

You have successfully integrated your corporate data center with Tiger Cloud.
