diff --git a/docs/cloud_pricing_api/self_hosted.md b/docs/cloud_pricing_api/self_hosted.md index 43f395eb..18f55ac8 100644 --- a/docs/cloud_pricing_api/self_hosted.md +++ b/docs/cloud_pricing_api/self_hosted.md @@ -5,7 +5,7 @@ title: Self-hosting import useBaseUrl from '@docusaurus/useBaseUrl'; -Most Infracost CLI users connect to our hosted Cloud Pricing API, since [no cloud credentials or secrets are sent](/docs/faq/#what-data-is-sent-to-the-cloud-pricing-api) to it (we are also [SOC2 Type II](/security/) certified). Large enterprises that have very restrictive security policies might require self-hosting. The following diagram shows an overview of the architecture. +Most Infracost CLI users connect to our hosted Cloud Pricing API, since [no cloud credentials or secrets are sent](/docs/faq/#what-data-is-sent-to-the-cloud-pricing-api) to it (we are also SOC2 Type II certified). Large enterprises that have very restrictive security policies might require self-hosting. The following diagram shows an overview of the architecture. ![Deployment overview](/img/docs/cloud_pricing_api/deployment_overview.png "Deployment overview") diff --git a/docs/faq.md b/docs/faq.md index 806891aa..15a7bd98 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -5,7 +5,7 @@ title: FAQ ## How does Infracost work? -Infracost has a [CLI](https://github.com/infracost/infracost) and a [Cloud Pricing API](https://github.com/infracost/cloud-pricing-api) backend service, as well as many [CI/CD integrations](/docs/integrations/cicd). There is also a SaaS product, [Infracost Cloud](/pricing/), that complements the open source CLI by giving teams advanced visibility and controls. +Infracost has a [CLI](https://github.com/infracost/infracost) and a [Cloud Pricing API](https://github.com/infracost/cloud-pricing-api) backend service, as well as many [CI/CD integrations](/docs/integrations/cicd). There is also a SaaS product, Infracost Cloud, that complements the open source CLI by giving teams advanced visibility and controls. When the CLI runs, it: 1. **Extracts cost-related parameters**
@@ -22,7 +22,7 @@ When the CLI runs, it: ## Security and Privacy -Security is of paramount importance to us. We are SOC 2 Type II certified. Our [Security page](/security) gives an overview of the processes and systems Infracost has in place to ensure we are continually protecting our users' data. +Security is of paramount importance to us. We are SOC 2 Type II certified. Our Security page gives an overview of the processes and systems Infracost has in place to ensure we are continually protecting our users' data. If you have any questions or concerns, please [contact us](mailto:hello@infracost.io). @@ -96,7 +96,7 @@ If you have [enabled](/docs/infracost_cloud/get_started/) this, the CLI sends it ### Do you sell my data? -No. Infracost is backed by top-tier investors including Y Combinator and Sequoia. We also have an [paid product](/pricing). For more information about how we handle data see our [Privacy Policy](/docs/privacy-policy). +No. Infracost is backed by top-tier investors including Y Combinator and Sequoia. We also have an paid product. For more information about how we handle data see our [Privacy Policy](/docs/privacy-policy). ### How should I report a security vulnerability? @@ -139,7 +139,7 @@ Sure! See the [currency](/docs/features/environment_variables/#infracost_currenc ### What's the difference between source control and CI/CD integration? -Source control integration is when you connect Infracost directly to your GitHub or GitLab. CI/CD integration is when you install the Infracost CLI in your CI/CD pipelines and run commands. +Source control integration is when you connect Infracost directly to your GitHub or GitLab. CI/CD integration is when you install the Infracost CLI in your CI/CD pipelines and run commands. We recommend source control integration as it is much simpler to setup, and faster to run. [This page](/docs/guides/source_control_benefits/) explains more about the benefits of source control integrations over CI/CD integrations. diff --git a/docs/integrations/github_app.md b/docs/integrations/github_app.md index 4f0282d8..6a887183 100644 --- a/docs/integrations/github_app.md +++ b/docs/integrations/github_app.md @@ -5,7 +5,7 @@ title: GitHub App (recommended) import useBaseUrl from '@docusaurus/useBaseUrl'; -The Infracost GitHub App is an automated integration meaning that Infracost runs on our infrastructure and we keep it up to date. Infracost is trusted by thousands of companies around the world, including many of the Fortune 500. We are [SOC 2 Type II](/security) certified. +The Infracost GitHub App is an automated integration meaning that Infracost runs on our infrastructure and we keep it up to date. Infracost is trusted by thousands of companies around the world, including many of the Fortune 500. We are SOC 2 Type II certified. | 1. Install the Infracost GitHub App | 2. Get pull request comments | |--------------|-----------| diff --git a/docs/integrations/gitlab_app.md b/docs/integrations/gitlab_app.md index ce5a87b3..ff591832 100644 --- a/docs/integrations/gitlab_app.md +++ b/docs/integrations/gitlab_app.md @@ -5,7 +5,7 @@ title: GitLab App (recommended) import useBaseUrl from '@docusaurus/useBaseUrl'; -The Infracost GitLab App is an automated integration meaning that Infracost runs on our infrastructure and we keep it up to date. Infracost is trusted by thousands of companies around the world, including many of the Fortune 500. We are [SOC 2 Type II](/security) certified. +The Infracost GitLab App is an automated integration meaning that Infracost runs on our infrastructure and we keep it up to date. Infracost is trusted by thousands of companies around the world, including many of the Fortune 500. We are SOC 2 Type II certified. | 1. Install the Infracost GitLab App | 2. Get merge request comments | |--------------|-----------| diff --git a/docs/integrations/terraform_cloud_enterprise.md b/docs/integrations/terraform_cloud_enterprise.md index ce3197e3..226eaebb 100644 --- a/docs/integrations/terraform_cloud_enterprise.md +++ b/docs/integrations/terraform_cloud_enterprise.md @@ -19,7 +19,7 @@ Our CI/CD integrations run the Infracost CLI and parse Terraform HCL code direct This option uses the Terraform plan JSON that Terraform Cloud/Enterprise generates. The following features are not currently supported by this option: posting pull request comments, multiple currencies, modelling usage-based resources via the usage-file. Please [contact us](mailto:hello@infracost.io) if you need these features. -[Terraform Run Tasks](/blog/terraform-runtasks-what-why-how/) can be used to integrate Infracost into Terraform Cloud/Enterprise directly. It sits between the plan and apply stage and shows a cost estimate for the changes that are about to be deployed. There is also a shareable details link that will open a pre-authenticated link with a detailed breakdown of costs per resource. +Terraform Run Tasks] can be used to integrate Infracost into Terraform Cloud/Enterprise directly. It sits between the plan and apply stage and shows a cost estimate for the changes that are about to be deployed. There is also a shareable details link that will open a pre-authenticated link with a detailed breakdown of costs per resource. #### 1. Generate Infracost Endpoint Sign up or log in to [Infracost Cloud](https://dashboard.infracost.io/tfc-sign-up) and go to the Integrations page to enable the Terraform Cloud integration. This creates an Infracost endpoint URL and HMAC key that you'll use in the next step. You can also create an organization in Infracost to match the organization name you have in Terraform Cloud. diff --git a/docs/integrations/third_party_integrations.md b/docs/integrations/third_party_integrations.md index 53a4fa40..4ef11741 100644 --- a/docs/integrations/third_party_integrations.md +++ b/docs/integrations/third_party_integrations.md @@ -24,7 +24,7 @@ Infracost can also be used alongside third-party systems including: Please follow these steps when creating a third-party integration with Infracost: 1. **User-specific API keys**: ask your users to sign up for their own free Infracost API key and enter that into your product's settings page. This approach is used by our partners, including HashiCorp, as it enables users to use custom price books and other user-specific Infracost features. Your docs should mention something like: - [Sign up](https://dashboard.infracost.io) and go to the Org Settings page to get your free Infracost API key. - - [Install Infracost](https://www.infracost.io/docs/#2-get-api-key) to get your free API key. + - [Install Infracost](/docs/#2-get-api-key) to get your free API key. 2. **Use Terraform directory method**: we recommend you run Infracost against a [Terraform directory](/docs/features/cli_commands/#option-1-terraform-directory) (as opposed to a Terraform plan JSON file) as that is faster and does not require you to set cloud credentials or secrets. 3. **CLI JSON format**: Infracost's CLI has a [JSON format](/docs/features/cli_commands/#examples) that you should use, e.g. get total cost estimate. We do not have language-specific clients so your application needs to run the Infracost CLI. You can also use [this API](/docs/integrations/infracost_api/) if you have a Terraform plan JSON file already. 4. **Email us**: Our email is [hello@infracost.io](mailto:hello@infracost.io), contact us if you need help or advice on the best ways to integrate, or would like to be featured in this page!