From ce4c647ee1e2d04a12b4de4955362d0f50f6ac6f Mon Sep 17 00:00:00 2001 From: Vadim Golub Date: Wed, 15 Jan 2025 12:41:30 +0000 Subject: [PATCH] docs: Update terminology to use allowlist (#691) --- docs/faq.md | 4 ++-- docs/integrations/github_app.md | 2 +- docs/integrations/gitlab_app.md | 2 +- docs/integrations/terraform_cloud_enterprise.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 3412acff..d55ebebb 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -96,9 +96,9 @@ No. Infracost is backed by top-tier investors including Y Combinator and Sequoia If you believe you have found a vulnerability within Infracost, please let us know right away. Follow the process [outlined here](https://github.com/infracost/infracost/blob/master/SECURITY.md). -### How can I whitelist Infracost IP addresses? +### How can I allowlist Infracost IP addresses? -Infracost provides static IPs for its Cloud Pricing API and Infracost Cloud services. If your environment has network traffic restrictions, you can whitelist these IPs in your firewall rules. +Infracost provides static IPs for its Cloud Pricing API and Infracost Cloud services. If your environment has network traffic restrictions, you can allowlist these IPs in your firewall rules. | Name | Source | Destination | Domains | Port | IPs | Notes | |-|-|-|-|-|-|-| diff --git a/docs/integrations/github_app.md b/docs/integrations/github_app.md index f71969e0..402f0e30 100644 --- a/docs/integrations/github_app.md +++ b/docs/integrations/github_app.md @@ -53,7 +53,7 @@ If you use the GitHub Enterprise "Enable IP allow list", the Infracost GitHub Ap - 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`. +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 allowlist `52.223.24.69`, and `76.223.127.201`. ### GitHub Enterprise Server diff --git a/docs/integrations/gitlab_app.md b/docs/integrations/gitlab_app.md index 96b0f3b6..d6db6969 100644 --- a/docs/integrations/gitlab_app.md +++ b/docs/integrations/gitlab_app.md @@ -53,7 +53,7 @@ If you use GitLab's IP allow-list to restrict access to your GitLab installation ### Outgoing traffic from GitLab -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`. +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 allowlist `52.223.24.69`, and `76.223.127.201`. ### Other network/security requirements diff --git a/docs/integrations/terraform_cloud_enterprise.md b/docs/integrations/terraform_cloud_enterprise.md index 1da13d7a..fa33d9d7 100644 --- a/docs/integrations/terraform_cloud_enterprise.md +++ b/docs/integrations/terraform_cloud_enterprise.md @@ -39,7 +39,7 @@ This step is only needed by Terraform Enterprise (TFE) users. You need to allow - 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). +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-allowlist-infracost-ip-addresses). ### 3. Configure a Run Task