Connectivity with AWS Transit Gateway

1

Open a ticket in Zendesk, indicating the need for this type of connectivity. In this ticket, it is important to share the CIDRs of the networks that will be accessible via AWS transit gateway. Commercial validation may be required.

Client

2

Create the AWS transit gateway in the account hosting the services (backends) to be accessed by Sensedia Integrations.

Client

3

Attach the VPC and subnet hosting the backends to the AWS transit gateway.

Client

4

Share the AWS transit gateway with the Sensedia team via ticket. For this step, it will be necessary to obtain Sensedia’s account ID. This ID may vary depending on the setup of the environment made for each client.

Client

5

After sharing, an invitation will be generated for the Sensedia account. The technical team will accept this sharing.

Sensedia

6

The Sensedia team will attach the VPC hosting Sensedia Integrations to the AWS transit gateway shared by the client.

Sensedia

7

The Sensedia team will share the CIDR of the VPC used to host Integrations.

Sensedia

8

Configure routes and firewall rules to ensure access from the Sensedia VPC.

Client

9

The Sensedia team will also add routes related to the CIDRs informed in step 1.

Sensedia

10

Test the connection. This can be done in two ways:

1. Creating an integration whose destination is a backend contained in the networks attached to the transit gateway (recommended).

2. Running tests via network tools.

Client/Sensedia