Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding multi cell migration page #4688

Merged
merged 15 commits into from
Dec 21, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions website/docs/docs/cloud/migration.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
title: "Multi-cell migration checklist"
id: migration
description: "Prepare for account migration to AWS cell based architecture."
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
pagination_next: null
pagination_prev: null
---

dbt Labs is in the process of migrating our U.S. based multi-tenant accounts to [AWS cell-based architecture](https://docs.aws.amazon.com/wellarchitected/latest/reducing-scope-of-impact-with-cell-based-architecture/what-is-a-cell-based-architecture.html), a critical component of the [AWS well-architected framework](https://aws.amazon.com/architecture/well-architected/?wa-lens-whitepapers.sort-by=item.additionalFields.sortDate&wa-lens-whitepapers.sort-order=desc&wa-guidance-whitepapers.sort-by=item.additionalFields.sortDate&wa-guidance-whitepapers.sort-order=desc). The benefits of the cell-based architecture will improve the performance, reliability, and security of your dbt Cloud environment, but there is some preparation required to ensure a successful migration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i used to write "U.S." as well but i was recently retrained to use "US" instead, as the more modern way of spelling it 🤷‍♀️

Suggested change
dbt Labs is in the process of migrating our U.S. based multi-tenant accounts to [AWS cell-based architecture](https://docs.aws.amazon.com/wellarchitected/latest/reducing-scope-of-impact-with-cell-based-architecture/what-is-a-cell-based-architecture.html), a critical component of the [AWS well-architected framework](https://aws.amazon.com/architecture/well-architected/?wa-lens-whitepapers.sort-by=item.additionalFields.sortDate&wa-lens-whitepapers.sort-order=desc&wa-guidance-whitepapers.sort-by=item.additionalFields.sortDate&wa-guidance-whitepapers.sort-order=desc). The benefits of the cell-based architecture will improve the performance, reliability, and security of your dbt Cloud environment, but there is some preparation required to ensure a successful migration.
dbt Labs is in the process of migrating our US based multi-tenant accounts to the [AWS cell-based architecture](https://docs.aws.amazon.com/wellarchitected/latest/reducing-scope-of-impact-with-cell-based-architecture/what-is-a-cell-based-architecture.html), a critical component of the [AWS well-architected framework](https://aws.amazon.com/architecture/well-architected/?wa-lens-whitepapers.sort-by=item.additionalFields.sortDate&wa-lens-whitepapers.sort-order=desc&wa-guidance-whitepapers.sort-by=item.additionalFields.sortDate&wa-guidance-whitepapers.sort-order=desc). The benefits of the cell-based architecture will improve the performance, reliability, and security of your dbt Cloud environment, but there is some preparation required to ensure a successful migration.

matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

This document outlines the steps that you must take to prevent service disruptions before your environment is migrated over to the cell-based architecture. This will impact areas such as login, IP restrictions, and API access.

### What’s changing? Pre-migration checklist.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

Prior to your migration date, your account admin will need to make some changes to your dbt Cloud account.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

If your account has been scheduled for migration, upon login, you will see a banner indicating your migration date. If you do not see a banner, you do not need to take any action.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

1. **IP Addresses** — dbt Cloud has new IPs that will be used to access your warehouse after the migration. Make sure to allow inbound traffic from these IPs in your firewall, and include it in any database grants. All six of the IPs below should be added to allowlists.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
* Old IPs: `52.45.144.63`, `54.81.134.249`, `52.22.161.231`
* New IPs: `52.3.77.232`, `3.214.191.130`, `34.233.79.135`
2. **APIs and integrations** — Each dbt Cloud account will be allocated a static Access URL like: `aa000.us1.dbt.com`. You should begin migrating your API access and partner integrations to use the new static subdomain as soon as possible. You can find your Access URL on:
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
* Any page where you generate or manage API tokens.
* The **Account Settings** > **Account page**.

:::important Multiple account access
Each account for which you have access will have a different, dedicated [Access URL](https://next.docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses#accessing-your-account)!
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
:::

3. **IDE sessions** — Any uncommitted changes in the IDE may be lost during the migration process. We _strongly_ encourage you to commit all changes in the IDE before your scheduled migration time.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
4. **User invitations** — Any pending user invitations will be invalidated during the migration. You can re-send the invitations once the migration is complete.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
5. **Git Integrations** — Integrations with Github, Gitlab, and Azure DevOps will need to be manually updated. We are not migrating any accounts using these integrations at this time. If you are using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
6. **SSO Integrations** — Integrations with SSO IdPs will need to be manually updated. We are not migrating any accounts using SSO at this time; if you are using one of these integrations and your account is scheduled for migration, please contact support, and we will delay your migration.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

### Post-migration
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

After migration, if you completed all of the checklist items above, your dbt Cloud resources and jobs will continue to work as they did before.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

You have the option to log into dbt Cloud at a different URL:
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
* If you were previously logging in at `cloud.getdbt.com`, you should instead plan to login at `us1.dbt.com`. The original URL will still work, but you’ll have to click through to be redirected upon login.
* You may also log in directly with your account’s unique [Access URL](https://next.docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses#accessing-your-account).
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
Loading