EnterpriseDB · nidhibhammar · Dec 9, 2024
@@ -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: 
 

@@ -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,19 +20,17 @@ 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
 
 To get started with EDB Postgres AI Cloud Service databases you will need an EDB Postgres AI account.
 
 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
 

@@ -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:

@@ -1,20 +1,22 @@
 ---
-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."
 ---
 
 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
 
 For many organizations, managing databases can be a complex and time-consuming task. The Managed 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 cloud account for EDB to deploy into.

 <center>
 <a href="../../../images/fullymanaged.svg"><img width="50%" src="../../../images/fullymanaged.svg"/></a>
 </center>

 The advantage of the Managed option is that the database can deploy directly into your cloud infrastructure, so you have full control over the cloud account and the data. 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.

@@ -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 <cred> 

@@ -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.
@@ -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?

@@ -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