From f9b5769ca4b41f46664800726497ca5032cfba69 Mon Sep 17 00:00:00 2001 From: Alistair Scott Date: Fri, 15 Nov 2024 17:47:22 +0000 Subject: [PATCH] docs: update IPs (#679) --- docs/faq.md | 2 +- docs/integrations/github_app.md | 8 +++++++- docs/integrations/gitlab_app.md | 8 +++++++- docs/integrations/terraform_cloud_enterprise.md | 8 +++++++- 4 files changed, 22 insertions(+), 4 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index b6bf961b..3412acff 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -102,7 +102,7 @@ Infracost provides static IPs for its Cloud Pricing API and Infracost Cloud serv | Name | Source | Destination | Domains | Port | IPs | Notes | |-|-|-|-|-|-|-| -| Inbound | Infracost Cloud | Your CI/CD system | N/A | 443 | 3.133.40.66 | Only needed if you use [source control integrations](/docs/integrations/cicd/#source-control-integrations-recommended) | +| Inbound | Infracost Cloud | Your CI/CD system | N/A | 443 | 3.133.40.66
3.16.104.91
3.147.121.170
3.141.214.65
18.221.82.195
18.119.42.142 | Only needed if you use [source control integrations](/docs/integrations/cicd/#source-control-integrations-recommended) | | Outbound | Your CI/CD system | Infracost Cloud | dashboard.api.infracost.io
pricing.api.infracost.io | 443 | 76.223.127.201
52.223.24.69 | Infracost CLI uses both domains | ## Features diff --git a/docs/integrations/github_app.md b/docs/integrations/github_app.md index ef1fcdbd..56c7eabf 100644 --- a/docs/integrations/github_app.md +++ b/docs/integrations/github_app.md @@ -44,7 +44,13 @@ Our automated GitHub App integration works with both GitHub Enterprise Cloud and Follow the same [usage steps](#usage) as the regular GitHub App above. #### Incoming traffic to GitHub -If you use the GitHub Enterprise "Enable IP allow list", the Infracost GitHub App will automatically add the required IP address to your GitHub organization's IP allow list. If you need to do that manually, please allow incoming traffic from `3.133.40.66` to your GitHub instance port 443 (or whatever port you use); this is the IP address used by Infracost Cloud services to call the integration. +If you use the GitHub Enterprise "Enable IP allow list", the Infracost GitHub App will automatically add the required IP address to your GitHub organization's IP allow list. If you need to do that manually, please allow incoming traffic from the following IP addresses to your GitHub instance port 443 (or whatever port you use); these are the IP addresses used by Infracost Cloud services to call the integration: +- 3.133.40.66 +- 3.16.104.91 +- 3.147.121.170 +- 3.141.214.65 +- 18.221.82.195 +- 18.119.42.142 #### Outgoing traffic from GitHub If you have restricted out-going traffic from your instance, you need to allow traffic to be sent to `dashboard.api.infracost.io:443` too. If you can only do that by IP address (and not domains), you should whitelist `52.223.24.69`, and `76.223.127.201`. diff --git a/docs/integrations/gitlab_app.md b/docs/integrations/gitlab_app.md index f3301912..96b0f3b6 100644 --- a/docs/integrations/gitlab_app.md +++ b/docs/integrations/gitlab_app.md @@ -43,7 +43,13 @@ Follow the same [usage steps](#usage) as the regular GitLab App above but note t ### Incoming traffic to GitLab -If you use GitLab's IP allow-list to restrict access to your GitLab installation, you need to allow incoming traffic from `3.133.40.66` to your GitLab instance's port 443 (or whatever port you use); this is the IP address used by Infracost Cloud services to call the integration. +If you use GitLab's IP allow-list to restrict access to your GitLab installation, you need to allow incoming traffic from the following IP addresses to your GitLab instance's port 443 (or whatever port you use); these are the IP addresses used by Infracost Cloud services to call the integration: +- 3.133.40.66 +- 3.16.104.91 +- 3.147.121.170 +- 3.141.214.65 +- 18.221.82.195 +- 18.119.42.142 ### Outgoing traffic from GitLab diff --git a/docs/integrations/terraform_cloud_enterprise.md b/docs/integrations/terraform_cloud_enterprise.md index 5ab43ce0..1da13d7a 100644 --- a/docs/integrations/terraform_cloud_enterprise.md +++ b/docs/integrations/terraform_cloud_enterprise.md @@ -31,7 +31,13 @@ Sign up or log in to [Infracost Cloud](https://dashboard.infracost.io) and go to ### 2. Firewall configuration for TFE -This step is only needed by Terraform Enterprise (TFE) users. You need to allow incoming traffic from `3.133.40.66` to your TFE instance port 443 (or whatever port you use); this is the IP address used by Infracost Cloud services to call your Run Task integration. +This step is only needed by Terraform Enterprise (TFE) users. You need to allow incoming traffic from the following IP addresses to your TFE instance port 443 (or whatever port you use); these are the IP addresses used by Infracost Cloud services to call your Run Task integration. +- 3.133.40.66 +- 3.16.104.91 +- 3.147.121.170 +- 3.141.214.65 +- 18.221.82.195 +- 18.119.42.142 If you have restricted out-going traffic from your TFE instance, you need to allow traffic to be sent to [our Outbound domains/IPs](/docs/faq/#how-can-i-whitelist-infracost-ip-addresses).