From 993b46cb3629bf8e1aaa7bd16c55b19b05947ec6 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 9 Dec 2024 20:19:45 +0530 Subject: [PATCH] Cloud Service - Removing - Cloud Service Hosted docs Under Cloud Service, the following topics are edited - index.mdx - Planning - your cloud account WIP Creating a Cluster - --- .../creating_cluster/creating_a_cluster.mdx | 11 ++--- .../cloud-service/getting_started/index.mdx | 9 ++-- .../edb_hosted_cloud_service.mdx | 42 ------------------- .../choosing_your_deployment/index.mdx | 17 -------- .../getting_started/planning/index.mdx | 2 +- .../your_cloud_account.mdx | 6 ++- .../connecting_to_your_cloud/index.mdx | 4 +- .../preparing_cloud_account/index.mdx | 2 +- .../preparing_cloud_account/preparing_aws.mdx | 2 +- .../01_understanding_qotas_in_azure.mdx | 16 +++---- .../preparing_azure/index.mdx | 10 ++--- .../preparing_gcp/index.mdx | 2 +- .../understanding_quotas_in_gcp.mdx | 8 ++-- .../edb-postgres-ai/cloud-service/index.mdx | 2 +- 14 files changed, 34 insertions(+), 99 deletions(-) delete mode 100644 advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/edb_hosted_cloud_service.mdx delete mode 100644 advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/index.mdx rename advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/{choosing_your_deployment => }/your_cloud_account.mdx (89%) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx index f4fd50a94fb..00e2bebd969 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx @@ -72,19 +72,14 @@ The following options aren't available when creating your cluster: 2. Select the number of standby replicas for your primary/standby high-availability cluster. -3. Select the type of cloud account for your cluster. You can choose EDB Hosted Cloud Service or Your Cloud Account. For more information, see [Deployment options](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/). - !!! Note - - If you use EDB Hosted Cloud Service, your estimated cloud infrastructure costs are calculated into your cluster's estimated monthly price shown at the bottom of the page. - -4. Select the cloud provider and region for your cluster. If you're using your account and haven't connected it to EDB Postgres AI Console yet, see [Connecting to your cloud](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/). +3. Select the cloud provider and region for your cluster. If you're using your account and haven't connected it to EDB Postgres AI Console yet, see [Connecting to your cloud](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/). !!! Tip For the best performance, we strongly recommend that this region be the same as your other resources that communicate with your cluster. For a list of available regions, see [Supported regions](/edb-postgres-ai/cloud-service/references/supported_regions/). If you're interested in deploying a cluster to a region that isn't currently available, contact [Support](/edb-postgres-ai/cloud-service/support_services/). -5. Select **Next: Cluster Settings** to continue to specify the required settings for your cluster. +4. Select **Next: Cluster Settings** to continue to specify the required settings for your cluster. ## Cluster Settings tab @@ -108,7 +103,7 @@ The following options aren't available when creating your cluster: 2. In the **Postgres Version** list, select the version of Postgres that you want to use. See [Database version policy](/edb-postgres-ai/cloud-service/references/supported_database_versions/) for more information. -6. In the **Instance Type** section: +6. In the **Instance Size** section: 1. Select the category that works best for your applications and workload: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/index.mdx index 99a9b67b8aa..2ef3d0aa9c2 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/index.mdx @@ -3,7 +3,6 @@ title: Getting started indexCards: simple description: High-level description of the tasks needed to get started with EDB Postgres AI Cloud Service. navigation: - - overview - planning - your_cloud_account - creating_cluster @@ -21,7 +20,7 @@ redirects: - /biganimal/latest/getting_started/overview/ --- -EDB Postgres AI Cloud Service provides hosted and managed Postgres database clusters within the EDB Postgres AI platform. +EDB Postgres AI Cloud Service provides managed Postgres database clusters within the EDB Postgres AI platform. ## Get an EDB Account @@ -29,11 +28,9 @@ To get started with EDB Postgres AI Cloud Service databases you will need an EDB Create an EDB account. For more information, see [Create an EDB account](../../console/using/introduction/#accessing-the-edb-postgres-ai-console). After setting up the account, you can access all of the features and capabilities of the EDB Postgres AI console. -EDB Postgres AI Cloud Service can host your database for you on AWS, GCP, or Azure managing the infrastructure and billing in one place - this is using EDB Hosted Cloud Service - or you can use your own cloud account to have databases deployed into your own cloud - this is using Your Cloud Account. +With EDB Postgres AI Cloud Service, you can use your own cloud account to have databases deployed into your own cloud and manage by EDB. -If you want to use your cloud account, go to our [Getting Started with your cloud account](your_cloud_account/getting_started_with_your_cloud_account) section which covers the steps needed to prepare your cloud account for Cloud Service clusters. - -For the rest of this Getting Started section, we will use EDB Hosted Cloud Service databases, because they are easy to deploy and do not require any management work on the cloud provider. The same steps apply to both EDB Hosted and Your Cloud Account databases. +For more information to use your cloud account, go to our [Getting Started with your cloud account](your_cloud_account/getting_started_with_your_cloud_account) section which covers the steps needed to prepare your cloud account for Cloud Service clusters. ## Creating a database cluster diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/edb_hosted_cloud_service.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/edb_hosted_cloud_service.mdx deleted file mode 100644 index 4c54f5f2fd0..00000000000 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/edb_hosted_cloud_service.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -navTitle: EDB Hosted Cloud Service -title: Choosing EDB Hosted Cloud Service -description: "EDB Postgres AI Cloud Service is able to host a fully managed EDB Postgres database in the EDB cloud." -redirects: -- /biganimal/latest/planning/deployment_options/deploying_bah/ ---- - -To deploy database clusters with EDB Hosted Cloud Service: - -- Understand the benefits of using the [EDB Hosted Cloud Service](#edb-hosted-cloud-service). -- Understand the requirements of [deploying a cluster with EDB Hosted Cloud Service](#deploying-a-cluster-with-edb-hosted-cloud-service). - -## EDB Hosted Cloud Service - -If you are looking for a fully hosted database solution, the Hosted option of the EDB Postgres AI Cloud Service provides a fully managed database service that allows you to focus on your applications and data, while EDB manages the database infrastructure. All you need to provide is the data and EDB manages the rest. - -The advantage of the Hosted option is that the database deploys within the EDB cloud infrastructure, so you have full control over the data. EDB's cloud infrastructure globally spans the major cloud service providers making it easy to co-locate the database with other services. - -EDB manages the database infrastructure, including backups, monitoring, and updates, and provides a single pane of glass for managing your databases, monitoring performance, and accessing logs and metrics. All of this is visible through the [EDB Postgres AI Console](/edb-postgres-ai/console/) and its single pane of glass which provides a unified view of your fully managed databases, self-managed databases (through the [EDB Postgres AI Agent](/edb-postgres-ai/console/estate/agent/)), analytics lakehouses, S3 stores and machine learning services. - -Hosted, fully managed databases are also quick to deploy and easy to scale. You can start with a small database and scale up as your data grows. EDB manages the scaling and performance of the database, so you can focus on your applications and data. - -The Hosted option is ideal for organizations that want a fully managed database solution without the complexity of managing the database infrastructure or that want to quickly deploy a database and start building applications without having to provision and manage the database infrastructure. - -The Hosted option is available for EDB Postgres Advanced Server (EPAS) and EDB Postgres Extended Server (PGE) databases. To get a fully hosted cluster, select EDB Postgres AI Cloud Service as the deployment option when you create a new database: - -
- -
- -You can deploy EDB's Postgres Advanced Server (EPAS) or Postgres Extended Server (PGE) databases as hosted databases, with a range of [deployment options](../choosing_cluster_type/) for high availability and fault tolerance. - -## Deploying a cluster with EDB Hosted Cloud Service - -To deploy clusters using EDB Hosted Cloud Service: - -- Choose what [Postgres distribution](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_postgres_distro/) available on the Cloud Service best meets your needs. - -- Select appropriate regions from the [EDB Hosted Cloud Service regions](/edb-postgres-ai/cloud-service/references/supported_regions/) to place your cloud resources closest to your users. - -- Evaluate how EDB Postgres AI charges you for [cloud infrastructure costs](/edb-postgres-ai/cloud-service/references/pricing_and_billing/#edb-hosted-cloud-service). diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/index.mdx deleted file mode 100644 index 0fae1f287fd..00000000000 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/index.mdx +++ /dev/null @@ -1,17 +0,0 @@ ---- -navTitle: Choosing deployment -title: Choosing your deployment option -description: Choose to use either EDB Hosted Cloud Service or Your Cloud Account. -indexCards: simple -redirects: - - /purl/upm/deployment-options-info/ - - /biganimal/release/overview/deployment_options/ - - /biganimal/latest/planning/deployment_options/ #generated for BigAnimal URL path removal branch -navigation: - - deploying_edb_hosted - - deploying_using_your_cloud_account ---- - -You have two deployment options with EDB Postgres AI®. You can deploy clusters using EDB Hosted Cloud Service, or you can deploy using Your Cloud Account. - -To learn about the pricing of these two deployment options, see [Pricing and billing](/edb-postgres-ai/cloud-service/references/pricing_and_billing/). diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/index.mdx index 9addea6b2a3..994dba7f17c 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/index.mdx @@ -3,7 +3,7 @@ title: Planning indexCards: simple description: To manage your databases, plan and choose your deployment, cluster type and EDB Postgres database. navigation: - - choosing_your_deployment + - your_cloud_account - choosing_cluster_type - choosing_postgres_distro redirects: diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/your_cloud_account.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/your_cloud_account.mdx similarity index 89% rename from advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/your_cloud_account.mdx rename to advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/your_cloud_account.mdx index 24937494b5a..d579a935714 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/your_cloud_account.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/planning/your_cloud_account.mdx @@ -1,6 +1,6 @@ --- -navTitle: Your Cloud Account -title: Choosing Your Cloud Account +navTitle: Deploying with Your Cloud Account +title: Deploying with Your Cloud Account description: "EDB Postgres AI Cloud Service is able to manage an EDB Postgres database in your cloud." --- @@ -8,6 +8,8 @@ To deploy database clusters with Your Cloud Account: - Understand what it means to use [Your Cloud Account](#your-cloud-account). - Understand the requirements of [deploying a cluster with Your Cloud Account](#deploying-a-cluster-with-your-cloud-account). +- To learn about the pricing, see [Pricing and billing](/edb-postgres-ai/cloud-service/references/pricing_and_billing/). + ## Your Cloud Account diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx index f0958c08f43..83e86d9bd71 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/connecting_to_your_cloud/index.mdx @@ -9,7 +9,7 @@ redirects: - /biganimal/latest/getting_started/02_connecting_to_your_cloud/ #generated for BigAnimal URL path removal branch --- -Use these techniques to connect your cloud if you're using Your Cloud Account as your [deployment option](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/). +Use these techniques to connect to your cloud account. ## Cloud Service access requirements @@ -47,7 +47,7 @@ For additional cloud provider-specific requirements, see [Setting up specific cl 1. Open your cloud provider shell in your browser. -2. Create a BigAnimal CLI credential: +2. Create a Cloud Service CLI credential: ```shell biganimal credential create --name diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx index 80b01550dc3..e7e2834cf10 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/index.mdx @@ -12,4 +12,4 @@ navigation: - preparing_gcp --- -When using Your Cloud Account, each time you create a cluster, you must ensure the readiness of your cloud to work with EDB Postgres AI. You need to perform this check only if you're not using EDB's Cloud Service as your [deployment option](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/). +When using Your Cloud Account, each time you create a cluster, you must ensure the readiness of your cloud to work with EDB Postgres AI. \ No newline at end of file diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws.mdx index 1e021edd4a9..b9ed93e2bf5 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws.mdx @@ -13,7 +13,7 @@ Before preparing your cloud account, make sure that you're assigned the followin - arn:aws:iam::aws:policy/ServiceQuotasFullAccess -EDB Postgres AI Cloud Service requires you to check the readiness of your AWS account before you deploy your clusters. (You don't need to perform this check if you're using the EDB Hosted Cloud Service as your [deployment option](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/).) The checks that you perform ensure that your AWS account is prepared to meet your clusters' requirements and resource limits, such as: +EDB Postgres AI Cloud Service requires you to check the readiness of your AWS account before you deploy your clusters. The checks that you perform ensure that your AWS account is prepared to meet your clusters' requirements and resource limits, such as: - Is the AWS CLI configured to access your AWS account? - Is there a sufficient limit on the number of vCPUs and Network Load Balancers (NLBs) left in your region? diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/01_understanding_qotas_in_azure.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/01_understanding_qotas_in_azure.mdx index d915fecbc6d..80aae6aed23 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/01_understanding_qotas_in_azure.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/01_understanding_qotas_in_azure.mdx @@ -5,11 +5,11 @@ redirects: - /biganimal/latest/getting_started/preparing_cloud_account/01_preparing_azure/01_understanding_qotas_in_azure/ #generated for BigAnimal URL path removal branch --- -Follow these BigAnimal requirements and recommended resource limits in Azure. +Follow these EDB Postgres AI Cloud Service requirements and recommended resource limits in Azure. ## Azure resource provider registrations -BigAnimal creates and manages some of the resources using resource providers. For example, if you want to store keys, you need the Microsoft.KeyVault resource provider. This resource provider offers a resource type called *vaults* for creating the key vault. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types). +EDB Postgres AI Cloud Service creates and manages some of the resources using resource providers. For example, if you want to store keys, you need the Microsoft.KeyVault resource provider. This resource provider offers a resource type called *vaults* for creating the key vault. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types). To prevent failures while creating your clusters, ensure that each of the following Azure resource providers are registered in your Azure subscription. @@ -30,7 +30,7 @@ To prevent failures while creating your clusters, ensure that each of the follow ## Regional activation resources and access requirements -The table provides BigAnimal's regional activation resources and access requirements. +The table provides Cloud Service's regional activation resources and access requirements. | Resource type | Activated region | Network access | Description | |--------------------------------------|------------------|----------------|----------------------------------------------------------------------| @@ -47,11 +47,11 @@ The table provides BigAnimal's regional activation resources and access requirem | Log analytics workspaces | Yes | N/A | Not in use for custom monitoring | !!!note -A Storage account for TFstate is created on the first activated region per BigAnimal project. It is in private network access. Private DNS zone are required for private storage account and private key vaults. +A Storage account for TFstate is created on the first activated region per Cloud Service project. It is in private network access. Private DNS zone are required for private storage account and private key vaults. !!! ## Public IP addresses limits -Every BigAnimal cluster with public network access is assigned a single public IP address, and this IP address counts against the quota for both basic and standard IP address types in a region. BigAnimal can't create more clusters if the IP address limit is reached. +Every Cloud Service cluster with public network access is assigned a single public IP address, and this IP address counts against the quota for both basic and standard IP address types in a region. Cloud Service can't create more clusters if the IP address limit is reached. ### Recommended limit @@ -67,13 +67,13 @@ The number of cores required by the database cluster depends on the instance typ - A cluster running on an E{N}sv3 instance without HA enabled uses exactly {N} ESv3 cores. - A cluster running on an E{N}sv3 instance with HA enabled and 2 replicas uses 3 \* {N} ESv3 cores. -BigAnimal requires an additional eight Dv4 virtual machine cores per region for management resources. +EDB Postgres AI Cloud Service requires an additional eight Dv4 virtual machine cores per region for management resources. -BigAnimal requires an additional six Dv4 virtual machine cores per region for periodic maintenance upgrades. +EDB Postgres AI Cloud Service requires an additional six Dv4 virtual machine cores per region for periodic maintenance upgrades. ### Recommended limits -BigAnimal recommends the following per region when requesting virtual machine resource limit increases: +EDB Postgres AI Cloud Service recommends the following per region when requesting virtual machine resource limit increases: - Total Regional vCPUs: minimum of 50 per designated region - Standard Dv4 Family vCPUs: minimum of 14 per designated region diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx index 874b307e4de..1e53d35df65 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/index.mdx @@ -7,7 +7,7 @@ redirects: - /biganimal/latest/getting_started/preparing_cloud_account/01_preparing_azure/ #generated for BigAnimal URL path removal branch --- -BigAnimal requires you to check the readiness of your Azure subscription before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/).) The checks that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: +EDB Postgres AI Cloud Service requires you to check the readiness of your Azure subscription before you deploy your clusters. The checks that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: - Are the necessary Azure resource providers registered for your subscription? - Is there a restriction on SKUs for the standard Esv3 family and standard D2_v4 VM size? @@ -15,7 +15,7 @@ BigAnimal requires you to check the readiness of your Azure subscription before ## Prerequisites -When preparing your Azure account, make sure that you're assigned either the Global Administrator role or the Privileged Role Administrator role in Azure AD and that you have the Owner role for your BigAnimal Azure subscription. +When preparing your Azure account, make sure that you're assigned either the Global Administrator role or the Privileged Role Administrator role in Azure AD and that you have the Owner role for your EDB Postgres AI Cloud Service Azure subscription. Before proceeding, see [Understanding requirements in Azure](01_understanding_qotas_in_azure) for details on planning for your clusters' requirements and resource limits in Azure. @@ -41,7 +41,7 @@ EDB provides a shell script, called [`biganimal-csp-preflight`](https://github.c | Argument | Description | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | <target-subscription> | Azure subscription ID of your BigAnimal deployment. | + | <target-subscription> | Azure subscription ID of your Cloud Service deployment. | | <region> | Azure region where your clusters are being deployed. See [Supported regions](/edb-postgres-ai/cloud-service/references/supported_regions/) for a list of possible regions. | Possible options are: @@ -49,10 +49,10 @@ EDB provides a shell script, called [`biganimal-csp-preflight`](https://github.c | Options | Description | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `-h` or `--help` | Displays the command help. | - | `-i` or `--instance-type` | Azure VM instance type for the BigAnimal cluster. The `help` command provides a list of possible VM instance types. Choose the instance type that best suits your application and workload. Choose an instance type in the memory optimized ESv3 or ESv4 series for large data sets. Choose from the compute optimized FSv2 series for compute-bound applications. Choose from the general purpose DSv3 or DSv4 series if you don't require memory or compute optimization. See [Sizes for virtual machines in Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes) for information to help you choose the appropriate instance type. | + | `-i` or `--instance-type` | Azure VM instance type for the Cloud Service cluster. The `help` command provides a list of possible VM instance types. Choose the instance type that best suits your application and workload. Choose an instance type in the memory optimized ESv3 or ESv4 series for large data sets. Choose from the compute optimized FSv2 series for compute-bound applications. Choose from the general purpose DSv3 or DSv4 series if you don't require memory or compute optimization. See [Sizes for virtual machines in Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes) for information to help you choose the appropriate instance type. | | `-a` or `--high-availability` | *DEPRECATED* - Enables high availability for the cluster. Replaced with `-x` or `--cluster-architecture` command. | | `-x` or `--cluster-architecture` | Defines the cluster architecture and can be `single`, `ha`, or `eha`. See [Supported cluster types](/edb-postgres-ai/cloud-service/references/supported_cluster_types/) for more information. | - | `-n` or `--networking` | Type of network endpoint for the BigAnimal cluster, either `public` or `private`. See [Cluster networking architecture](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/cluster_networking/) for more information. | + | `-n` or `--networking` | Type of network endpoint for the Cloud Service cluster, either `public` or `private`. See [Cluster networking architecture](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/cluster_networking/) for more information. | | `-r` or `--activate-region` | Specifies region activation if no clusters currently exist in the region. | | `--onboard` | Checks if the user and subscription are correctly configured. | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/index.mdx index b2023982394..f97b228145a 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/index.mdx @@ -19,7 +19,7 @@ Alternatively, you can have an equivalent single role, such as: - roles/owner -BigAnimal requires you to check the readiness of your Google Cloud (GCP) account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your [deployment option](/edb-postgres-ai/cloud-service/getting_started/planning/choosing_your_deployment/). The checks that you perform ensure that your Google Cloud account is prepared to meet your clusters' requirements and resource limits. +Cloud Service requires you to check the readiness of your Google Cloud (GCP) account before you deploy your clusters. The checks that you perform ensure that your Google Cloud account is prepared to meet your clusters' requirements and resource limits. ## Required APIs and services diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx index 0bb7a7d6332..15e5a2282a9 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp.mdx @@ -4,7 +4,7 @@ redirects: - /biganimal/latest/getting_started/preparing_cloud_account/preparing_gcp/understanding_quotas_in_gcp/ #generated for BigAnimal URL path removal branch --- -Follow these BigAnimal requirements and recommended resource limits in Google Cloud. +Follow these EDB Postgres AI Cloud Service requirements and recommended resource limits in Google Cloud. ## vCPU limits Any time a new VM is deployed in Google Cloud, the vCPUs for the VMs must not exceed the total vCPU limits for the region. @@ -17,12 +17,12 @@ The number of cores required by the database cluster depends on the instance typ - A cluster running on an e2-standard-{N} instance with HA enabled and 2 replicas uses 3 * {N} e2-standard cores. -BigAnimal requires an additional eight n2-standard virtual machine cores per region for management resources. +EDB Postgres AI Cloud Service requires an additional eight n2-standard virtual machine cores per region for management resources. -BigAnimal requires an additional four n2-standard virtual machine cores per region for periodic maintenance upgrades. +EDB Postgres AI Cloud Service requires an additional four n2-standard virtual machine cores per region for periodic maintenance upgrades. ## Recommended limits -BigAnimal recommends the following per region when requesting virtual machine resource limit increases: +EDB Postgres AI Cloud Service recommends the following per region when requesting virtual machine resource limit increases: - Total Regional vCPUs: minimum of 50 per designated region diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 90d5fa70dc6..0016fbdd8a4 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -30,7 +30,7 @@ The EDB Postgres AI Cloud Service itself is a fully managed cloud service that p Cloud Service builds on the [EDB Postgres Advanced Server](/epas/latest) and [EDB Postgres Extended](/pge/latest) databases and it's designed to help organizations accelerate the development and deployment of AI and analytics applications. -Databases in the EDB Postgres AI Cloud Service can run on EDB's own cloud accounts or managed by EDB on your own cloud on your behalf. +Databases in the EDB Postgres AI Cloud Service is managed by EDB on your own cloud on your behalf. ## EDB Postgres AI Cloud Service, Console, and Estate