github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 18:18:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix ambiguity in saas access use case prereqs (#4762)

Browse Source 
Just a minor wording change.
This commit is contained in:
Jamil
2024-04-24 12:03:29 -07:00
committed by GitHub
parent 5dc52edecc
commit cdeb77c5d5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/src/app/kb/use-cases/saas-app-access/readme.mdx
View File

@@ -22,8 +22,6 @@ into an **app connector** for SaaS applications that support IP allowlists.
## Prerequisites
- Any SaaS app that supports IP allowlists, configured to allow the public IP
address(es) of the NAT Gateway(s) you deployed above.
- A Site with a descriptive name to use for deploying Gateways for this use
case, for example `SaaS connectors`. [Create a Site](/kb/deploy/sites) if you
haven't already.
@@ -33,6 +31,8 @@ into an **app connector** for SaaS applications that support IP allowlists.
[Terraform examples](https://www.github.com/firezone/firezone/tree/main/terraform/examples)
for examples on how to automate deploying multiple Gateways to various cloud
providers.
- Any SaaS app that supports IP allowlists, configured to allow the public IP
address(es) of the Gateway(s) you want to use.
<Alert color="warning">
For reliable access to your SaaS apps, we always recommend deploying multiple