docs: update IPs (#679)

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 <br /> 3.16.104.91 <br /> 3.147.121.170 <br /> 3.141.214.65 <br /> 18.221.82.195 <br /> 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 <br/> pricing.api.infracost.io | 443 | 76.223.127.201 <br /> 52.223.24.69 | Infracost CLI uses both domains |
 
 ## Features

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`.

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
 

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).