Merge pull request #6728 from EnterpriseDB/release/2025-04-28a

Release: 2025-04-28a

Author: nidhibhammar

advocacy_docs/edb-postgres-ai/analytics/how_to_lakehouse_sync.mdx

@@ -2,8 +2,6 @@
 title: Lakehouse Sync
 navTitle: Lakehouse Sync
 description: How to perform a Lakehouse Sync.
-directoryDefaults:
-  displayBanner: "Notice: Lakehouse Sync capabilities are no longer available in Cloud Service deployments. The documentation remains available for historical reference and will be removed in the future."
 deepToC: true
 ---
 

advocacy_docs/edb-postgres-ai/analytics/index.mdx

@@ -4,6 +4,8 @@ navTitle: Lakehouse analytics
 indexCards: simple
 iconName: Improve
 description: How EDB Postgres Lakehouse extends the power of Postgres by adding a vectorized query engine and separating storage from compute, to handle analytical workloads.  
+directoryDefaults:
+  displayBanner: "Notice: Since EDB Hosted services have been removed from the Cloud Service, Lakehouse capabilities are now only available as part of the EDB Postgres AI Hybrid Control Plane, which is currently in tech preview."
 navigation:
 - concepts
 - quick_start

advocacy_docs/edb-postgres-ai/analytics/quick_start.mdx

@@ -28,8 +28,8 @@ For more details, see [concepts](./concepts) and [reference](./reference),
 but this should cover the gist of it:
 
 * Postgres Lakehouse nodes are ephemeral, but they have NVMe hard drives for
-local cache and spill out space. Currently we support deploying them to
-EDB-hosted regions in AWS.
+local cache and spill out space. Currently we support deploying them to clusters
+created with the EDB Postgres AI Hybrid Control Plane on AWS infrastructure, which is under tech preview.
 * Postgres Lakehouse nodes are pre-configured to query benchmark datasets
 in object storage.
 * Postgres Lakehouse is generally “read-only,” but otherwise supports all
@@ -70,7 +70,7 @@ A few notes:
 
 * You will need to provide your own password. Create a secure password and save
 it to your password manager. We will not save it on our side.
-* Only AWS is supported, in BigAnimal Hosted regions.
+* Only AWS is supported, in EDB Postgres AI Hybrid Control Plane deployments.
 * You can choose EDB Postgres Advanced Server (EPAS) or EDB Postgres Extended (PGE),
 and the pricing calculator uses the same formula with license costs as it
 would for a normal EPAS or PGE single-node cluster.

advocacy_docs/edb-postgres-ai/analytics/reference/providers_and_regions.mdx

@@ -6,9 +6,8 @@ description: Supported cloud providers and regions for Lakehouse
 **AWS only**: Currently, support for all Lakehouse features (Lakehouse nodes,
 Managed Storage Locations, and Lakehouse Sync) is limited to AWS.
 
-**EDB-hosted only**: "Bring Your Own Account" (BYOA) regions are NOT currently
-supported for Lakehouse resources. Support is limited to
-ONLY **EDB Postgres® AI Hosted** environments on AWS (a.k.a. "EDB-Hosted AWS regions").
+**Hybrid Control Plane only**: Support is limited to
+ONLY **EDB Postgres® AI Hybrid Control Plane** environments on AWS.
 
 This means you can select from one of the following regions:
 
@@ -27,8 +26,8 @@ This means you can select from one of the following regions:
 
 To be precise:
 
-* Lakehouse nodes can only be provisioned in EDB-hosted AWS regions
-* Managed Storage Locations can only be created in EDB-hosted AWS regions
-* Lakehouse Sync can only sync from source databases in EDB-hosted AWS regions
+* Lakehouse nodes can only be provisioned on AWS regions of a Hybrid Control Plane deployment.  
+* Managed Storage Locations can only be created in AWS regions.
+* Lakehouse Sync can only sync from source databases in AWS regions.
 
-These limitations will be removed as we continue to improve the product. Eventually, we will support BYOA, as well as Azure and GCP, for all Lakehouse use cases.
+These limitations will be removed as we continue to improve the product. Eventually, we will support Azure and GCP, for all Lakehouse use cases.

advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_cluster.mdx

@@ -19,24 +19,18 @@ redirects:
   - /biganimal/latest/free_trial/detail/create_a_cluster/create_cluster_portal/
 ---
 
-!!!Note "When using Your Cloud"
+
+## Prerequisites
 
 Before creating your cluster, make sure you have enough resources. Without enough resources, your request to create a cluster fails. 
 
 -   If your cloud provider is Azure, see [Preparing your Azure account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/).
 -   If your cloud provider is AWS, see [Preparing your AWS account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws/).
 -   If your cloud provider is Google Cloud, see [Preparing your Google Cloud account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/).
 -   Activate a region before cluster creation. See [Activating regions](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions/).
-!!!
-
-!!!note "When using EDB Hosted Cloud"
 
-The following options aren't available when creating your cluster:
 
--   AWS IAM authentication
--   Superuser access
--   PgBouncer 
-!!!
+## Create a cluster
 
 1.  Sign in to the [EDB Postgres AI Console](https://portal.biganimal.com).
 
@@ -72,19 +66,13 @@ 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 haven't connected your account 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
 
@@ -100,23 +88,24 @@ The following options aren't available when creating your cluster:
 
     1.  In the **Postgres Type** field, select the type of Postgres you want to use:
 
-        -   **[EDB Postgres Advanced Server](/epas/latest/)** is EDB's Oracle-compatible database offering. View [a quick demonstration of Oracle compatibility on EDB Postgres AI](/edb-postgres-ai/cloud-service/using_cluster/demonstration_oracle_compatibility/). EDB Postgres Advanced Server is compatible with all three cluster types.
-
-        -   **[EDB Postgres Extended Server](/pge/latest/)** is EDB's PostgreSQL-compatible database offering that uses advanced logical replication.
-
         -   **[PostgreSQL](/supported-open-source/postgresql/)** is the open-source, object-relational database management system. PostgreSQL is compatible with single-node and primary/standby high-availability cluster types.
+        
+        -   **[EDB Postgres Extended Server](/pge/latest/)** is EDB's PostgreSQL-compatible database offering that uses advanced logical replication.
 
+        -   **[EDB Postgres Advanced Server](/epas/latest/)** is EDB's Oracle-compatible database offering. View [a quick demonstration of Oracle compatibility on EDB Postgres AI](/edb-postgres-ai/cloud-service/using_cluster/demonstration_oracle_compatibility/). EDB Postgres Advanced Server is compatible with all three cluster types.
+    
     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: 
 
     1.  Select the category that works best for your applications and workload: 
 
-        -   Memory optimized for large data sets
+        -   **General purpose** if you don't require memory or compute optimization 
+
+        -   **Memory optimized** for large data sets
 
-        -   Compute optimized for compute bound applications
+        -   **Compute optimized** for compute bound applications
 
-        -   General purpose if you don't require memory or compute optimization 
     2.  Select the instance series and size. See [Sizes for virtual machines in Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes), [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/), or the [Google Cloud Machine families resource and comparison guide](https://cloud.google.com/compute/docs/machine-resource) for information to help you choose the appropriate instance type. 
 
         !!!note
@@ -171,14 +160,12 @@ The following options aren't available when creating your cluster:
 
        When provisioning database storage, not all of the storage space you specify is available for holding your data. Some space is reserved for other purposes. For a full explanation of the structure of a Postgres data directory, see [Database File Layout](https://www.postgresql.org/docs/current/storage-file-layout.html). You can make more storage space available for data if you specify separate storage for write ahead logs (WAL). 
 
-8.  In the **Network, Logs, & Telemetry** section: <PurlAnchor urlPath="/purl/upm/private-endpoints-info" />
+8.  In the **Networking** section: <PurlAnchor urlPath="/purl/upm/private-endpoints-info" />
 
     In **Connectivity Type**, specify whether to use private or public networking. Networking is set to **Public** by default. Public means that any client can connect to your cluster’s public IP address over the internet. Optionally, you can limit traffic to your public cluster by specifying an IP allowlist, which allows access only to certain blocks of IP addresses. To limit access, select **Use allowlists** and add one or more classless inter-domain routing (CIDR) blocks. CIDR is a method for allocating IP addresses and IP routing to a whole network or subnet. If you have any CIDR block entries, access is limited to those IP addresses. If none are specified, all network traffic is allowed. 
 
     Private networking allows only IP addresses in your private network to connect to your cluster.  
 
-    If you're using private networking and you're using EDB Hosted cloud account, you must enter your cloud service provider's account information. EDB Postgres AI Cloud Service uses it to auto-approve your private endpoints and also to provide access for logging and telemetry. To enable you to create your private endpoint, Cloud Service provides you with the corresponding service name, which you can use to connect to your cluster privately. 
-
     See [Cluster networking architecture](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/cluster_networking/) for more information. 
 
 9.  To optionally make updates to your database configuration parameters, select **Next: DB Configuration**.
@@ -208,8 +195,22 @@ Change the default database backup retention period of 30 days using the
 retention period to a number of days, weeks, or months. The retention period
 must be between 1-180 days, 1-25 weeks, or 1-6 months.
 
+You can schedule a backup start time in UTC. You can choose hours and minutes in 24-hour format or choose now to start the backup immediately.
+
 Cloud Service deletes backups older than the retention period.
 
+### Access
+
+#### Identity and Access Management (IAM) Authentication
+
+<PurlAnchor urlPath="/purl/upm/csp-auth" />
+
+Enable **Identity and Access Management (IAM) Authentication** to turn on the ability to log in to Postgres using your AWS IAM credentials. For this feature to take effect, after you create the cluster, you must add each user to a role that uses AWS IAM authentication in Postgres. For details, see [IAM authentication for Postgres](/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication/#iam-authentication-for-postgres).
+
+#### Superuser Access
+
+Enable **Superuser Access** to grant superuser privileges to the edb_admin role. This option is available for single-node and primary/standby high-availability clusters. See [Notes on the edb_admin role](/edb-postgres-ai/cloud-service/using_cluster/postgres_access/admin_roles/#notes-on-the-edb_admin-role).
+
 ### Maintenance
 
 Enable the **Custom Maintenance Window** option and use the controls to set a weekly 60-minute maintenance window in which maintenance upgrades occur for the cluster. If you don't set a window, the updates are applied at EDB's discretion with prior notification.  
@@ -220,6 +221,12 @@ Enable the **Custom Maintenance Window** option and use the controls to set a we
 
 For more information, see [Periodic maintenance](/edb-postgres-ai/cloud-service/managing_your_cluster/periodic_maintenance/).
 
+### Extensions
+
+Enable **pgvector** extension to add support for vector storage and vector similarity search in Postgres. For more information, see [Blog on Vector](https://www.enterprisedb.com/blog/what-is-pgvector).
+
+Enable **PostGIS** extension to extend the capabilities of PostgreSQL relational database by adding support for sorting, indexing and querying the geographic data.
+
 ### Connections
 
 <PurlAnchor urlPath="/purl/upm/connections/" />
@@ -257,18 +264,6 @@ Enable **PgBouncer** to have it manage your connections to Postgres databases an
 
 Use the **PgBouncer Configuration Settings** menu to set PgBouncer-specific settings. Select the **Read-Write** and **Read-Only** tabs according to the type of connection you want to configure. The **Read-Only** tab is available if you're creating a primary/standby high-availability cluster and have enabled read-only workloads. 
 
-### Access
-
-#### Identity and Access Management (IAM) Authentication
-
-<PurlAnchor urlPath="/purl/upm/csp-auth" />
-
-Enable **Identity and Access Management (IAM) Authentication** to turn on the ability to log in to Postgres using your AWS IAM credentials. For this feature to take effect, after you create the cluster, you must add each user to a role that uses AWS IAM authentication in Postgres. For details, see [IAM authentication for Postgres](/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication/#iam-authentication-for-postgres).
-
-#### Superuser Access
-
-Enable **Superuser Access** to grant superuser privileges to the edb_admin role. This option is available for single-node and primary/standby high-availability clusters. See [Notes on the edb_admin role](/edb-postgres-ai/cloud-service/using_cluster/postgres_access/admin_roles/#notes-on-the-edb_admin-role).
-
 ### Security
 
 <PurlAnchor urlPath="/purl/upm/tde-security/" />

advocacy_docs/edb-postgres-ai/cloud-service/getting_started/creating_cluster/creating_a_dha_cluster.mdx

@@ -7,24 +7,17 @@ redirects:
 deepToC: true
 ---
 
-!!!Note "When using Your Cloud"
+## Prerequistes
 
 Before creating your cluster, make sure you have enough resources. Without enough resources, your request to create a cluster fails. 
 
 -   If your cloud provider is Azure, see [Preparing your Azure account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_azure/).
 -   If your cloud provider is AWS, see [Preparing your AWS account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_aws/).
 -   If your cloud provider is Google Cloud, see [Preparing your Google Cloud account](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/preparing_cloud_account/preparing_gcp/).
 -   Activate a region before cluster creation. See [Activating regions](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/managing_regions/).
-!!!
 
-!!!note "When using EDB Hosted Cloud"
 
-The following options aren't available when creating your cluster:
-
--   AWS IAM authentication
--   Superuser access
--   PgBouncer 
-!!!
+## Create a cluster
 
 1.  Sign in to the [EDB Postgres AI Console](https://portal.biganimal.com).
 
@@ -38,27 +31,21 @@ The following options aren't available when creating your cluster:
 
     -   [Distributed High Availability](/edb-postgres-ai/cloud-service/references/supported_cluster_types/distributed_highavailability/) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions to deliver higher performance and faster recovery.<br/><br/>
 
-    If you want to create a single-node or primary/standby high-availability cluster, follow the [Single Node or Primary/Standby High Availability](.) page.
+    If you want to create a single-node or primary/standby high-availability cluster, follow the [Single Node or Primary/Standby High Availability](../creating_cluster/creating_a_cluster.mdx) page.
 
     See [Supported cluster types](/edb-postgres-ai/cloud-service/references/supported_cluster_types/) for more information about the different cluster types.
 
     !!!Note
 
        You can't switch from a single-node or primary/standby high-availability cluster to a distributed high-availability cluster or vice versa. 
 
-2.  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. 
-
-3.  Select **Next: Cluster Settings**
+2.  Select **Next: Cluster Settings**
 
 ## Cluster Settings tab
 
 1.  In the **Cluster Name** field, enter the name for your cluster.
 
-2.  In the **Password** field, enter a password for your cluster. This is the password for the user edb_admin.
+2.  In the **Password** field, enter a password for your cluster. This is the password for the user `edb_admin`.
 
 3.  Under **Tags**, select **+**.
 
@@ -159,8 +146,6 @@ The following options aren't available when creating your cluster:
 
     Private networking allows only IP addresses in your private network to connect to your cluster.  
 
-    If you're using private networking and you're using EDB Hosted Cloud Service, you must enter your cloud service provider's account information. Cloud Service uses it to auto-approve your private endpoints and also to provide access for logging and telemetry. To enable you to create your private endpoint, Cloud Service provides you with the corresponding service name, which you can use to connect to your cluster privately. 
-
     See [Cluster networking architecture](/edb-postgres-ai/cloud-service/getting_started/your_cloud_account/cluster_networking/) for more information. 
 
 7.  To take the snapshot backups, enable **Volume Snapshots**. The snapshot backups are stored on the disk in the same region without degrading the performance. Enabling **Volume Snapshots** might increase the storage costs on your cloud service provider. By default, the snapshot backups are stored on the disk for 30 days.
@@ -171,6 +156,8 @@ The following options aren't available when creating your cluster:
     **Retention Period** controls. You can configure
     the retention period to a number of days, weeks, or months. The retention
     period must be between 1-180 days, 1-25 weeks, or 1-6 months.
+    
+    You can schedule a backup start time in UTC. You can choose hours and minutes in 24-hour format or choose now to start the backup immediately.
 
     Cloud Service deletes backups older than the retention period.