docs: clean up IP allow list URLs and security info re: data planes (#67074)
## What <!-- * Describe what the change is solving. Link all GitHub issues related to this change. --> This is minor docs cleanup after we released the Iowa region on GCP. There's not much to update, but it did prompt me to take a look at a few things, update some URLs, and reframe the discussion of how Airbyte is deployed to Cloud. Companion change to this UI update, but there is no dependency between them. https://github.com/airbytehq/airbyte-platform-internal/pull/17923 ## How <!-- * Describe how code changes achieve the solution. --> ## Review guide <!-- 1. `x.py` 2. `y.py` --> ## User Impact <!-- * What is the end result perceived by the user? * If there are negative side effects, please list them. --> ## Can this PR be safely reverted and rolled back? <!-- * If unsure, leave it blank. --> - [x] YES 💚 - [ ] NO ❌ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
@@ -91,10 +91,10 @@ To fill out the required information:
|
||||
|
||||
<!-- env:cloud -->
|
||||
|
||||
#### Step 4: (Airbyte Cloud Only) Allow inbound traffic from Airbyte IPs.
|
||||
#### Step 4: (Airbyte Cloud Only) Allow inbound traffic from Airbyte IPs
|
||||
|
||||
If you are on Airbyte Cloud, you will always need to modify your database configuration to allow inbound traffic from Airbyte IPs. You can find a list of all IPs that need to be allowlisted in
|
||||
our [Airbyte Security docs](../../platform/operating-airbyte/security#network-security-1).
|
||||
our [Airbyte Security docs](../../platform/operating-airbyte/ip-allowlist).
|
||||
|
||||
Now, click `Set up source` in the Airbyte UI. Airbyte will now test connecting to your database. Once this succeeds, you've configured an Airbyte MySQL source!
|
||||
|
||||
|
||||
@@ -66,10 +66,10 @@ To fill out the required information:
|
||||
|
||||
<!-- env:cloud -->
|
||||
|
||||
### Step 3: (Airbyte Cloud Only) Allow inbound traffic from Airbyte IPs.
|
||||
### Step 3: (Airbyte Cloud Only) Allow inbound traffic from Airbyte IPs
|
||||
|
||||
If you are on Airbyte Cloud, you will always need to modify your database configuration to allow inbound traffic from Airbyte IPs. You can find a list of all IPs that need to be allowlisted in
|
||||
our [Airbyte Security docs](../../platform/operating-airbyte/security#network-security-1).
|
||||
our [Airbyte Security docs](../../platform/operating-airbyte/ip-allowlist).
|
||||
|
||||
Now, click `Set up source` in the Airbyte UI. Airbyte will now test connecting to your database. Once this succeeds, you've configured an Airbyte Postgres source!
|
||||
|
||||
|
||||
@@ -61,7 +61,7 @@ If you are on Airbyte Cloud, you will always need to modify your database config
|
||||
|
||||

|
||||
|
||||
2. Add a new network, and enter the Airbyte's IPs, which you can find in our [Airbyte Security documentation](../../../platform/operating-airbyte/security#network-security-1).
|
||||
2. Add a new network, and enter the Airbyte's IPs, which you can find in our [Airbyte Security documentation](../../../platform/operating-airbyte/ip-allowlist).
|
||||
|
||||
Now, click `Set up source` in the Airbyte UI. Airbyte will now test connecting to your database. Once this succeeds, you've configured an Airbyte Postgres source!
|
||||
|
||||
|
||||
@@ -95,7 +95,7 @@ Airbyte Cloud leverages the security features of leading Cloud providers and set
|
||||
|
||||
### Physical infrastructure
|
||||
|
||||
Airbyte Cloud is currently deployed on GCP with all servers located in the United States. We use isolated pods to ensure your data is kept separate from other customers’ data.
|
||||
Airbyte Cloud uses control planes on GCP in the United States. Airbyte uses isolated pods to keep your data separate from other customers’ data. Data planes [are available](../cloud/managing-airbyte-cloud/manage-data-residency) in the United States (GCP) and European Union (AWS). If you [deploy your own data plane](../enterprise-flex/), that data plane runs in your own infrastructure.
|
||||
|
||||
Only certain Airbyte staff can access Airbyte infrastructure and technical logs for deployments, upgrades, configuration changes, and troubleshooting.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user