A VPC is, simply put, a private and isolated network within your cloud provider (for example, AWS).
By routing your application’s outbound traffic through a gateway within this private network, you can associate a Static IP address to it. This ensures that all requests from your application to our API will originate from the same IP address.
To simplify the implementation, we’ve compiled the official technical documentation from the main cloud providers. Your technical teams can follow these guides to configure a VPC with a fixed outbound IP:
Amazon Web Services (AWS)
AWS uses the Elastic IP service to provide a static public IP address. The documentation below explains how to create a VPC and associate an Elastic IP with a NAT Gateway, which will centralize the outbound traffic.
Guide: VPC with Private Subnets and NAT Gateway
Allocating an Elastic IP: Working with Elastic IPs
Google Cloud Platform (GCP)
In Google Cloud, you can set up a VPC and use the Cloud NAT service to assign a static external IP address to your instances.
Guide: Set Up Cloud NAT with a Static IP
Reserving a Static External IP Address: Reserve a Static External IP Address
Microsoft Azure
In Azure, the process involves creating a Virtual Network (VNet) and associating a Public IP address (Standard SKU) with a NAT Gateway.
Guide: Tutorial: Create a NAT Gateway Using the Azure Portal
Associating a Public IP: Create, Change, or Delete a Public IP Address
We are available to clarify any questions and assist you as needed throughout this process.
Comments
0 comments
Article is closed for comments.