Process for establishing connectivity using AWS Transit Gateway

1

Open a zendesk ticket, 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 through the AWS Transit Gateway. An eventual commercial validation may be necessary.

Customer

2

Create the AWS Transit Gateway in the account that hosts the services (backends) to be accessed by the Sensedia API Gateway.

Customer

3

Attach the VPC and subnet that host the backends to the AWS Transit Gateway.

Customer

4

Share the AWS Transit Gateway with the Sensedia team via ticket. For this step, you will need to get the account ID Sensedia. This ID may vary according to the environment setup performed for each client.

Customer

5

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

Sensedia

6

The Sensedia team will attach the VPC that hosts the Sensedia API Gateway to the AWS Transit Gateway shared by the customer.

Sensedia

7

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

Sensedia

8

Configure routes and firewall rules so that access from the VPC Sensedia is guaranteed.

Customer

9

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

Sensedia

10

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

1. Creating an API whose destination is a backend contained in the networks linked to the Transit Gateway (recommended).

2. Running tests via network tools.

Customer/Sensedia