diff --git a/docs.json b/docs.json index a76ab82e56..20140591e3 100644 --- a/docs.json +++ b/docs.json @@ -82,9 +82,10 @@ { "group": "Dedicated Cloud", "pages": [ - "platform/hosting/hosting-options/dedicated_cloud", - "platform/hosting/hosting-options/dedicated_regions", - "platform/hosting/export-data-from-dedicated-cloud" + "platform/hosting/hosting-options/dedicated-cloud", + "platform/hosting/hosting-options/dedicated-cloud/rate-limits", + "platform/hosting/hosting-options/dedicated-cloud/regions", + "platform/hosting/hosting-options/dedicated-cloud/export-data" ] }, { @@ -93,6 +94,7 @@ "platform/hosting/hosting-options/self-managed", "platform/hosting/self-managed/ref-arch", "platform/hosting/self-managed/requirements", + "platform/hosting/self-managed/rate-limits", "platform/hosting/self-managed/operator", "platform/hosting/self-managed/on-premises-deployments/kubernetes-airgapped", "platform/hosting/server-upgrade-process", @@ -3890,6 +3892,22 @@ "source": "/platform/hosting/secure-storage-connector", "destination": "/platform/hosting/data-security/secure-storage-connector" }, + { + "source": "/platform/hosting/hosting-options/dedicated_cloud", + "destination": "/platform/hosting/hosting-options/dedicated-cloud" + }, + { + "source": "/platform/hosting/hosting-options/rate-limits-dedicated-cloud", + "destination": "/platform/hosting/hosting-options/dedicated-cloud/rate-limits" + }, + { + "source": "/platform/hosting/hosting-options/dedicated_regions", + "destination": "/platform/hosting/hosting-options/dedicated-cloud/regions" + }, + { + "source": "/platform/hosting/export-data-from-dedicated-cloud", + "destination": "/platform/hosting/hosting-options/dedicated-cloud/export-data" + }, { "source": "/platform/hosting/self-managed/install-on-public-cloud", "destination": "/platform/hosting/self-managed" diff --git a/ja/platform/hosting/hosting-options/self-managed.mdx b/ja/platform/hosting/hosting-options/self-managed.mdx index 880c2a753b..e24976f020 100644 --- a/ja/platform/hosting/hosting-options/self-managed.mdx +++ b/ja/platform/hosting/hosting-options/self-managed.mdx @@ -6,7 +6,7 @@ description: プロダクション環境での W&B Self-Managed のデプロイ ## クラウドまたはオンプレミスインフラストラクチャーでの W&B Self-Managed の利用 -W&B では、[W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) または [W&B 専用クラウド](/platform/hosting/hosting-options/dedicated_cloud) などの完全管理型のデプロイメントオプションを推奨しています。W&B の完全管理型サービスは、設定がほとんど不要で、シンプルかつ安全に利用できます。 +W&B では、[W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) または [W&B 専用クラウド](/platform/hosting/hosting-options/dedicated-cloud) などの完全管理型のデプロイメントオプションを推奨しています。W&B の完全管理型サービスは、設定がほとんど不要で、シンプルかつ安全に利用できます。 W&B Server は、お客様の [AWS、Google Cloud、または Azure のクラウド経由のアカウント](#deploy-wb-server-within-Self-Managed-cloud-accounts)、または [オンプレミスインフラストラクチャー](#オンプレミスインフラストラクチャーへの-wb-server-のデプロイ) 内にデプロイできます。 @@ -20,7 +20,7 @@ W&B Server は、お客様の [AWS、Google Cloud、または Azure のクラウ - W&B Self-Managed デプロイメントの継続的なメンテナンス。 -組織が規制要件の対象となる場合は、W&B がメンテナンスを行う [W&B 専用クラウド](/platform/hosting/hosting-options/dedicated_cloud.mdx) へのデプロイを検討してください。 +組織が規制要件の対象となる場合は、W&B がメンテナンスを行う [W&B 専用クラウド](/platform/hosting/hosting-options/dedicated-cloud.mdx) へのデプロイを検討してください。 - W&B 専用クラウド のホスティングプラットフォームは、SOC 2 Type 2 の要件を満たしています。 - 適切に設定された場合、W&B 専用クラウド のデプロイメントは HIPAA に準拠します。 @@ -68,4 +68,4 @@ URL にアクセスすると、**Get a License for W&B Local** フォームに 3. **Get a License** ステップの **Name of Instance** フィールドにインスタンスの名前を入力し、任意で **Description** フィールドに説明を入力します。 4. **Generate License Key** ボタンを選択します。 -デプロイメントの概要と、そのインスタンスに関連付けられたライセンスキーが表示されたページが表示されます。 \ No newline at end of file +デプロイメントの概要と、そのインスタンスに関連付けられたライセンスキーが表示されたページが表示されます。 diff --git a/ko/platform/hosting/hosting-options/self-managed.mdx b/ko/platform/hosting/hosting-options/self-managed.mdx index 7d89cb48f9..ee869a0864 100644 --- a/ko/platform/hosting/hosting-options/self-managed.mdx +++ b/ko/platform/hosting/hosting-options/self-managed.mdx @@ -6,7 +6,7 @@ description: 프로덕션 환경에 W&B Self-Managed 배포하기 ## 클라우드 또는 온프레미스 인프라에서 W&B Self-Managed 사용하기 -W&B는 [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) 또는 [W&B 전용 클라우드](/platform/hosting/hosting-options/dedicated_cloud) 배포 유형과 같은 완전 관리형 배포 옵션을 권장합니다. W&B 완전 관리형 서비스는 설정이 거의 또는 전혀 필요하지 않아 사용이 간편하고 안전합니다. +W&B는 [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) 또는 [W&B 전용 클라우드](/platform/hosting/hosting-options/dedicated-cloud) 배포 유형과 같은 완전 관리형 배포 옵션을 권장합니다. W&B 완전 관리형 서비스는 설정이 거의 또는 전혀 필요하지 않아 사용이 간편하고 안전합니다. [AWS, Google Cloud 또는 Azure 클라우드 계정](#deploy-wb-server-within-Self-Managed-cloud-accounts) 혹은 [온프레미스 인프라](#온프레미스-인프라에-wb-server-배포하기) 내에 W&B Server를 배포하세요. @@ -19,7 +19,7 @@ W&B는 [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_c - W&B Self-Managed 배포의 지속적인 유지 관리. -조직이 규제 요구 사항을 준수해야 하는 경우, W&B가 유지 관리하는 [W&B 전용 클라우드](/platform/hosting/hosting-options/dedicated_cloud.mdx)에 배포하는 것을 고려해 보세요. +조직이 규제 요구 사항을 준수해야 하는 경우, W&B가 유지 관리하는 [W&B 전용 클라우드](/platform/hosting/hosting-options/dedicated-cloud.mdx)에 배포하는 것을 고려해 보세요. - W&B 전용 클라우드의 호스팅 플랫폼은 SOC 2 Type 2 요구 사항을 충족합니다. - 적절하게 설정된 경우, W&B 전용 클라우드 배포는 HIPAA를 준수합니다. @@ -66,4 +66,4 @@ W&B 계정이 없는 경우, 계정을 먼저 생성해야 무료 라이선스 3. **Get a License** 단계의 **Name of Instance** 필드에 인스턴스 이름을 입력하고, 선택 사항으로 **Description** 필드에 설명을 입력합니다. 4. **Generate License Key** 버튼을 클릭합니다. -배포 개요와 해당 인스턴스에 연결된 라이선스 키가 표시된 페이지가 나타납니다. \ No newline at end of file +배포 개요와 해당 인스턴스에 연결된 라이선스 키가 표시된 페이지가 나타납니다. diff --git a/platform/hosting.mdx b/platform/hosting.mdx index a250a718fd..3c81835beb 100644 --- a/platform/hosting.mdx +++ b/platform/hosting.mdx @@ -21,7 +21,7 @@ Some features and functionality require an [Enterprise](https://wandb.ai/site/pr A single-tenant, fully managed service deployed in W&B's cloud infrastructure. It is the best place to onboard W&B if your organization requires conformance to strict governance controls including data residency, have need of advanced security capabilities, and are looking to optimize their AI operating costs by not having to build & manage the required infrastructure with security, scale & performance characteristics. - See **[W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud)** for more information. + See **[W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud)** for more information. diff --git a/platform/hosting/data-security/data-encryption.mdx b/platform/hosting/data-security/data-encryption.mdx index 6300d632ab..c65b401d22 100644 --- a/platform/hosting/data-security/data-encryption.mdx +++ b/platform/hosting/data-security/data-encryption.mdx @@ -2,7 +2,7 @@ title: Data encryption in Dedicated Cloud --- -W&B uses a W&B-managed cloud-native key to encrypt the W&B-managed database and object storage in every [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), by using the customer-managed encryption key (CMEK) capability in each cloud. In this case, W&B acts as a `customer` of the cloud provider, while providing the W&B platform as a service to you. Using a W&B-managed key means that W&B has control over the keys that it uses to encrypt the data in each cloud, thus doubling down on its promise to provide a highly safe and secure platform to all of its customers. +W&B uses a W&B-managed cloud-native key to encrypt the W&B-managed database and object storage in every [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), by using the customer-managed encryption key (CMEK) capability in each cloud. In this case, W&B acts as a `customer` of the cloud provider, while providing the W&B platform as a service to you. Using a W&B-managed key means that W&B has control over the keys that it uses to encrypt the data in each cloud, thus doubling down on its promise to provide a highly safe and secure platform to all of its customers. W&B uses a `unique key` to encrypt the data in each customer instance, providing another layer of isolation between Dedicated Cloud tenants. The capability is available on AWS, Azure and Google Cloud. diff --git a/platform/hosting/data-security/ip-allowlisting.mdx b/platform/hosting/data-security/ip-allowlisting.mdx index def5ee7013..c0d671de9f 100644 --- a/platform/hosting/data-security/ip-allowlisting.mdx +++ b/platform/hosting/data-security/ip-allowlisting.mdx @@ -2,7 +2,7 @@ title: Configure IP allowlisting for Dedicated Cloud --- -You can restrict access to your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) instance from only an authorized list of IP addresses. This applies to the access from your AI workloads to the W&B APIs and from your user browsers to the W&B app UI as well. Once IP allowlisting has been set up for your Dedicated Cloud instance, W&B denies any requests from other unauthorized locations. Reach out to your W&B team to configure IP allowlisting for your Dedicated Cloud instance. +You can restrict access to your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) instance from only an authorized list of IP addresses. This applies to the access from your AI workloads to the W&B APIs and from your user browsers to the W&B app UI as well. Once IP allowlisting has been set up for your Dedicated Cloud instance, W&B denies any requests from other unauthorized locations. Reach out to your W&B team to configure IP allowlisting for your Dedicated Cloud instance. IP allowlisting is available on Dedicated Cloud instances on AWS, Google Cloud and Azure. diff --git a/platform/hosting/data-security/private-connectivity.mdx b/platform/hosting/data-security/private-connectivity.mdx index 6b156930d9..588914e0be 100644 --- a/platform/hosting/data-security/private-connectivity.mdx +++ b/platform/hosting/data-security/private-connectivity.mdx @@ -2,7 +2,7 @@ title: Configure private connectivity to Dedicated Cloud --- -You can connect to your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud/) instance over the cloud provider's secure private network. This applies to the access from your AI workloads to the W&B APIs and optionally from your user browsers to the W&B app UI as well. When using private connectivity, the relevant requests and responses do not transit through the public network or internet. +You can connect to your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) instance over the cloud provider's secure private network. This applies to the access from your AI workloads to the W&B APIs and optionally from your user browsers to the W&B app UI as well. When using private connectivity, the relevant requests and responses do not transit through the public network or internet. Secure private connectivity is coming soon as an advanced security option with Dedicated Cloud. diff --git a/platform/hosting/data-security/secure-storage-connector.mdx b/platform/hosting/data-security/secure-storage-connector.mdx index e93b7a8048..381993096b 100644 --- a/platform/hosting/data-security/secure-storage-connector.mdx +++ b/platform/hosting/data-security/secure-storage-connector.mdx @@ -7,7 +7,7 @@ import ByobContextNote from "/snippets/en/_includes/byob-context-note.mdx"; ## Overview -Bring your own bucket (BYOB) allows you to store W&B artifacts and other related sensitive data in your own cloud or on-prem infrastructure. In case of [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), data that you store in your bucket is not copied to the W&B managed infrastructure. +Bring your own bucket (BYOB) allows you to store W&B artifacts and other related sensitive data in your own cloud or on-prem infrastructure. In case of [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), data that you store in your bucket is not copied to the W&B managed infrastructure. * Communication between W&B SDK / CLI / UI and your buckets occurs using [pre-signed URLs](./presigned-urls). @@ -37,7 +37,7 @@ There are two scopes you can configure your storage bucket to: | Scope | Description | |----------------|-------------| -| Instance level | In [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) and [Self-Managed](/platform/hosting/hosting-options/self-managed), any user with the required permissions within your organization or instance can access files stored in your instance's storage bucket. Not applicable to [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). | +| Instance level | In [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) and [Self-Managed](/platform/hosting/hosting-options/self-managed), any user with the required permissions within your organization or instance can access files stored in your instance's storage bucket. Not applicable to [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). | | Team level | If a W&B Team is configured to use a Team level storage bucket, team members can access files stored in it. Team level storage buckets allow greater data access control and data isolation for teams with highly sensitive data or strict compliance requirements.

Team level storage can help different business units or departments sharing an instance to efficiently use the infrastructure and administrative resources. It can also allow separate project teams to manage AI workflows for separate customer engagements. Available for all deployment types. You configure team level BYOB when setting up the team. | This flexible design allows for many different storage topologies, depending on your organization's needs. For example: @@ -293,10 +293,10 @@ For details, see [Create an S3 bucket](https://docs.aws.amazon.com/AmazonS3/late Replace `` accordingly and keep a record of the bucket name. Next, [configure W&B](#configure-byob). - If you are using [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), replace `` with the corresponding value. + If you are using [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), replace `` with the corresponding value. * For [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud): `arn:aws:iam::725579432336:role/WandbIntegration` - * For [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud): `arn:aws:iam::830241207209:root` + * For [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud): `arn:aws:iam::830241207209:root` For more details, see the [AWS Self-Managed hosting guide](/platform/hosting/hosting-options). @@ -342,10 +342,10 @@ For details, see [Create a bucket](https://docs.cloud.google.com/storage/docs/cr gsutil cors get gs:// ``` -1. If you are using [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), grant the `storage.admin` role to the Google Cloud service account linked to the W&B Platform. W&B requires this role to check the bucket's CORS configuration and attributes, such as whether object versioning is enabled. If the service account does not have the `storage.admin` role, these checks result in a HTTP 403 error. +1. If you are using [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), grant the `storage.admin` role to the Google Cloud service account linked to the W&B Platform. W&B requires this role to check the bucket's CORS configuration and attributes, such as whether object versioning is enabled. If the service account does not have the `storage.admin` role, these checks result in a HTTP 403 error. * For [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), the account is: `wandb-integration@wandb-production.iam.gserviceaccount.com` - * For [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) the account is: `deploy@wandb-production.iam.gserviceaccount.com` + * For [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) the account is: `deploy@wandb-production.iam.gserviceaccount.com` Keep a record of the bucket name. Next, [configure W&B for BYOB](#configure-byob). @@ -375,7 +375,7 @@ For details, see [Create a blob storage container](https://learn.microsoft.com/e If data in your bucket expires due to an [object lifecycle management policy](https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-policy-configure?tabs=azure-portal), you may lose the ability to read the history of some runs. -1. Generate a storage account access key and make a note of its name and the storage account name. If you are using [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), share the storage account name and access key with your W&B team using a secure sharing mechanism. +1. Generate a storage account access key and make a note of its name and the storage account name. If you are using [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), share the storage account name and access key with your W&B team using a secure sharing mechanism. **Team level BYOB**: diff --git a/platform/hosting/enterprise-licenses.mdx b/platform/hosting/enterprise-licenses.mdx index 968cc67cd1..7762199730 100644 --- a/platform/hosting/enterprise-licenses.mdx +++ b/platform/hosting/enterprise-licenses.mdx @@ -14,7 +14,7 @@ This page provides a comprehensive overview of Enterprise licenses, including wh ## Deployment Options Enterprise licenses are available for W&B Dedicated Cloud and Self-Managed deployments. -- [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) provides single-tenant infrastructure managed by W&B, deployed in Google Cloud. Dedicated Cloud deployments automatically include an Enterprise license. No additional configuration is required, and all Enterprise features are available immediately upon provisioning. +- [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) provides single-tenant infrastructure managed by W&B, deployed in Google Cloud. Dedicated Cloud deployments automatically include an Enterprise license. No additional configuration is required, and all Enterprise features are available immediately upon provisioning. - [W&B Self-Managed](/platform/hosting/hosting-options/self-managed) is deployed on your own infrastructure, providing full control over your deployment and data. Air-gapped deployments are supported. Without an Enterprise license, [Enterprise features](#enterprise-features) are unavailable. ## Obtain an Enterprise license @@ -137,5 +137,5 @@ For assistance with Enterprise licenses, contact your account team, [Sales](mail ## Additional resources - [W&B Pricing](/pricing) - [W&B Self-Managed](/platform/hosting/hosting-options/self-managed) -- [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) +- [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) - [Security & Compliance](/security) diff --git a/platform/hosting/hosting-options/dedicated_cloud.mdx b/platform/hosting/hosting-options/dedicated-cloud.mdx similarity index 88% rename from platform/hosting/hosting-options/dedicated_cloud.mdx rename to platform/hosting/hosting-options/dedicated-cloud.mdx index f5880cedce..b9119def71 100644 --- a/platform/hosting/hosting-options/dedicated_cloud.mdx +++ b/platform/hosting/hosting-options/dedicated-cloud.mdx @@ -3,15 +3,19 @@ description: Deploy W&B Dedicated Cloud in production title: Dedicated Cloud --- -W&B Dedicated Cloud is a single-tenant, fully managed platform deployed in W&B's AWS, Google Cloud, or Azure cloud accounts. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances. Your W&B specific metadata and data is stored in an isolated cloud storage and is processed using isolated cloud compute services. +W&B Dedicated Cloud is a single-tenant, fully managed platform deployed in W&B's AWS, Google Cloud, or Azure cloud accounts. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances. Your W&B specific metadata and data is stored in an isolated cloud storage and is processed using isolated cloud compute services. -W&B Dedicated Cloud is available in [multiple global regions for each cloud provider](./dedicated_regions) +W&B Dedicated Cloud is available in [multiple global regions for each cloud provider](./dedicated-cloud/regions) + +## Rate limits + +W&B applies default rate limits on Dedicated Cloud to maintain instance stability. See [Rate limits](/platform/hosting/hosting-options/dedicated-cloud/rate-limits) for default values, how limits are enforced, and how to request higher limits when you scale up training. ## Compliance -- **SOC 2**: W&B Dedicated Cloud's hosting platform meets the requirements of the [Service and Organization Controls (SOC) 2 Type 2](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2), published by the [Auditing Standards Board of the American Institute of Certified Public Accountants (AICPA)](https://www.aicpa-cima.com/home). A SOC 2 report evaluates a service organization’s controls for security, availability, processing integrity, confidentiality, and privacy. W&B Dedicated Cloud is subject to periodic internal and external audits to verify continued compliance. Refer to the [W&B Security Portal](https://security.wandb.ai/) to request the SOC 2 report and other security and compliance documents. +- **SOC 2**: W&B Dedicated Cloud's hosting platform meets the requirements of the [Service and Organization Controls (SOC) 2 Type 2](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2), published by the [Auditing Standards Board of the American Institute of Certified Public Accountants (AICPA)](https://www.aicpa-cima.com/home). A SOC 2 report evaluates a service organization's controls for security, availability, processing integrity, confidentiality, and privacy. W&B Dedicated Cloud is subject to periodic internal and external audits to verify continued compliance. Refer to the [W&B Security Portal](https://security.wandb.ai/) to request the SOC 2 report and other security and compliance documents. - **HIPAA**: When configured appropriately, W&B Dedicated Cloud meets the requirements of the [Health Insurance Portability and Accountability Act of 1996 (HIPAA)](https://www.hhs.gov/hipaa/for-professionals/index.html). Compliance with HIPAA is a shared responsibility that involves W&B, the customer, and any third-party services involved in the deployment. Organizations subject to HIPAA must have a **Business Associate Agreement** on file with W&B. Refer to the [W&B Security Portal](https://security.wandb.ai/) to request more information. -## Data security +## Data security You can bring your own bucket (BYOB) using the [secure storage connector](/platform/hosting/data-security/secure-storage-connector) at the [instance and team levels](/platform/hosting/data-security/secure-storage-connector#configuration-options) to store your files such as models, datasets, and more. @@ -21,7 +25,7 @@ Similar to W&B Multi-tenant Cloud, you can configure a single bucket for multipl Dedicated Cloud architecture diagram -In addition to BYOB with secure storage connector, you can use [IP allowlisting](/platform/hosting/data-security/ip-allowlisting) to restrict access to your Dedicated Cloud instance from only trusted network locations. +In addition to BYOB with secure storage connector, you can use [IP allowlisting](/platform/hosting/data-security/ip-allowlisting) to restrict access to your Dedicated Cloud instance from only trusted network locations. You can connect privately to your Dedicated Cloud instance using [cloud provider's secure connectivity solution](/platform/hosting/data-security/private-connectivity). diff --git a/platform/hosting/hosting-options/dedicated-cloud/export-data.mdx b/platform/hosting/hosting-options/dedicated-cloud/export-data.mdx new file mode 100644 index 0000000000..a396e05575 --- /dev/null +++ b/platform/hosting/hosting-options/dedicated-cloud/export-data.mdx @@ -0,0 +1,19 @@ +--- +description: Export data from Dedicated Cloud +title: Export data from Dedicated Cloud +--- + +If you would like to export all the data managed in your Dedicated Cloud instance, you can use the W&B SDK API to extract the runs, metrics, artifacts, and more with the [Import and Export API](/models/ref/python/public-api/). The following table covers some of the key exporting use cases. + +| Purpose | Documentation | +|---------|---------------| +| Export project metadata | [Projects API](/models/ref/python/public-api/projects) | +| Export runs in a project | [Runs API](/models/ref/python/public-api/runs) | +| Export reports | [Report and Workspace API](/models/reports/clone-and-export-reports/) | +| Export artifacts | [Explore artifact graphs](/models/artifacts/explore-and-traverse-an-artifact-graph/), [Download and use artifacts](/models/artifacts/download-and-use-an-artifact/#download-and-use-an-artifact-stored-on-wb) | + +If you manage artifacts stored in the Dedicated Cloud with [Secure Storage Connector](/platform/app/settings-page/teams/#secure-storage-connector), you may not need to export the artifacts using the W&B SDK API. + + +Using W&B SDK API to export all of your data can be slow if you have a large number of runs, artifacts etc. W&B recommends running the export process in appropriately sized batches so as not to overwhelm your Dedicated Cloud instance. + diff --git a/platform/hosting/hosting-options/dedicated-cloud/rate-limits.mdx b/platform/hosting/hosting-options/dedicated-cloud/rate-limits.mdx new file mode 100644 index 0000000000..abab4fc4f6 --- /dev/null +++ b/platform/hosting/hosting-options/dedicated-cloud/rate-limits.mdx @@ -0,0 +1,13 @@ +--- +title: Rate limits +description: Default rate limits on Dedicated Cloud and how to request changes +--- +import RateLimitsDefaultsAndNotification from "/snippets/en/_includes/rate-limits-defaults-and-notification.mdx"; + +W&B Dedicated Cloud applies rate limits to maintain instance stability. W&B can adjust limits when you scale up training or need higher throughput. + +## Default limits and notification + + + +These defaults are recommended for typical production workloads. If your workloads consistently exceed these limits, contact [W&B support](mailto:support@wandb.com) or your Account Solutions Engineer (AISE) to request higher limits. Provide details of your experimental setup and usage patterns. diff --git a/platform/hosting/hosting-options/dedicated-cloud/regions.mdx b/platform/hosting/hosting-options/dedicated-cloud/regions.mdx new file mode 100644 index 0000000000..654e54c8af --- /dev/null +++ b/platform/hosting/hosting-options/dedicated-cloud/regions.mdx @@ -0,0 +1,74 @@ +--- +title: Supported Dedicated Cloud regions +--- + +AWS, Google Cloud, and Azure support cloud computing services in multiple locations worldwide. Global regions help ensure that you satisfy requirements related to data residency & compliance, latency, cost efficiency and more. W&B supports many of the available global regions for Dedicated Cloud. + + +Reach out to W&B Support if your preferred AWS, Google Cloud, or Azure Region is not listed. W&B can validate if the relevant region has all the services that Dedicated Cloud needs and prioritize support depending on the outcome of the evaluation. + + +## Supported AWS Regions + +The following table lists [AWS Regions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html) that W&B currently supports for Dedicated Cloud instances. + +| Region location | Region name | +|-------------|--------| +|US East (Ohio)| us-east-2| +|US East (N. Virginia)|us-east-1| +|US West (N. California)|us-west-1| +|US West (Oregon)|us-west-2| +|Canada (Central)|ca-central-1| +|Europe (Frankfurt)|eu-central-1| +|Europe (Ireland)|eu-west-1| +|Europe (London)|eu-west-2| +|Europe (Milan)|eu-south-1| +|Europe (Stockholm)|eu-north-1| +|Asia Pacific (Mumbai)|ap-south-1| +|Asia Pacific (Singapore)| ap-southeast-1| +|Asia Pacific (Sydney)|ap-southeast-2| +|Asia Pacific (Tokyo)|ap-northeast-1| +|Asia Pacific (Seoul)|ap-northeast-2| + +For more information about AWS Regions, see the [Regions, Availability Zones, and Local Zones](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html) in the AWS Documentation. + +See [What to Consider when Selecting a Region for your Workloads](https://aws.amazon.com/blogs/architecture/what-to-consider-when-selecting-a-region-for-your-workloads/) for an overview of factors that you should consider when choosing an AWS Region. + +## Supported Google Cloud Regions +The following table lists [Google Cloud Regions](https://cloud.google.com/compute/docs/regions-zones) that W&B currently supports for Dedicated Cloud instances. + +| Region location | Region name | +|-------------|--------| +|South Carolina|us-east1| +|N. Virginia|us-east4| +|Iowa|us-central1| +|Oregon|us-west1| +|Los Angeles|us-west2| +|Las Vegas|us-west4| +|Toronto|northamerica-northeast2| +|Belgium|europe-west1| +|London|europe-west2| +|Frankfurt|europe-west3| +|Netherlands|europe-west4| +|Sydney|australia-southeast1| +|Tokyo|asia-northeast1| +|Seoul|asia-northeast3| + +For more information about Google Cloud Regions, see [Regions and zones](https://cloud.google.com/compute/docs/regions-zones) in the Google Cloud Documentation. + +## Supported Azure Region +The following table lists [Azure regions](https://azure.microsoft.com/explore/global-infrastructure/geographies/#geographies) that W&B currently supports for Dedicated Cloud instances. + +| Region location | Region name | +|-------------|--------| +|Virginia|eastus| +|Iowa|centralus| +|Washington|westus2| +|California|westus| +|Canada Central|canadacentral| +|France Central|francecentral| +|Netherlands|westeurope| +|Tokyo, Saitama|japaneast| +|Seoul|koreacentral| + +For more information about Azure regions, see [Azure geographies](https://azure.microsoft.com/explore/global-infrastructure/geographies/#overview) in the Azure Documentation. diff --git a/platform/hosting/hosting-options/multi_tenant_cloud.mdx b/platform/hosting/hosting-options/multi_tenant_cloud.mdx index 06d6d82d9d..8cc7fc1cbc 100644 --- a/platform/hosting/hosting-options/multi_tenant_cloud.mdx +++ b/platform/hosting/hosting-options/multi_tenant_cloud.mdx @@ -14,7 +14,7 @@ W&B Multi-tenant Cloud scales to meet your organization's needs, and supports lo ## Compliance W&B Multi-tenant Cloud's hosting platform meets the requirements of the [Service and Organization Controls (SOC) 2 Type 2](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2), published by the [Auditing Standards Board of the American Institute of Certified Public Accountants (AICPA)](https://www.aicpa-cima.com/home). A SOC 2 report evaluates a service organization’s controls for security, availability, processing integrity, confidentiality, and privacy. W&B Multi-tenant Cloud is subject to periodic internal and external audits to verify continued compliance. Refer to the [W&B Security Portal](https://security.wandb.ai/) to request the SOC 2 report and other security and compliance documents. -W&B Multi-tenant Cloud does not meet the requirements of the [Health Insurance Portability and Accountability Act of 1996 (HIPAA)](https://www.hhs.gov/hipaa/for-professionals/index.html). If your organization is subject to HIPAA, consider [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) instead. +W&B Multi-tenant Cloud does not meet the requirements of the [Health Insurance Portability and Accountability Act of 1996 (HIPAA)](https://www.hhs.gov/hipaa/for-professionals/index.html). If your organization is subject to HIPAA, consider [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) instead. ## Data security diff --git a/platform/hosting/hosting-options/self-managed.mdx b/platform/hosting/hosting-options/self-managed.mdx index 0791a3e5ab..85ee3f4625 100644 --- a/platform/hosting/hosting-options/self-managed.mdx +++ b/platform/hosting/hosting-options/self-managed.mdx @@ -6,7 +6,7 @@ sidebarTitle: Deployment overview -W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. +W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. Deploy W&B Server on your [AWS, Google Cloud, or Azure cloud account](#deploy-wb-server-within-Self-Managed-cloud-accounts) or within your [on-premises infrastructure](#deploy-wb-server-in-on-prem-infrastructure). @@ -19,7 +19,7 @@ Your IT/DevOps/MLOps team is responsible for: - Continuously maintaining your W&B Self-Managed W&B deployment. -If your organization is subject to regulatory requirements, consider deploying on [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud.mdx), which is maintained by W&B. +If your organization is subject to regulatory requirements, consider deploying on [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), which is maintained by W&B. - W&B Dedicated Cloud's hosting platform meets the requirements of SOC 2 Type 2. - When configured appropriately, a W&B Dedicated Cloud deployment complies with HIPAA. @@ -38,6 +38,8 @@ Configuration follows a hierarchy: **Release Channel Values** (defaults from W&B - To deploy W&B Self-Managed to a custom cloud platform that is not AWS, the requirements are similar to the requirements for deploying in [on-prem infrastructure](#deploy-wb-server-in-on-prem-infrastructure). - To deploy W&B Self-Managed in air-gapped environments, see [Deploy on Air-Gapped Kubernetes](/platform/hosting/self-managed/on-premises-deployments/kubernetes-airgapped). +You can optionally [configure rate limits](/platform/hosting/self-managed/rate-limits) on your instance to maintain stability. See [Rate limits](/platform/hosting/self-managed/rate-limits) for default values and notification behavior. + ## Required infrastructure All deployment options depend on the following infrastructure: diff --git a/platform/hosting/iam/advanced_env_vars.mdx b/platform/hosting/iam/advanced_env_vars.mdx index 287b0cb75f..9ae629d2e1 100644 --- a/platform/hosting/iam/advanced_env_vars.mdx +++ b/platform/hosting/iam/advanced_env_vars.mdx @@ -2,7 +2,7 @@ title: Advanced IAM configuration --- -In addition to basic [environment variables](../env-vars), you can use environment variables to configure IAM options for your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instance. +In addition to basic [environment variables](../env-vars), you can use environment variables to configure IAM options for your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instance. Choose any of the following environment variables for your instance depending on your IAM needs. diff --git a/platform/hosting/iam/identity_federation.mdx b/platform/hosting/iam/identity_federation.mdx index fda25bddd4..5db463274a 100644 --- a/platform/hosting/iam/identity_federation.mdx +++ b/platform/hosting/iam/identity_federation.mdx @@ -45,7 +45,7 @@ As part of the workflow to exchange the JWT for a W&B access token and then acce * The JWT signature is verified using the JWKS at the W&B organization level. This is the first line of defense, and if this fails, that means there's a problem with your JWKS or how your JWT is signed. * The `iss` claim in the JWT should be equal to the issuer URL configured at the organization level. * The `sub` claim in the JWT should be equal to the user's email address as configured in the W&B organization. -* The `aud` claim in the JWT should be equal to the name of the W&B organization which houses the project that you are accessing as part of your AI workflow. In case of [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instances, you could configure an instance-level environment variable `SKIP_AUDIENCE_VALIDATION` to `true` to skip validation of the audience claim, or use `wandb` as the audience. +* The `aud` claim in the JWT should be equal to the name of the W&B organization which houses the project that you are accessing as part of your AI workflow. In case of [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instances, you could configure an instance-level environment variable `SKIP_AUDIENCE_VALIDATION` to `true` to skip validation of the audience claim, or use `wandb` as the audience. * The `exp` claim in the JWT is checked to see if the token is valid or has expired and needs to be refreshed. ## External service accounts diff --git a/platform/hosting/iam/org_team_struct.mdx b/platform/hosting/iam/org_team_struct.mdx index b9f1607668..95806026c0 100644 --- a/platform/hosting/iam/org_team_struct.mdx +++ b/platform/hosting/iam/org_team_struct.mdx @@ -10,7 +10,7 @@ An *Organization* is the root scope in your W&B account or instance. All actions If you are using [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), you may have more than one organization where each may correspond to a business unit, a personal user, a joint partnership with another business and more. -If you are using [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or a [Self-Managed instance](/platform/hosting/hosting-options/self-managed), it corresponds to one organization. Your company may have more than one of Dedicated Cloud or Self-Managed instances to map to different business units or departments, though that is strictly an optional way to manage AI practioners across your businesses or departments. +If you are using [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or a [Self-Managed instance](/platform/hosting/hosting-options/self-managed), it corresponds to one organization. Your company may have more than one of Dedicated Cloud or Self-Managed instances to map to different business units or departments, though that is strictly an optional way to manage AI practioners across your businesses or departments. For more information, see [Manage organizations](./access-management/manage-organization). diff --git a/platform/hosting/iam/service-accounts.mdx b/platform/hosting/iam/service-accounts.mdx index 7871cbd813..05361ac5e6 100644 --- a/platform/hosting/iam/service-accounts.mdx +++ b/platform/hosting/iam/service-accounts.mdx @@ -35,7 +35,7 @@ Service accounts are particularly useful for: - **Airflow/Prefect/Dagster**: ML pipeline orchestration tools -Service accounts are available on [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), [Self-Managed instances](/platform/hosting/hosting-options/self-managed) with an enterprise license, and enterprise accounts in [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). +Service accounts are available on [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), [Self-Managed instances](/platform/hosting/hosting-options/self-managed) with an enterprise license, and enterprise accounts in [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). ## Organization-scoped service accounts diff --git a/platform/hosting/iam/sso.mdx b/platform/hosting/iam/sso.mdx index 8e77849efc..ec9fe6a9c1 100644 --- a/platform/hosting/iam/sso.mdx +++ b/platform/hosting/iam/sso.mdx @@ -16,9 +16,9 @@ The ID token is a JWT that contains the user's identity information, such as the In the context of W&B, access tokens authorize requests to APIs on behalf of the user, but since W&B’s primary concern is user authentication and identity, it only requires the ID token. -You can use environment variables to [configure IAM options](/platform/hosting/iam/advanced_env_vars) for your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instance. +You can use environment variables to [configure IAM options](/platform/hosting/iam/advanced_env_vars) for your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instance. -To assist with configuring Identity Providers for [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) W&B installations, follow these guidelines to follow for various IdPs. If you’re using the SaaS version of W&B, reach out to [support@wandb.com](mailto:support@wandb.com) for assistance in configuring an Auth0 tenant for your organization. +To assist with configuring Identity Providers for [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) W&B installations, follow these guidelines to follow for various IdPs. If you’re using the SaaS version of W&B, reach out to [support@wandb.com](mailto:support@wandb.com) for assistance in configuring an Auth0 tenant for your organization. ## Configure your IdP This section shows how to configure your identity provider (IdP) for OIDC. Select the tab for your IdP for details. diff --git a/platform/hosting/monitoring-usage/audit-logging.mdx b/platform/hosting/monitoring-usage/audit-logging.mdx index 900a4f6674..6aad0cc877 100644 --- a/platform/hosting/monitoring-usage/audit-logging.mdx +++ b/platform/hosting/monitoring-usage/audit-logging.mdx @@ -8,7 +8,7 @@ How to access audit logs depends on your W&B platform deployment type: | W&B Platform Deployment type | Audit logs access mechanism | |----------------------------|--------------------------------| -| [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) |
  • [Instance-level BYOB](/platform/hosting/data-security/secure-storage-connector): Synced to instance-level bucket (BYOB) every 10 minutes. Also available using [the API](#fetch-audit-logs-using-api).
  • Default instance-level storage: Available only by using [the API](#fetch-audit-logs-using-api).
| +| [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) |
  • [Instance-level BYOB](/platform/hosting/data-security/secure-storage-connector): Synced to instance-level bucket (BYOB) every 10 minutes. Also available using [the API](#fetch-audit-logs-using-api).
  • Default instance-level storage: Available only by using [the API](#fetch-audit-logs-using-api).
| | [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) | Available for Enterprise plans only. Available only by using [the API](#fetch-audit-logs-using-api). | | [Self-Managed](/platform/hosting/hosting-options/self-managed) | Synced to instance-level bucket every 10 minutes. Also available using [the API](#fetch-audit-logs-using-api). | @@ -18,7 +18,7 @@ For more details about the format of the logs, see [Audit log schema](#audit-log ## Audit log retention - If you require audit logs to be retained for a specific period of time, W&B recommends periodically transferring logs to long-term storage, either using storage buckets or the Audit Logging API. -- If you are subject to the [Health Insurance Portability and Accountability Act of 1996 (HIPAA)](https://hhs.gov/hipaa/for-professionals/index.html), audit logs must be retained for a minimum of 6 years in an environment where they cannot be deleted or modified by any internal or exterrnal actor before the end of the mandatory retention period. For HIPAA-compliant [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud) instances with [BYOB](/platform/hosting/data-security/secure-storage-connector), you must configure guardrails for your managed storage, including any long-term retention storage. +- If you are subject to the [Health Insurance Portability and Accountability Act of 1996 (HIPAA)](https://hhs.gov/hipaa/for-professionals/index.html), audit logs must be retained for a minimum of 6 years in an environment where they cannot be deleted or modified by any internal or exterrnal actor before the end of the mandatory retention period. For HIPAA-compliant [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) instances with [BYOB](/platform/hosting/data-security/secure-storage-connector), you must configure guardrails for your managed storage, including any long-term retention storage. ## Audit log schema This table shows all keys which may appear in an audit log entry, ordered alphabetically. Depending on the action and the circumstances, a specific log entry may include only a subset of the possible fields. @@ -49,7 +49,7 @@ This table shows all keys which may appear in an audit log entry, ordered alphab Personally identifiable information (PII), such as email addresses and the names of projects, teams, and reports, is available only using the API endpoint option. - For [Self-Managed](/platform/hosting/hosting-options/self-managed) and - [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), an organization admin can [exclude PII](#exclude-pii) when fetching audit logs. + [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), an organization admin can [exclude PII](#exclude-pii) when fetching audit logs. - For [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), the API endpoint always returns relevant fields for audit logs, including PII. This is not configurable. ## Before you begin @@ -89,7 +89,7 @@ The API response contains new-line separated JSON objects. Objects will include To use basic authentication with your API key to access the audit logs API, set the HTTP request's `Authorization` header to the string `Basic` followed by a space, then the base-64 encoded string in the format `username:API-KEY`. In other words, replace the username and API key with your values separated with a `:` character, then base-64-encode the result. For example, to authorize as `demo:p@55w0rd`, the header should be `Authorization: Basic ZGVtbzpwQDU1dzByZA==`. ### Exclude PII when fetching audit logs -For [Self-Managed](/platform/hosting/hosting-options/self-managed) and [Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud), a W&B organization or instance admin can exclude PII when fetching audit logs. For [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), the API endpoint always returns relevant fields for audit logs, including PII. This is not configurable. +For [Self-Managed](/platform/hosting/hosting-options/self-managed) and [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud), a W&B organization or instance admin can exclude PII when fetching audit logs. For [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud), the API endpoint always returns relevant fields for audit logs, including PII. This is not configurable. To exclude PII, pass the `anonymize=true` URL parameter. For example, if your W&B instance URL is `https://mycompany.wandb.io` and you would like to get audit logs for user activity within the last week and exclude PII, use an API endpoint like: diff --git a/platform/hosting/self-managed/operator.mdx b/platform/hosting/self-managed/operator.mdx index 09a55782c1..a68e0c09a8 100644 --- a/platform/hosting/self-managed/operator.mdx +++ b/platform/hosting/self-managed/operator.mdx @@ -347,7 +347,7 @@ For full infrastructure-plus-application deployment on AWS, Google Cloud, or Azu ## Deploy with Terraform on public cloud -W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud/) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. +W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. W&B provides Terraform modules for deploying the platform on public cloud providers. These modules automate the provisioning of infrastructure and installation of W&B Server. diff --git a/platform/hosting/self-managed/rate-limits.mdx b/platform/hosting/self-managed/rate-limits.mdx new file mode 100644 index 0000000000..7abf934424 --- /dev/null +++ b/platform/hosting/self-managed/rate-limits.mdx @@ -0,0 +1,13 @@ +--- +title: Rate limits +description: Optional rate limits on Self-Managed instances for stability +--- +import RateLimitsDefaultsAndNotification from "/snippets/en/_includes/rate-limits-defaults-and-notification.mdx"; + +You can configure rate limits on your W&B Self-Managed instance to maintain stability and prevent one user or workload from negatively impacting others. These limits are optional. If you do not set them, the instance does not enforce the limits described below. + +## Default limits and notification + + + +These defaults are recommended for typical production workloads. If your workloads consistently exceed these limits, you can configure these limits (or leave them unset) according to your instance size and shared usage. For configuration details, refer to [Deploy W&B with Kubernetes Operator](/platform/hosting/self-managed/operator) or contact [W&B support](mailto:support@wandb.com). diff --git a/platform/hosting/self-managed/ref-arch.mdx b/platform/hosting/self-managed/ref-arch.mdx index 5e58f777d8..20769d3def 100644 --- a/platform/hosting/self-managed/ref-arch.mdx +++ b/platform/hosting/self-managed/ref-arch.mdx @@ -23,7 +23,7 @@ Consider carefully whether a Self-Managed approach with W&B is suitable for your A strong understanding of how to run and maintain production-grade application is an important prerequisite before you deploy Self-Managed W&B. If your team needs assistance, our Professional Services team and partners offer support for implementation and optimization. -To learn more about managed solutions for running W&B instead of managing it yourself, refer to [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) and [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud). +To learn more about managed solutions for running W&B instead of managing it yourself, refer to [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) and [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud). ## Infrastructure diff --git a/platform/hosting/self-managed/requirements.mdx b/platform/hosting/self-managed/requirements.mdx index f978dc1206..454ea9fd86 100644 --- a/platform/hosting/self-managed/requirements.mdx +++ b/platform/hosting/self-managed/requirements.mdx @@ -17,7 +17,7 @@ import SelfManagedObtainLicense from "/snippets/en/_includes/self-managed-obtain This page provides a comprehensive overview of the infrastructure and software requirements for deploying W&B Self-Managed. Review these requirements before beginning your deployment. -W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated_cloud/) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. +W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) or [W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required. For complete architectural guidance, see the [reference architecture](/platform/hosting/self-managed/ref-arch/). diff --git a/snippets/en/_includes/rate-limits-defaults-and-notification.mdx b/snippets/en/_includes/rate-limits-defaults-and-notification.mdx new file mode 100644 index 0000000000..d8f5d4585c --- /dev/null +++ b/snippets/en/_includes/rate-limits-defaults-and-notification.mdx @@ -0,0 +1,18 @@ +The following default limits help maintain platform stability: + +| Limit | Default | Scope | +|-------|---------|-------| +| Filestream requests per second | 500 | Project | +| Filestream ingestion per second | 120 MB | Project | +| Filestream requests per second | 2 | Run | +| Run creation requests per second | 80 | Project | + +When a limit is exceeded, the W&B SDK returns HTTP response `429`, and the message `HTTP 429: rate limited exceeded` appears in the SDK logs. + +- Filesystem rate limits never cause logging to crash or fail. When the SDK receives a `429` response on a filestream request, it will back off and retry the rate-limited request as-is, while subsequent updates accumulate. + +- Run creation rate limits block further training. + +``` +HTTP 429: rate limit exceeded +```