Static Egress IPs
Some third-party platforms may find it necessary to whitelist connections made from your Porter-provisioned infrastructure. This guide walks you through determining the egress IPs used by your applications.
AWS
AWS CLI
After ensuring you have the AWS CLI installed and configured to access the account which contains your Porter cluster, run the following command:
You’ll need to replace <CLUSTER_NAME>
and <REGION>
with the name, and region of your cluster.
This command will return the egress IP which you can use to whitelist your workloads with third party platforms. In case your cluster has multiple gateways, there will be multiple egress IPs.
AWS VPC Console
-
Log into the AWS account containing your Porter cluster, and navigate to the
VPC
console in the appropriate region for your cluster. -
In the left pane, select
NAT gateways
, and you’ll be able to see your cluster’s NAT gateways; they’ll be named after your cluster, and have a tagporter.run/managed: true
-
Copy the contents of
Primary public IP
- this serves as the egress IP which you can use to whitelist your workloads with third party platforms. In case your cluster has multiple gateways, there will be multiple egress IPs.
Google Cloud Platform (GCP)
gcloud CLI
After ensuring you have the GCP gcloud CLI installed and configured to access the account which contains your Porter cluster, run the following command:
You’ll need to replace REGION
with the region that your cluster was deployed in.
If your cluster name is my-cluster
, then your egress IP will be my-cluster-cloud-nat-ip
This command will return the egress IP which you can use to whitelist your workloads with third party platforms.
In case your cluster has multiple gateways, there will be multiple egress IPs.
GCP Console
-
Log into the GCP console, and navigate to Cloud NAT
-
Search for your cluster name in the search bar, and click on the ‘Gateway Name’
-
Your clusters IP address will be listed under “Cloud NAT Rules” as “Cloud NAT IPs”