diff --git a/exadata-database-service-xs-get-started/.vscode/settings.json b/exadata-database-service-xs-get-started/.vscode/settings.json
new file mode 100644
index 0000000..6f3a291
--- /dev/null
+++ b/exadata-database-service-xs-get-started/.vscode/settings.json
@@ -0,0 +1,3 @@
+{
+ "liveServer.settings.port": 5501
+}
\ No newline at end of file
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md
new file mode 100644
index 0000000..c3093f2
--- /dev/null
+++ b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md
@@ -0,0 +1,242 @@
+
+
+
+# Configure & Validate Notifications for Monitoring ECPU Scaling changes
+
+
+## Introduction
+
+This lab walks you through the steps to configure & validate notifications for monitoring ECPU Scaling changes.
+
+Estimated Lab Time: 15 minutes
+
+**How Notifications Work?**
+
+The OCI Notifications service communicates when something happens with your resources in Oracle Cloud Infrastructure.
+
+The Notifications service lets you to set up communication channels for publishing messages using topics and subscriptions. When a message is published to a topic, the Notifications service sends the message to all of the topic's subscriptions.
+
+
+
+**Notifications Concepts**
+
+The following concepts are essential to working with OCI Notifications Service:
+
+***Notification*** - A configuration for sending messages, such as an alarm or event rule. Each message is sent to subscriptions in the specified topic.
+
+***Subscription*** - An endpoint for a topic. Published messages are sent to each subscription for a topic.
+
+ You can get human-readable messages through supported subscription protocols:
+
+ * **Email**
+ * **Function**
+ * **HTTPS (Custom URL)**
+ * **PagerDuty**
+ * **Slack**
+ * **SMS**
+
+***Topic*** - A communication channel for sending messages to subscriptions. Each topic name is unique across the tenancy.
+
+***Event Rules*** - When triggered, an event rule sends an event message to the configured topic. Notifications then deliver the message to active subscriptions.
+
+***Database Service Events*** - Database Service Events enables you to be notified about health issues with your Oracle Databases or other components on the Database Cloud Service.
+
+**Create Events Rule to Create Notification Automation for Database Service Events**
+
+The Database Service Events feature implementation generates events for Data Plane operations and conditions and Notifications by leveraging the existing OCI Events service and Notification service. Users can subscribe to the Database Service Events and receive notifications. To receive notifications, subscribe to the Database Service Events and get notified using the Oracle Notification service.
+
+### Objectives
+
+- After completing this lab, you should be able to configure notifications and events rules for monitoring ECPU Scaling changes for Exadata Database Service on Exascale Infrastructure
+
+### Prerequisites
+
+This lab requires completion of the following:
+
+* Completion of **Lab1**
+* Required IAM Policies for [**Managing Topics and Notifications**](https://docs.oracle.com/en-us/iaas/Content/Security/Reference/notifications_security.htm#iam-policies) and [**Managing Events**](https://docs.oracle.com/en-us/iaas/Content/Identity/policyreference/cloudeventspolicyreference.htm)
+
+## Task 1: Configure Notification Topic and Subscription for Enabled ECPU change
+
+1. Open the navigation menu and click **Developer Services**. Under **Application Integration**, click **Notifications**.
+
+ 
+
+2. The **Topics** page is selected by default, select your Compartment and Click **Create Topic**.
+
+ 
+
+3. Provide the Topic name. For this lab, use ***MyExaDBXSTopic*** for the Topic name.
+
+ 
+
+4. Click **Create**.
+
+ 
+
+ Once the Topic has been created, you will see the created Topic with the state of ***Active***.
+
+ 
+
+5. Click the name of the Topic you created to open the **Topic Details** page.
+
+ 
+
+6. On the Topic Details page, click **Create Subscription**.
+
+ 
+
+7. In the Create Subscription panel, for **Protocol**, select ***Email***. Provide your ***Email Address***, then Click **Create**
+
+ 
+
+ >**Note:** Notifications creates the email subscription and sends a confirmation URL to your assigned email address.
+
+ The subscription is ***pending*** until confirmation is received.
+
+ 
+
+8. Open your assigned Email, Check for the ***OCI Notifications Service Subscription Confirmation*** email, and Click the ***Confirm subscription*** link.
+
+ 
+
+ By clicking the confirmation link, it will launch a browser displaying that the subscription has been confirmed and that you have subscribed your assigned Email to the Topic you selected.
+
+ 
+
+ You can now see that the subscription is ***Active***.
+
+ 
+
+
+## Task 2: Create Events Rule to Create Notification Automation for Enabled ECPU Change
+
+1. Open the navigation menu and click **Observability & Management**. Under **Events Service**, click **Rules**.
+
+ 
+
+2. Select your ***Compartment*** and Click **Create Rule**
+
+ 
+
+3. In the Create Rule panel, provide the Rule name. For this lab, use ***MyExaDBXSEventsRule***.
+
+ 
+
+4. Configure **Rule Conditions**:
+
+ * In the **Rule Conditions** section, For Condition, Select ***Event Type***.
+ * For **Service Name**, select ***Database***
+ * For **Event Type**, Select ***Exadb VM Cluster - Update Begin*** and ***Exadb VM Cluster - Update End***
+
+ 
+
+5. Configure **Actions**:
+
+ * In the **Actions** section, For **Action Type**, Select ***Notifications***.
+ * For **Notifications Compartment**, select your ***Compartment***
+ * For **Topic**, Select ***MyExaDBXSTopic***
+
+
+ 
+
+6. Click **Create Rule**
+
+ 
+
+## Task 3: Validate the Current VM Cluster Resource Allocation and Scale up the Enabled ECPUs using the Console
+
+1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**.
+
+2. Select your ***Compartment***, and Select your **VM Cluster**.
+
+ 
+
+ The VM Cluster Details page displays information about the selected VM cluster. Under the **Resource allocation**, pay attention to the number of ***Enabled ECPUs:***
+
+ 
+
+3. In the VM Cluster Details page, Click **Scale VM Cluster**.
+
+ 
+
+ 
+
+ Scale Up the number of ***ECPUs enabled per VM*** from ***8 ECPU*** to ***12 ECPU***
+
+ 
+
+
+4. Click **Save Changes**
+
+ >**Note:** ECPU scaling activities are done online with no downtime. Once the scale up operation is complete, the VM Cluster status changes from ***Updating*** to ***Available***.
+
+## Task 4: List VM Cluster Configuration using CLI
+
+>**Note:** To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***.
+
+1. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section.
+
+ 
+
+ Paste the VM Cluster OCID to a text editor.
+
+2. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu.
+
+ 
+
+ This displays the Cloud Shell in a "drawer" at the bottom of the console:
+
+ 
+
+3. Run the OCI CLI Command to get the VM Cluster Configuration.
+
+ >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 4 Step 1)*
+
+ ```
+
+
+ oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state"}'
+
+
+ ```
+
+ After running the command, you will see similar output below.
+
+ 
+
+ You can see the new ***Enabled ECPU*** for the VM Cluster and with the ***Lifecycle State*** of ***Available***.
+
+## Task 5: Confirm Notifications output in the notification email that was configured
+
+1. Open your assigned email. You should be receiving two notification emails.
+
+ Review the details of the following notification email events:
+
+ * Start of the ECPU scale up operation - ***(updateexadbvmcluster.begin)***
+
+ 
+
+ * End of the ECPU scale up operation ***(updateexadbvmcluster.end)***
+
+ 
+
+ The Notification email for the Update VM Cluster Events shows the before and After VM Cluster ECPU Allocation.
+
+ Pay attention to the following fields from the notification email message:
+ * ***CPU Core Count***
+ * ***Reserved CPU Core Count***
+ * ***Enabled ECPU Core Count***
+ * ***Reserved ECPU Core Count***
+
+***!!! Congratulations:*** You may now **proceed to the next lab**.
+
+## Learn More
+
+* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/exadata-cloud-infrastructure-events.html) to learn more about Oracle Exadata Database Service on Exascale Infrastructure Events.
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png
new file mode 100644
index 0000000..19bbf8f
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/begin-notification.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-rule.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-rule.png
new file mode 100644
index 0000000..ee2bb0a
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-rule.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png
new file mode 100644
index 0000000..46bcff4
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-subscription.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.png
new file mode 100644
index 0000000..5cea5bb
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-create-topic.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png
new file mode 100644
index 0000000..e73b3e7
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png
new file mode 100644
index 0000000..dea470a
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png
new file mode 100644
index 0000000..708c9cb
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-actions.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png
new file mode 100644
index 0000000..4166697
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png
new file mode 100644
index 0000000..4de451b
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png
new file mode 100644
index 0000000..a4e97a1
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-events-rule.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-events-rule.png
new file mode 100644
index 0000000..de83859
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-events-rule.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.png
new file mode 100644
index 0000000..89f6245
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-rule.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png
new file mode 100644
index 0000000..b16c295
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png
new file mode 100644
index 0000000..f6b702d
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-active.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-name.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-name.png
new file mode 100644
index 0000000..3b749cb
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic-name.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png
new file mode 100644
index 0000000..f6385dd
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/create-topic.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png
new file mode 100644
index 0000000..02a9a80
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/current-ecpu.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png
new file mode 100644
index 0000000..02a9a80
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png
new file mode 100644
index 0000000..0fec12f
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/end-notification.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png
new file mode 100644
index 0000000..0f32146
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-notifications.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-rules.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-rules.png
new file mode 100644
index 0000000..48120ee
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-rules.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png
new file mode 100644
index 0000000..5bdca95
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png
new file mode 100644
index 0000000..5b4be29
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png
new file mode 100644
index 0000000..4f245a3
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png
new file mode 100644
index 0000000..eb55e58
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/provide-topic-name.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png
new file mode 100644
index 0000000..2de56d3
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/resource-allocation.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png
new file mode 100644
index 0000000..f361b4a
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png
new file mode 100644
index 0000000..0cf3716
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png
new file mode 100644
index 0000000..360a51e
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-active.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-active.png
new file mode 100644
index 0000000..4b198b0
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-active.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png
new file mode 100644
index 0000000..b56b50f
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png differ
diff --git a/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png
new file mode 100644
index 0000000..2814d23
Binary files /dev/null and b/exadata-database-service-xs-get-started/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md
new file mode 100644
index 0000000..a3963ed
--- /dev/null
+++ b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md
@@ -0,0 +1,100 @@
+# Create Thin Clone of an Oracle Pluggable Database (PDB) leveraging Exadata Exascale Technology
+
+
+## Introduction
+
+This lab walks you through how to create a thin cloned Oracle Pluggable Database of a Pluggable Database that is created on Exadata Exascale Infrastructure.
+
+ * For Pluggable Databases created on the Exadata Database Service on Exascale Infrastructure (**ExaDB-XS**), you can clone an Oracle Pluggable Database as a standard **clone** or as a **thin clone** (***unique to ExaDB-XS***).
+ * A PDB **clone** is an independent and complete copy of the given database as it existed at the time of the cloning operation.
+ * A PDB **thin clone** is a special type of the Local Clone, that leverages the Exascale redirect-on-write technology, that allows the thin clone PDB to share unchanged storage blocks with the parent PDB. This results in the fast creation of the thin cloned PDB with reduced space consumption.
+
+ * ***The following types of clones are supported:***
+ * ***Local Clone***: A full copy of the PDB that is created within the same CDB.
+ * ***Thin Clone***: A thin clone copy of the PDB that is created within the same CDB (***Option Only avaiable for Local Clones***).
+ * ***Remote Clone***: A full copy of the PDB that is created in a different CDB.
+ * ***Refreshable Clone***: A refreshable clone enables you to keep your remote clone updated with the source PDB. The only open mode you can have is read-only and refresh cannot be done while it is in read-only mode.
+
+
+**Estimated Time:** ***10 minutes***
+
+### **Objectives**
+
+- After completing this lab, you should be able to navigate to your VM Cluster, locate your desired Container Database, and create a thin cloned Oracle Pluggable Database on the Exadata Database Service on Exascale Infrastructure using the OCI Console.
+
+
+### **Prerequisites**
+
+This lab requires the completion of the following:
+
+* Successful creation of a VM Cluster on Exadata Database Service on Exascale Infrastructure.
+* Successful creation of Container Database on the VM Cluster, which will also includes the initial PDB.
+
+## Task 1: Create a Thin Clone PDB using OCI Console
+
+1. Open the **navigation menu** and click ***Oracle Database***. Under **Oracle Database**, click ***Oracle Database Service on Exascale Infrastructure***.
+
+ 
+ * **Note:** This will cause the **VM Clusters** page to be displayed.
+
+2. On the left rail, ensure that **VM Clusters** is selected (default selection). For the **List Scope**, select your compartment.
+
+ In the list of displayed VM clusters, click on the name of your VM Cluster.
+
+ 
+ * **Note:** This will cause the **VM Cluster Details** page to be displayed.
+
+3. Navigate from the VM Cluster to the Container Database (CDB). On the left rail under the **Resources** section, click on ***Container Databases***.
+
+ In the list of Container Databases diplayed, click on the ***name of the Container Database*** whose PDB we will create a thin clone of.
+
+ 
+ * **Note:** This will cause the **Container Database Details** page to be displayed.
+
+1. Navigate from CDB to Pluggable Database (PDB). On the left rail under the **Resources** section, click on ***Pluggable Databases***. From the list of available Pluggable Databases displayed, click on the ***name of the Pluggable Database*** we will create a thin clone of.
+
+ 
+ * **Note:** This will cause the **Pluggable Database Details** page to be displayed.
+
+5. Initiate the **Clone** Pluggable Database action.
+
+ On the **Pluggable Database Details** page, initiate the Clone PDB action by clicking on the ***Clone*** action button.
+
+ 
+ * **Note:** This will cause the **Clone Pluggable Database** configuration page to be displayed.
+
+6. Configure Clone PDB options and check the box to **Enable Thin Clone**
+
+ In the **Clone Pluggable Database** configuration page, select the PDB Clone type. Select ***Local Clone***.
+ * Provide the information to configure the new PDB.
+ * Enter the **PDB Name**
+ * Enter the **Database TDE wallet password**
+ * For this lab we will defer the initial PDB backup by ***unchecking the box*** to **Take a backup of the PDB immediately after cloning**
+ * Next, ensure to ***check the box*** to **Enable Thin Clone**
+ * Click on the ***Create Pluggable Database*** button to start the clone provisioning process.
+ 
+ * **Note:** that the thin PDB clone will be created and presented as a new PDB.
+ 
+
+1. List all of the PDBs in the Container Database (CDB). From the **Pluggable Database Details** page, select the ***Container Database Details*** link in the breadcrumb path at the top of the page.
+
+ * **Note:** that this will cause the **Container Database Details** page to be displayed.
+ 
+
+ On the left rail under the **Resources** section, click on ***Pluggable Databases***.
+ * **Note:** that this will cause a list of available Pluggable Databases to be displayed and that the Thin Clone PDB is listed, as just another PDB.
+
+
+***Congratulations!!!*** You may now **proceed to the next lab**.
+
+
+## Learn More
+
+* Click [here](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/exadata/doc/ecc-create-first-db.html) to learn more about Creating an Oracle Pluggable Database on Exadata Database Service on Exascale Infrastructure.
+
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Eddie Ambler, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/available-pdb-thin-clone-details-page.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/available-pdb-thin-clone-details-page.png
new file mode 100644
index 0000000..4801c0b
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/available-pdb-thin-clone-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/configure-pdb-thin-clone.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/configure-pdb-thin-clone.png
new file mode 100644
index 0000000..addb6ef
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/configure-pdb-thin-clone.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/console-to-exadb-xs.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/console-to-exadb-xs.png
new file mode 100644
index 0000000..f253228
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/console-to-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-pdb-thin-clone-from-cdb.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-pdb-thin-clone-from-cdb.png
new file mode 100644
index 0000000..075d429
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/list-pdb-thin-clone-from-cdb.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/mydemo-vm-cluster-details-page-to-cdb.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/mydemo-vm-cluster-details-page-to-cdb.png
new file mode 100644
index 0000000..d40ac81
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/mydemo-vm-cluster-details-page-to-cdb.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/navigate-cdb-to-pdb.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/navigate-cdb-to-pdb.png
new file mode 100644
index 0000000..a36ab85
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/navigate-cdb-to-pdb.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/pdb-details-clone-pdb.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/pdb-details-clone-pdb.png
new file mode 100644
index 0000000..3b5efd9
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/pdb-details-clone-pdb.png differ
diff --git a/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-compartment-and-mydemo-vm-cluster.png b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-compartment-and-mydemo-vm-cluster.png
new file mode 100644
index 0000000..59c2cc4
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-thin-clone-pdb-on-exascale/images/select-compartment-and-mydemo-vm-cluster.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/create-vmcluster-cdb-pdb-on-exascale.md b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/create-vmcluster-cdb-pdb-on-exascale.md
new file mode 100644
index 0000000..35fd729
--- /dev/null
+++ b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/create-vmcluster-cdb-pdb-on-exascale.md
@@ -0,0 +1,179 @@
+# Provision Oracle Exadata Database Service on Exascale Infrastructure using the OCI Console
+
+
+## Introduction
+
+This lab walks you through how to create an instance of the Exadata Database Service on Exascale Infrastructure using the OCI Console.
+
+
+Estimated Time: 2 Hours 10 minutes
+
+Watch the video below for a quick walk-through of the lab.
+ [Create a Custom Database Software Image](youtube:ggh0pIuPj2g)
+
+### Objectives
+
+- After completing this lab, you should be able to create an Exadata VM cluster and an Oracle Database on Oracle Exadata Database Service on Exascale Infrastructure using the OCI Console.
+
+
+### Prerequisites
+
+This lab requires completion of the following:
+
+* Successful Login to a Tenancy with a service limit assigned for the **Oracle Exadata Database Service on Exascale Infrastructure**
+
+## Task 1: Create an Exadata VM Cluster Resource on Oracle Exadata Database Service on Exascale Infrastructure
+
+1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**.
+
+ ![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ")
+
+2. In the left rail, **VM Clusters** is selected by default. Under **List Scope**, Select your compartment.
+
+ ![Select Compartment where VM Cluster will reside](./images/select-compartment.png" ")
+
+3. Click the **Create VM Cluster** button.
+
+ ![Click Create VM Cluster](./images/click-create-vm-cluster.png" ")
+
+ This causes the **Create VM Cluster** page to be displayed.
+
+4. **Provide the basic information to configure the Exadata VM cluster**.
+ * For **Compartment**: Ensure that the compartment that you want the VM Cluster to be created in is displayed.
+
+ * For **Display Name**: Enter ***MyDemoVMCluster***
+
+ * For **Cluster Name**: Enter ***MyDemoClus***
+
+ * For **Availability Domain**: Select the availability domain from the displayed options available.
+
+ ![Provide Basic VM Cluster Info](./images/provide-basic-vm-cluster-info-exascale.png" ")
+
+5. **To Configure the VM cluster, provide the following information:**
+ * For the **Number of VMs in the cluster**: ***Enter 2***
+ * For **ECPUs enabled per VM**: ***Enter 8***
+
+ * ***Reserve 4 additonal ECPUs*** by clicking on **Reserve additional ECPU to increase link** and entering the following:
+ * For **Total ECPUs per VM:** Provide a total number of ECPUs to allocate per VM. ***Enter 12***.
+ * The **ECPUs additional reserved per VM** field which is (read only) will now indicate that there are now **4 reserved ECPUs**.
+ * The **Memory per VM (GB)** field which is (read only) will display the amount of memory allocated to each VM.
+ ***Memory is calculated based on 2.75 GB per total ECPU***.
+
+ **Size the VM file system storage**:
+ * For system storage capacity per VM (GG): ***Enter 280***
+
+ **Note:** The VM Filesystems storage includes /u02 capacity, where your Database Homes will go, along with all of the other VM filesystems (/, /boot, /tmp, /var, /var/log, /var/log/audit, /home, swap, kdump, /u01, grid, /u02). Any extra capacity selected beyond system minimums will go into /u02.
+
+ ![Configure VM Cluster](./images/configure-vm-cluster-exascale.png" ")
+
+6. **Enter Configuration Details for Exascale Database Storage Vault:**
+ * Select **Create new vault**.
+
+ **For a new vault, specify the following:**
+ * For the **Exascale Vault name:** enter ***MyDemoStorageVault*** .
+ * For the **Storage Capacity for Databases (GB):** ***enter 300***.
+
+ ![Configure Exascale Storage Vault](./images/configure-exascale-storage-vault.png" ")
+
+1. **Select the Oracle Grid Infrastructure version and add SSH key:**
+ * **Grid Infrastructure Release and Version fields:** display the Oracle Grid Infrastructure versions available for deployment in the VM cluster.
+ ***Accept the default values for the 23ai release***.
+
+ * **Add your SSH Key for future access to your VMs**. Choose from:
+
+ * **Generate SSH key pair**(Default option) Select this option to generate an SSH keypair. Then in the dialog below click Save private key to download the key, and optionally click Save public key to download the key.
+ * **Upload SSH key files**: Select this option to browse or drag and drop .pub files.
+ * **Paste SSH keys:** Select this option to paste in individual public keys.
+
+ ![Configure Grid Infrastructure and SSH access](./images/configure-grid-infra-and-SSH-access.png" ")
+
+
+8. **To Configure the network settings, Select VCN and select Client and Backup subnet**
+ * **For the Virtual Cloud Network (VCN):** Select the ***virtual cloud network (VCN)*** for the compartment in which you want to create the VM cluster. Click ***Change Compartment*** to select a VCN in a different compartment.
+
+ * **For the Client subnet:** Select the ***client subnet*** in the compartment. This is the subnet to which the VM cluster should attach. Click ***Change Compartment*** to select a subnet in a different compartment.
+
+ * **For the Backup Subnet:** Select the subnet to use for the ***backup network***, which is typically used to transport backup information to and from the Backup Destination, and for Data Guard replication. Click ***Change Compartment*** to select a subnet in a different compartment, if applicable.
+
+ * **For the Hostname Prefix:** Enter the hostname
+
+ ![Configure Network Settings](./images/configure-network-settings.png" ")
+
+9. **Select license type & choose opt-in choices for Diagnostic & Collections options.**
+ * **Choose a license type:** The type of license that you want to use for the VM cluster. Your choice affects metering for billing. Select the ***Bring Your Own License (BYOL)*** OR ***License Included*** option.
+
+ ![Choose VM Cluster License Type](./images/choose-license-type.png" ")
+
+10. **Select Diagnostic and Collections Options**
+In the Edit Diagnostics Collection Settings dialog, you can enable or disable any of the Diagnostics Collections options. By enabling diagnostics collection and notifications, Oracle Cloud Operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. ***Accept the default values***.
+ * **Enable Diagnostics Events:** Allows Oracle to collect and publish critical, warning, error, and information events to me. For more information, see Overview of Database Service Events
+ * **Enable Health Monitoring:** Allows Oracle to collect health metrics/events such as Oracle Database up/down, disk space usage, and so on, and share them with Oracle Cloud operations. You will also receive notification of some events.
+ * **Enable Incident logs and trace collection:** Allows Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution.
+
+ ![Choose Diagnostic & Collections options](./images/choose-diagnostic-and-collections-options.png" ")
+
+11. Click **Create VM Cluster** to proceed with provisioning.
+
+
+## Task 2: Create an Oracle Database on Exadata Database Service on Exascale Infrastructure using OCI Console
+
+1. **Navigate to the Exadata Database Service on Exascale Infrastructure:**
+ * Open the navigation menu.
+ * Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**.
+
+ ![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ")
+
+2. **Navigate to the cloud VM cluster you want to create the database in:**
+ * In the left rail, ensure ***VM Clusters*** is selected.
+ * Under **List Scope**, Select your assigned compartment named ***MyCompartmentXX***.
+ * Then **click on your VM Clusters** ***assigned name*** to view the **VM Cluster Details page**.
+
+ ![Select Compartment and VM Cluster where Container Database will reside](./images/select-compartment-and-vm-cluster.png" ")
+
+3. On the **VM Cluster Details page** Click on **Create Container Database**.
+
+ 
+
+4. In the **Create Container Database** page enter the **basic information for creating the container database:**
+ * For the **Database Name:** Enter ***DemoDB***
+ * For the **Database Unique Name Suffix:** Enter ***DemoDB_23aiExascale***
+ * For the **Database Version:** Select ***23ai***
+ * For the **Pluggable Database Name:** Enter ***MyPDB***
+
+ 
+
+5. Specify the **Database Home Source and Administrator Credentials:**
+ * For the **Database Home source** choose: **Select an Existing Database Home**
+ * Select Database Home with display name of ***MyDemo23aiDBhome01***
+ * Next configure your **Administrator Credentials:**
+
+ 
+
+1. For this lab, we will not be enabling **Automatic Backups** for the database during the create database workflow.
+ * **Uncheck the box for:** ***Enable Automatic Backups***
+
+2. **Review & Configure Advanced Options** for the Container Database by clicking on the **Show Advanced Options** link.
+ * Under the **Management tab** set the Oracle_SID to ***ExascaleDemo***
+ 
+ * Under the **Encryption tab** you can select the desired key management method. Select ***Use Oracle-managed keys***.
+ 
+
+ * Under the **Tags tab:** you can add free-form tags to your resource. If you want to apply a defined tag, you must have permissions to use the tag namespace. Remember that you can also apply tags to your resources after they are provisioned.
+ 
+
+1. Click on the **Create Container Database** button to proceed with creating the Container Database.
+
+ 
+
+***!!! Congratulations:*** You may now **proceed to the next lab**.
+
+
+## Learn More
+
+* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/manage-vm-clusters.html) to learn more about managing the VM clusters on the Exadata Database Service on Exascale Infrastructure.
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page-with-pdb.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page-with-pdb.png
new file mode 100644
index 0000000..9373656
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page-with-pdb.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page.png
new file mode 100644
index 0000000..9a44dae
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/cdb-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png
new file mode 100644
index 0000000..d8b3b6d
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-diagnostic-and-collections-options.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png
new file mode 100644
index 0000000..daebcfd
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/choose-license-type.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/click-create-vm-cluster.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/click-create-vm-cluster.png
new file mode 100644
index 0000000..e5f88b9
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/click-create-vm-cluster.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png
new file mode 100644
index 0000000..ad6d7ba
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-encrypt-tab.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png
new file mode 100644
index 0000000..e550635
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-mgmt-tab.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png
new file mode 100644
index 0000000..2d2b9fd
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-adv-options-tags-tab.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png
new file mode 100644
index 0000000..6983b44
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-automatic-backups-to-rcv.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png
new file mode 100644
index 0000000..e00d8a7
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-exascale-storage-vault.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png
new file mode 100644
index 0000000..252a499
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-grid-infra-and-SSH-access.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png
new file mode 100644
index 0000000..9398d2c
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-network-settings.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png
new file mode 100644
index 0000000..15dadb5
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/configure-vm-cluster-exascale.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png
new file mode 100644
index 0000000..f253228
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/console-to-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png
new file mode 100644
index 0000000..2d597e9
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/create-cdb-basic-info.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png
new file mode 100644
index 0000000..bf82e12
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/define-dbhome-and-admin-pwd.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png
new file mode 100644
index 0000000..84472c5
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/provide-basic-vm-cluster-info-exascale.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png
new file mode 100644
index 0000000..959b09e
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment-and-vm-cluster.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png
new file mode 100644
index 0000000..31bf079
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/select-compartment.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png
new file mode 100644
index 0000000..3343d28
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vm-cluster-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png
new file mode 100644
index 0000000..d9cb9c1
Binary files /dev/null and b/exadata-database-service-xs-get-started/create-vmcluster-cdb-pdb-on-exascale/images/vmc-details-pg-create-cdb-on-exascale.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md
new file mode 100644
index 0000000..84f79ea
--- /dev/null
+++ b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md
@@ -0,0 +1,286 @@
+# Discover Environment Details using OCI API
+
+
+## Introduction
+
+This lab walks you through the steps to discover how to navigate to the Exadata Database Service on Exascale Infrastructure and discover the environment details for the Exadata VM Cluster, Container Database, Pluggable Database, and the Exascale Storage Vault using the OCI API.
+
+Estimated Time: 10 minutes
+
+### Objectives
+
+- After completing this lab, you should be able to discover Exadata Database Service on Exascale Infrastructure environment details using the OCI API.
+
+
+### Prerequisites
+
+This lab requires the completion of the following:
+
+* Completion of **Lab 1**
+* Required IAM Policies to [**Access OCI Cloud Shell**](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cloudshellintro.htm#Required_IAM_Policy).
+
+## Task 1: Get the VM Cluster Details using OCI CLI
+
+>**Note:** To use **OCI CLI** for this lab, we will be using the ***OCI Cloud Shell tool***.
+
+
+1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**.
+
+2. Select your ***Compartment***, and Select your **VM Cluster**.
+
+ 
+
+3. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu.
+
+ 
+
+ This displays the Cloud Shell in a "drawer" at the bottom of the console:
+
+ 
+
+ >**Note:** For this lab, we will be using the ***OCI Code Editor*** to store the required details in this lab.
+
+ Click on the ***Expand*** icon in **Actions** and select ***Open Code Editor***.
+
+ 
+
+ This displays the Code Editor in a side by side view with the Cloud Shell.
+
+ 
+
+ You can use the code editor to copy and paste obtained environment details in the lab. For better code viewing, under ***View*** select ***View: Toggle Word Wrap***.
+
+
+4. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section.
+
+ 
+
+
+ Paste the VM Cluster OCID value in your code or text editor.
+
+
+
+5. Run the OCI CLI Command to get the VM Cluster Configuration.
+
+ >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 4)*
+
+ ```
+
+
+ oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state",CompartmentOCID:"compartment-id"}'
+
+
+ ```
+ **Description:**
+
+ The OCI CLI command syntax is: **oci** ***db*** ***exadb-vm-cluster*** ***get*** ***--exadb-vm-cluster-id*** ***{VMClusterID}*** ***--query***
+
+ **Where:**
+
+ * ***db*** is the **service type** for the Oracle Database Cloud Services.
+ * ***exadb-vm-cluster*** is the **resource type** for the Exadata VM Cluster on Exascale Infrastructure.
+ * ***get*** is the **action** to get information about the Exadata VM Cluster on Exascale Infrastructure.
+ * ***--exadb-vm-cluster-id*** is the **parameter** for the ***VM Cluster OCID***.
+ * ***--query*** is the query parameter used for structured query options to display the specific VM Cluster data fields and values for the ***Display Name***, ***Enabled ECPUs***, ***Lifecycle state***, and ***Compartment OCID***
+
+ After running the command, you will see similar output below.
+
+ 
+
+ Pay attention to the following VM Cluster details from the command output:
+ * ***CompartmentOCID***
+ * **Display Name**
+ * **Enabled ECPUs**
+ * **Lifecycle State**
+
+ Copy the ***CompartmentOCID*** value and paste it value and paste it in your code or text editor.
+
+## Task 2: List the available Database Homes in a compartment using REST API
+
+1. From the Cloud Shell terminal, make an OCI REST API call to get a list of the available Database Homes in a compartment by running the **OCI RAW-REQUEST** command below:
+
+ > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***"{CompartmentOCID}"*** with the **Compartment OCID** obtained from ***Task 1 Step 5***
+
+ ```
+
+
+ oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10"
+
+
+ ```
+
+ **Description:**
+
+ The REST API Request is: ***GET /20160918/dbHomes?compartmentId={CompartmentOCID}&lifecycleState=AVAILABLE&limit=10***
+
+ **Where:**
+
+ * ***dbHomes*** is the **resource type** for the Oracle Database Home.
+ * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to list the available Database Homes.
+ * ***lifecycleState=AVAILABLE*** is the **query** to include a filter to return only Database Homes with the lifecycle state of Available.
+ * ***limit*** is the **query** to define the maximum number of items to return per page
+
+
+
+2. You will see a similar output as below.
+
+ 
+
+ Copy the **DB Home OCID** value from the ***"id"*** field and paste it in your notepad or text editor.
+
+ Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the database homes in the specified compartment.
+
+
+## Task 3: List the available Container Databases in a specified compartment using OCI CLI
+
+1. Run the OCI CLI Command to list the available Container Databases in a specified compartment.
+
+ >**Note:** Replace ***{CompartmentOCID}*** with the Compartment OCID obtained from ***Task 1 Step 5***
+
+ ```
+
+
+ oci db database list --compartment-id {CompartmentOCID} --query "data[*].{ContainerDatabase:\"db-name\",ContainerDatabaseOCID:id,State:\"lifecycle-state\"}" --output table
+
+
+ ```
+
+ **Description:**
+
+ The OCI CLI command syntax is: **oci** ***db*** ***database*** ***list*** ***--compartment-id*** ***{CompartmentOCID}*** ***--query***
+
+ **Where:**
+
+ * ***db*** is the **service type** for the Oracle Database Cloud Services.
+ * ***database*** is the **resource type** for the Container Database (CDB).
+ * ***list*** is the **action** to lists all Container Databases (CDBs) in a specified Compartment.
+ * ***--compartment-id*** is the **parameter** for the ***Compartment OCID***.
+ * ***--query*** is the query parameter used for structured query options to display the specific Container Database data fields and values for the ***Container Database Name***, ***Container Database OCID***, and ***Lifecycle state***
+
+ After running the command, you will see similar output below.
+
+ 
+
+ Copy the ***ContainerDatabaseOCID*** value and paste it in your code or text editor.
+
+## Task 4: List the available Pluggable Databases (PDBs) in a Container Database (CDB) using REST API
+
+1. Run the OCI CLI Command to list the available Pluggable Databases in a Container Database.
+
+ >**Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***{ContainerDatabaseOCID}*** with the ***Container Database (CDB) OCID*** obtained from ***Task 3***
+
+ ```
+
+
+ oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10"
+
+
+ ```
+
+ **Description:**
+
+ The REST API Request is: ***GET /20160918/pluggableDatabases?databaseId={ContainerDatabaseOCID}&limit=10***
+
+ **Where:**
+
+ * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB).
+ * ***databaseId*** is the **Container Database OCID**.
+ * ***limit*** is the **query** to define the maximum number of items to return per page
+
+ After running the command, you will see similar output below.
+
+ 
+
+ Look for the field ***pdbName*** and copy the **PDB OCID** value from the ***"id"*** field and paste it in your notepad or text editor.
+
+ Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of all the Pluggable Databases in the Container Database.
+
+## Task 5: Create Thin Clone of Pluggable Database (PDB) using REST API
+
+1. Prepare the JSON file for the Create Pluggable Database REST API call request body that contain the Create Thin Clone Pluggable Database Details resource.
+
+ Open the ***Code Editor*** tab.
+
+ Create a JSON file ***MyThinClonePDB.json*** with the required ***Create Pluggable Database*** details below
+
+ * **pdbName:** ***"ThinPDB2"***
+ * **pdbAdminPassword:** ***Enter your PDB admin password***
+ * **tdeWalletPassword:** ***Enter your TDE wallet password***
+ * **containerDatabaseId:** ***"{ContainerDatabaseOCID}"*** - Replace ***{ContainerDatabaseOCID}*** with **CDB OCID** obtained from ***Task 3***
+ * **pdbCreationTypeDetails:**
+ * **creationType:** ***"LOCAL\_CLONE\_PDB"***
+ * **sourcePluggableDatabaseId:** ***{PluggableDatabaseOCID}*** - Replace ***{PluggableDatabaseOCID}*** with **PDB OCID** obtained from ***Task 4***
+ * **isThinClone:** ***"true"***
+
+ 
+
+2. Make an OCI REST API call to create thin clone of pluggable database and starts a pluggable database (PDB) in the specified container database (CDB) by running the **OCI RAW-REQUEST** command below:
+
+ Open the **OCI Cloud Shell** tab and run the following command
+
+ >**Note:** Replace the API endpoint region "***{region}***" with your **assigned region**
+
+ 
+
+ ```
+
+
+ oci raw-request --http-method POST --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/pluggableDatabases" --request-body file://MyThinClonePDB.json
+
+
+
+ ```
+
+ **Description:**
+
+ The REST API Request is: ***POST /20160918/pluggableDatabases***
+
+ **Where:**
+
+ * ***pluggableDatabases*** is the **resource type** for the Pluggable Database (PDB).
+ * ***--request-body*** contains the **Create Pluggable Database Details** resource stored in the JSON file ***MyThinClonePDB.json***.
+
+ After running the command, you will see similar output below.
+
+ 
+
+ You will see that the Pluggable Database status ***"lifecycle-state"*** is ***PROVISIONING***.
+
+ Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to start the provisioning of the thin clone of a pluggable database.
+
+## Task 6: List Exascale Storage Vault using REST API
+
+1. Make an OCI REST API call to get a list of the Exascale Storage Vaults in the specified compartment by running the **OCI RAW-REQUEST** command below:
+
+ > **Note:** Replace the API endpoint region "***{region}***" with your **assigned region** and ***{CompartmentOCID}*** with the ***Compartment OCID*** obtained from ***Task 1***
+
+ ```
+
+
+ oci raw-request --http-method GET --target-uri "https://database.us-{region}-1.oraclecloud.com/20160918/exascaleDbStorageVaults?compartmentId={CompartmentOCID}&limit=10"
+
+
+
+ ```
+
+ **Description:**
+
+ The REST API Request is: ***GET /20160918/exascaleDbStorageVaults***
+
+ **Where:**
+
+ * ***exascaleDbStorageVaults*** is the **resource type** for the Exascale Storage Vault.
+ * ***compartmentId*** is the ***Compartment OCID*** of the Compartment where you want to get a list of the available Exascale Storage Vaults.
+
+ After running the command, you will see similar output below.
+
+ 
+
+ Having a Response ***"status": "200 OK"*** means the request was successfully received and was able to get a list of the available Exascale Storage Vaults in a specified comparment.
+
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png
new file mode 100644
index 0000000..fbc180d
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/clonepdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png
new file mode 100644
index 0000000..f78c5d4
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshell.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png
new file mode 100644
index 0000000..06ac712
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/cloudshelllaunch.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.png
new file mode 100644
index 0000000..f9f4ff7
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/code-editor-launch.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png
new file mode 100644
index 0000000..a4e97a1
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/copy-vmcluster-ocid.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png
new file mode 100644
index 0000000..cdf1766
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-cloud-shell.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png
new file mode 100644
index 0000000..f2d59b2
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/create-thin-clone-pdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/expand-code-editor.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/expand-code-editor.png
new file mode 100644
index 0000000..e7eb43a
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/expand-code-editor.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png
new file mode 100644
index 0000000..7ec2baa
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/get-vmcluster-updates.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png
new file mode 100644
index 0000000..a069635
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/getpdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png
new file mode 100644
index 0000000..2607a0f
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-all-cdb-in-compartment.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png
new file mode 100644
index 0000000..cce8914
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-cdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png
new file mode 100644
index 0000000..77755d7
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhome.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhomes.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhomes.png
new file mode 100644
index 0000000..bbf159f
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-dbhomes.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png
new file mode 100644
index 0000000..13232b0
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-exascale-storage-vault-in-a-compartment.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png
new file mode 100644
index 0000000..a3964a4
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/list-pdbs.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png
new file mode 100644
index 0000000..60eeb0f
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-thin-clone-pdb-json.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-worksheet-sample.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-worksheet-sample.png
new file mode 100644
index 0000000..5a448df
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/my-worksheet-sample.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png
new file mode 100644
index 0000000..5bdca95
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/navigate-vmcluster.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png
new file mode 100644
index 0000000..7010848
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/oci-cloud-shell.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png
new file mode 100644
index 0000000..bcf3f50
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-code-editor.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png
new file mode 100644
index 0000000..714b5b1
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-my-thin-clone.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png
new file mode 100644
index 0000000..a716027
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/open-myworksheet-mc.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png
new file mode 100644
index 0000000..e8c9d1b
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale-api/images/show-vm-cluster-details-comp-ocid.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/discover-env-details-on-exascale.md b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/discover-env-details-on-exascale.md
new file mode 100644
index 0000000..4b0157d
--- /dev/null
+++ b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/discover-env-details-on-exascale.md
@@ -0,0 +1,168 @@
+# Discover Oracle Exadata Database Service on Exascale Infrastructure Environment Details using OCI Console
+
+
+## Introduction
+
+ This lab walks you through the steps to discover how to navigate to the Exadata Database Service on Exascale Infrastructure and discover the environment details for the Exadata VM Cluster, Container Database, Pluggable Database, and the Exascale Storage Vault using the OCI Console.
+
+Estimated Time: 5 minutes
+
+### Objectives
+
+- After completing this lab, you should be able to discover Exadata Database Service on Exascale Infrastructure environment details using the OCI Console.
+
+
+### Prerequisites
+
+This lab requires the completion of the following:
+
+* Completion of **Lab 1**
+
+## Task 1: Discover Exadata VM Cluster Details
+
+1. **Navigate to the Exadata Database Service on Exascale Infrastructure:**
+ * Open the **Navigation Menu**.
+ * Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**.
+
+ ![Navigate to Exadata Database Service on Exascale Infrastructure](./images/console-to-exadb-xs.png" ")
+
+2. **Navigate to the list of availbale cloud Exadata VM cluster in your assigned compartment:**
+ * In the left rail, **VM Clusters** is selected by default.
+ * Under **List Scope**, Select your assigned compartment.
+ * Then **click on your clusters highlighted name that has a State of Available** to view the **VM Cluster Details page**.
+
+ ![Select Compartment and VM Cluster where Container Database will reside](./images/select-compartment-and-vm-cluster.png" ")
+
+1. On the **VM Cluster Details** page ***Discover the available VM Cluster information:***
+ * In the **General Information** Section you can find the following key items:
+ * What Compartment the VM Cluster is in.
+ * The Availability Domain of the VM Cluster.
+ * The OCID of the VM Cluster.
+ * The License Type selected for the VM Cluster.
+ * In the **Maintenance** Section you can find:
+ * Information about scheduled Node Maintenance Reboots.
+ * The **Resource Allocation** Section contains the following Cluster Wide Metrics:
+ * The numer of Reserved ECPUs available to conduct online scale up operation.
+ * The number of Enabled ECPUs across the VM Cluster.
+ * The amount of Memory allocated to the VMs across the VM Cluster.
+ * The total VM File Ystem Storage allocated to the VMs across the VM Cluster
+ * In the **Exascale Database Storage** Section you will find the followign key items:
+ * The location of the Exascale Storage Vault servicing this VM Cluster.
+ * The amount of Exascale database storage that was allocated and how much is free.
+ * The **Network** Section contains the followign key pieces of networking information:
+ * The nameof the VCN being used for the subnets and routing rules.
+ * The name of the Client SUbnet and Backup Subnet selected for this VM Cluster.
+ * The SCAN IPs, SCAN DNS name, and SCAN listener port.
+ * In the **Version** Section of the page, you will find the followign key items:
+ * The Exadata Image Version.
+ * The Grid Infrastructure Version.
+ * A link to view any available Updates required to keep your system up to date.
+
+ ![Review Information on VM Cluster Details page](./images/vm-cluster-details-page.png" ")
+
+4. On the left side of the page, under the **Resources** section: ***Discover the additional VM Cluster resources:***
+ * You can click the **Container Database** link to see a list of available databases.
+ ![VM Cluster Details page Resources Section Container Databases](./images/vm-cluster-details-page-resource-section-cdb-list.png" ")
+ * You can click the **Database Homes** link to see a list of the existing database homes.
+ ![VM Cluster Details page Resources Section Database Homes](./images/vm-cluster-details-page-resource-section-dbhome-list.png" ")
+ * You can click the **Virtual Machines** link to see a list of the Virtual Machines that are allocated to your VM Cluster
+ ![VM Cluster Details page Resources Section Virtual Machines](./images/vm-cluster-details-page-resource-section-vm-list.png" ")
+
+
+
+## Task 2: Discover Container Database (CDB) & Pluggable Database (PDB) Details
+
+1. Navigate to the **Container Database Details** page.
+ * On the left side of the page, under the **Resources** section: Select **Container Database** link.
+ * From the List of existing Container Databases in your compartment, select the name of your **Container Database that has a State of** ***Available*** to view the **Container Database Details** page.
+
+ ![Navigate to Container Database Details page](./images/vm-cluster-details-page-to-cdb.png" ")
+
+2. On the **Container Database Details** page ***Discover the following Container Database Information***
+
+ * On the **Container Database (CDB) Details** page, you can see a list of actions that can be performed, such as obtaining the connection string, and Restoring, Configuring Automatic Backups, Creating a Database from a Backup, and more actions.
+ * In the ***General Information*** Section you can find the following key items:
+ * The Lifecycle state of the Container Database.
+ * The OCID of the Container Database.
+ * The Database Unique Name and Oracle SID Prefix of the Container Database.
+ * In the ***Database Version*** Section of the page, you will find the followign key items:
+ * The name of the database software image if one was used to creade the Container Database.
+ * The name of the database home that has a link so that you can see what other databases share this home.
+ * The Database version for the Container Database.
+ * You will also find a link to view any available Updates required to keep your system up to date.
+ * In the ***Backup*** Section you can find:
+ * If your container database is configured for Automatic Backups.
+ * You can also see if your backups are healthy and know your exact Data Loss exposure.
+ * In this section, you can also see when your last backup was, when the next one is scheduled for, and how much storage you are using to backup this container database.
+ * The Backup section also includes information about the Backup Destination being used, and identifes the protection poicy being used and if realtime protection feature of the Recovery service is in use.
+ * The ***Data Guard*** Section of the page is pretty straight forward:
+ * Identifes if the Container Database has a peer Data Guard enabled for it or not.
+ * The ***Associated Services*** Section of the page:
+ * Informs you if the (optional) **Operations Insights** feature has been enabled for the container database.
+ * The ***Encryption*** Section of the page:
+ * Provides you with information about the type of encryption key management that is being used.
+
+ 
+
+
+3. On the left side of the page, under the **Resources** section: ***Discover the additional Container Database resources:***
+ * You can click the **Backups** link to see a list of available database backups.
+ ![VM Cluster Details page Resources Section Backups](./images/container-database-details-page-resource-section-backup-list.png" ")
+ * You can click the **Data Guard Association** link to see if this database has a Data Guard Peer.
+ ![VM Cluster Details page Resources Section Data Guard Association ](./images/container-database-details-page-resource-section-dg-list.png" ")
+ * You can click the **Pluggable Database** link to see a list of the Pluggable Databases that have been created in this Container Database.
+ ![VM Cluster Details page Resources Section Pluggable Databases ](./images/container-database-details-page-resource-section-pdb-list.png" ")
+
+
+4. Now lets ***Discover Details about our Pluggable Databases***
+ * From the **Resources** Section of the **Container Database Details** page, Click on the **Pluggable Database** Link
+ * Select the ***name of your Pluggable Database*** link to navigate the **Pluggable Database Details** page.
+
+ 
+
+5. On the **Pluggable Database Details** page ***Discover the following Pluggable Database Information***
+ * On the ***Pluggable Database (PDB) Details*** page, you can see a list of actions that can be performed, such as obtaining the connection string, and Cloning, Starting, Stopping, Relocating, and Restoring the PDB.
+ * In the ***General Information*** Section you can find the following key items:
+ * The Lifecycle state of the Pluggable Database.
+ * The OCID of the Pluggable Database.
+ * The linked Name of the Container Database where this PDB resides.
+ * In this section, you wil also see information indicating if the PDB is a Refreshable Clone and its Open Mode role.
+ * The ***Associated Services*** Section of the page:
+ *Informs you if the (optional) Operstions Insights feature has been enabled for the pluggable database.
+
+ 
+
+## Task 3: Discover Exascale Storage Vault Details
+
+1. Navigate from the **Pluggable Database Details** page to the **VM Cluster Details** page.
+
+ * On the **Pluggable Database Details** page, you will see the navigation bread crumb links. ***Click on the VM Cluster Details*** link.
+
+ 
+
+2. On the **VM Clusters** page, click on the ***Exascale Storage Vault name*** for your VM Cluster.
+ This will launch the **Exascale Storage Vault Details** page.
+ 
+
+
+3. On the **Exascale Storage Vault Details** page ***Discover the following Exascale Storage Vault Information***
+ * On the **Exascale Storage Vault Details** page, you can see a list of actions that can be performed, such as scaling the storage vault or moving the Vault to another compartment.
+ * In the **General Information** Section of the **VM Cluster Information** tab, you can find the following key items:
+ * The Lifecycle state of the Exascale Storage Vault.
+ * What Compartment the Exascale Storage Vault is in.
+ * The Availability Domain of the Exascale Storage Vault.
+ * The OCID of the Exascale Storage Vault.
+ * In the **Exascale Database Storage** Section you will find:
+ * The amount of Exascale database storage that was allocated and how much is free.
+ * On the left side of the page, under the **Resources** section:
+ * You can click on the **Associated VM Clusters** link to see a list of VM Clusters that are using this storage vault.
+
+ 
+
+***!!! Congratulations:*** You may now **proceed to the next lab**.
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Eddie Ambler, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png
new file mode 100644
index 0000000..476211c
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs .png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png
new file mode 100644
index 0000000..9476315
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/console-to-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png
new file mode 100644
index 0000000..c2609d6
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-backup-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png
new file mode 100644
index 0000000..11e3720
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-dg-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png
new file mode 100644
index 0000000..590cb48
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section-pdb-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png
new file mode 100644
index 0000000..30dd6d2
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page-resource-section.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png
new file mode 100644
index 0000000..039d988
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/container-database-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png
new file mode 100644
index 0000000..fe438a3
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/exascale-storage-vault-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png
new file mode 100644
index 0000000..7000336
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-cdb-to-pdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png
new file mode 100644
index 0000000..e71ceff
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/navigate-vmc-details-to-exascale-storage-vault.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png
new file mode 100644
index 0000000..6cc6552
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pdb-to-vmc-via-breadcrumb-link.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png
new file mode 100644
index 0000000..3eef07b
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/pluggable-database-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png
new file mode 100644
index 0000000..cac5e82
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/select-compartment-and-vm-cluster.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png
new file mode 100644
index 0000000..7a49744
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-cdb-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png
new file mode 100644
index 0000000..7f2bd98
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-dbhome-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png
new file mode 100644
index 0000000..c5096e6
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section-vm-list.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png
new file mode 100644
index 0000000..cd938ae
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-resource-section.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png
new file mode 100644
index 0000000..945c591
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page-to-cdb.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png
new file mode 100644
index 0000000..88a55c8
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vm-cluster-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.png b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.png
new file mode 100644
index 0000000..6f88e0e
Binary files /dev/null and b/exadata-database-service-xs-get-started/discover-env-details-on-exascale/images/vmc-page-via-breadcumb-link.png differ
diff --git a/exadata-database-service-xs-get-started/get-started-gs/get-started-gs.md b/exadata-database-service-xs-get-started/get-started-gs/get-started-gs.md
new file mode 100644
index 0000000..bd454b6
--- /dev/null
+++ b/exadata-database-service-xs-get-started/get-started-gs/get-started-gs.md
@@ -0,0 +1,71 @@
+# Get started - Connect to Oracle Cloud Tenancy
+
+
+## **Introduction**
+
+Oracle Cloud is the industry's broadest and most integrated cloud provider, with deployment options ranging from the public cloud to your data center. Oracle Cloud offers best-in-class services across Software as a Service (SaaS), Platform as a Service (PaaS), Database as a Service (DBaaS), and Infrastructure as a Service (IaaS).
+
+**Estimated Time:** ***5 minutes***
+
+**Types of Cloud Accounts that can be used for this workshop:**
+
+ * ***Oracle Cloud Paid Account***: When your tenancy is provisioned, Oracle sends an email to the default administrator at your company with the sign-in credentials and URL. This administrator can then create a user for each person who needs access to the Oracle Cloud. Check your email or contact your administrator for your credentials and account name.
+
+ * ***Oracle provided Cloud Workshop Account***: This type of environment can be obtained by engaging with your Sales Engineer to coordinate obtaining approval to obtain an Event Code which will provide temporary access to an Oracle provided environment.
+
+
+
+
+### **Objectives**
+
+- For this workshop we will learn how to login to a tenancy using the **Oracle Cloud Paid Account**.
+
+
+### **Prerequisites**
+
+* **Cloud Account Name** - Secure your Oracle Cloud tenancy name that will be used for this workshop.
+
+* **Username** - Secure your personal or assigned username for this workshop
+
+* **Password** - Secure your personal or assigned password for this workshop
+
+* **Required Service Limits** - If you are using a personal Oracle Cloud tenancy, you will need to ensure that you have service limits assigned for the following resources to run the workshop:
+
+ | Limits Name | Description | Value |
+ |-------------|-------------|----------|
+ | exadbxs-vm-instance-base-count|Exadata Database Service on Exascale Infrastructure - Instance Count| >= **2**|
+ | exadbxs-total-cpu-base-count | Exadata Database Service on Exascale Infrastructure - Total ECPU Count | >= **24** |
+ | exadbxs-local-storage-base-gb | Exadata Database Service on Exascale Infrastructure - Local Storage (GB) | >= **600** GB |
+ | exadbxs-hc-storage-base-gb | Exadata Database Service on Exascale Infrastructure - High Capacity Storage (GB) | >= **600** GB
+
+
+* **Required IAM Policy for Oracle Exadata Database Service on Exascale Infrastructure** - Configure the [**required Identity Access Management (IAM) Policy**](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/preparing-for-exadb-xs-deployment.html#GUID-EA03F7BC-7D8E-4177-AFF4-615F71C390CD) for provisioning Oracle Exadata Database Service on Exascale Infrastructure systems
+
+
+## Task 1: Log in to Oracle Cloud Tenancy
+
+1. Go to [**cloud.oracle.com**](https://cloud.oracle.com/?region=us-sanjose-1&tenant=livelabs4exadb) and enter your **Cloud Account Name** *(**Cloud Tenancy**)*.
+
+ 
+
+
+2. Enter your assigned **username** and **password** and click **Sign In**
+
+ 
+
+3. You are now signed in to Oracle Cloud!
+
+ 
+
+
+
+You may now **proceed to lab 1**.
+
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png b/exadata-database-service-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png
new file mode 100644
index 0000000..4d9a2b5
Binary files /dev/null and b/exadata-database-service-xs-get-started/get-started-gs/images/cloud-tenancy-sign-in.png differ
diff --git a/exadata-database-service-xs-get-started/get-started-gs/images/oci-login-landing-page.png b/exadata-database-service-xs-get-started/get-started-gs/images/oci-login-landing-page.png
new file mode 100644
index 0000000..4fa7340
Binary files /dev/null and b/exadata-database-service-xs-get-started/get-started-gs/images/oci-login-landing-page.png differ
diff --git a/exadata-database-service-xs-get-started/get-started-gs/images/select-cloud-tenancy.png b/exadata-database-service-xs-get-started/get-started-gs/images/select-cloud-tenancy.png
new file mode 100644
index 0000000..53bae60
Binary files /dev/null and b/exadata-database-service-xs-get-started/get-started-gs/images/select-cloud-tenancy.png differ
diff --git a/exadata-database-service-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png b/exadata-database-service-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png
new file mode 100644
index 0000000..fdff4f7
Binary files /dev/null and b/exadata-database-service-xs-get-started/introduction-gs/images/architecture-diagram-for-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png b/exadata-database-service-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png
new file mode 100644
index 0000000..9f2aa0c
Binary files /dev/null and b/exadata-database-service-xs-get-started/introduction-gs/images/enabled-and-reserved-ECPU-on-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/introduction-gs/images/introduction.png b/exadata-database-service-xs-get-started/introduction-gs/images/introduction.png
new file mode 100644
index 0000000..f8249c3
Binary files /dev/null and b/exadata-database-service-xs-get-started/introduction-gs/images/introduction.png differ
diff --git a/exadata-database-service-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png b/exadata-database-service-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png
new file mode 100644
index 0000000..d345a1e
Binary files /dev/null and b/exadata-database-service-xs-get-started/introduction-gs/images/thin-clone-pdb-on-exadb-xs.png differ
diff --git a/exadata-database-service-xs-get-started/introduction-gs/introduction-gs.md b/exadata-database-service-xs-get-started/introduction-gs/introduction-gs.md
new file mode 100644
index 0000000..9c16f8a
--- /dev/null
+++ b/exadata-database-service-xs-get-started/introduction-gs/introduction-gs.md
@@ -0,0 +1,50 @@
+# Introduction
+
+## About this Workshop
+
+This workshop is designed to provide you with hands on experience using the Exadata Database Service on Exascale Infrastructure, which is Oracle’s next generation architecture of the Exadata Database Service.
+
+In this workshop, you will use several of the OCI management interfaces to conduct various database lifecycle tasks on the Exadata Database Service on Exascale Infrastructure.
+
+The workshop exercises are designed to provide you with operational experience creating & managing the Exascale Storage Vault, the Exadata VM Cluster, Container Databases, Pluggable Databases, and thin clones that leverage the Exascale technology stack.
+
+You will also learn how to configure alerts and notifications for events that we will trigger during some of the workshop lab tasks.
+
+Don’t miss your chance to be one of the first to gain hand-on experience with Exadata & the Exascale technology stack.
+
+
+**Estimated Workshop Time:** ***90 minutes***
+
+
+### **Oracle Exadata Exascale: World’s Only Intelligent Data Architecture for Cloud**
+
+
+Exadata Exascale is Oracle’s revolutionary multitenant architecture that combines the intelligence of Exadata with all the benefits of modern clouds. This loosely-coupled architecture incorporates the Exascale intelligent storage cloud and a pool of Exascale database-optimized compute to provide hyper-elasticity while meeting even the most demanding workload requirements.
+
+
+
+When running Exadata Database Service on Exascale Infrastructure, you have access to its intelligent capabilities across your application portfolio. Database-optimized intelligent infrastructure runs AI, analytics, mission-critical OLTP, and developer workloads faster and more efficiently, reducing overall IT costs. Some of these capabilities include:
+
+* Intelligent AI: The combination of AI Smart Scan with Exadata System Software 24ai offloads key AI Vector Search operations to the Exascale intelligent storage cloud, enabling massive amounts of vector data to be searched up to 30X faster.
+
+* Intelligent analytics: The combination of intelligent columnarization and Smart Scan make hundreds or thousands of processing cores in the Exascale intelligent storage cloud available to process any SQL query.
+
+* Intelligent OLTP: Exascale’s intelligent architecture automatically tiers data between DRAM, flash, and disk enabling low-latency, high-throughput Remote Direct Memory Access (RDMA) to frequently accessed data and delivers the performance of DRAM, the IOPS of flash, and the capacity of disk.
+
+* Database-aware intelligent clones:The Exascale intelligent storage cloud uses redirect-on-write snapshot technology to instantly create space-efficient database clones from read-write sources.
+
+Starting today, you can enjoy Exadata Database Service benefits at a lower entry cost for smaller, but no less critical, databases. Exadata Database Service on Exascale Infrastructure bridges the gap between dedicated Exadata infrastructure and virtual machines on shared commodity infrastructure. It extends Exadata’s advantages to every organization in every industry, regardless of size or workload.
+
+You can start small using virtual machine (VM) cluster configurations with as little as 8 ECPUs and 22 GB of memory per VM, and 300 GB of intelligent database storage. You can easily scale up the number of ECPUs and number of VMs in the cluster, and then shrink them when you don’t need them. To ensure ECPU capacity is available when you need it, you can reserve ECPUs at a nominal cost.
+
+You may now **proceed to the next lab**
+
+## Learn More
+
+* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/index.html) to learn more about the Exadata Database Service on Exascale Infrastructure.
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, Mar 2025.
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png
new file mode 100644
index 0000000..e8e4cfc
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png
new file mode 100644
index 0000000..d5b5bf0
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png
new file mode 100644
index 0000000..dfefc84
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/copy-compartment-ocid.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png
new file mode 100644
index 0000000..c8b0928
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png
new file mode 100644
index 0000000..a53ee3e
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png
new file mode 100644
index 0000000..be0383b
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png
new file mode 100644
index 0000000..b30b28f
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png
new file mode 100644
index 0000000..7154802
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png
new file mode 100644
index 0000000..4e3b20a
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-ocpu.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png
new file mode 100644
index 0000000..7420932
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png
new file mode 100644
index 0000000..4214ac7
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png
new file mode 100644
index 0000000..772da36
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png
new file mode 100644
index 0000000..f305533
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/scale-vm-cluster-updating.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png
new file mode 100644
index 0000000..c4bc910
Binary files /dev/null and b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/images/vmcluster-details-page.png differ
diff --git a/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md
new file mode 100644
index 0000000..693a56b
--- /dev/null
+++ b/exadata-database-service-xs-get-started/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md
@@ -0,0 +1,118 @@
+
+
+
+# Scale Exascale Storage Vault Resources
+
+
+## Introduction
+
+This lab walks you through the steps to Scale the Exascale Storage Vault Resources using the OCI Console.
+
+Estimated Time: 10 minutes
+
+
+### Objectives
+
+- After completing this lab, you should be able to scale the Exascale Storage Vault Resources using the OCI Console.
+- List Exascale Storage Vault configuration using **OCI CLI**
+
+
+### Prerequisites
+
+This lab requires the completion of the following:
+
+* Completion of **Lab1**
+
+
+## Task 1: Scale the Exascale Storage Vault Resources using the OCI Console
+
+1. Open the navigation menu. Under **Oracle Database**, Click **Oracle Exadata Database Service on Exascale Infrastructure**.
+
+ 
+
+2. On the left rail, click **Exascale Storage Vaults**.
+
+ Select the name of your Exascale Storage Vault that you want to scale.
+
+ 
+
+3. The Exascale Storage Vault Details page displays information about the selected Vault.
+
+ Click on ***Scale storage vault***.
+
+ 
+
+ On the Scale Storage Vault dialog, enter a number for the capacity for High Capacity storage.
+ >**Note:** This number should be the value for the total storage that you want to have provisioned after the scaling operation completes.
+
+
+
+ For this lab, enter the value of ***400*** for the ***Storage capacity for Databases (GB)***, as we will scale up the Exascale Database Storage Vault from **300 GB to 400 GB**.
+
+ 
+
+4. Click ***Save Changes***. Your Vault will be scaled automatically.
+
+ >**Note:** Once the scale up operation is complete, the Exascale Storage Vault status will change from ***Updating*** to ***Available***.
+
+ 
+
+ In the Exascale Storage Vault Details page, Copy the Storage Vault OCID by clicking the ***copy*** button in the **OCID** field under the **General Information** section.
+ Paste the copied ***Exascale Storage Vault OCID*** to a text editor.
+
+ 
+
+## Task 2: List Exascale Storage Vault Configuration using CLI
+
+ >**Note:** To use **OCI CLI** for this lab, we will be using the ***OCI Cloud Shell tool***.
+
+1. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu.
+
+ 
+
+ This displays the Cloud Shell in a "drawer" at the bottom of the console:
+
+ 
+
+2. Run the OCI CLI Command to get the Exascale Storage Vault Configuration.
+
+ >**Note:** Replace ***{ExascaleVaultID}*** with the Exascale Storage Vault OCID copied from *(Task 1 Step 4)*
+
+ ```
+
+
+ oci db exascale-db-storage-vault get --exascale-db-storage-vault-id {ExascaleVaultID}
+
+
+ ```
+
+ **Description:**
+
+ The OCI CLI command syntax is: **oci** ***db*** ***exascale-db-storage-vault*** ***get*** ***--exascale-db-storage-vault-id*** ***{ExascaleVaultID}***
+
+ **Where:**
+
+ * ***db*** is the **service type** for the Oracle Database Cloud Services.
+ * ***exascale-db-storage-vault*** is the **resource type** for the Exascale Storage Vault.
+ * ***get*** is the **action** to get information about the Exascale Storage Vault Configuration.
+ * ***--exascale-db-storage-vault-id*** is the **parameter** for the Exascale Storage Vault OCID.
+
+ After running the command, you will see similar output below.
+
+ 
+
+ The output of the command displays information about the configuration of the selected ***Exascale Storage Vault***, such as:
+
+ * ***Storage Vault Display Name***
+ * ***Exascale Database Storage Capacity Available size in gbs***
+ * ***Exascale Database Storage Capacity Total size in gbs***
+ * ***Lifecycle state***
+ * ***Exascale Storage Vault Associated VM Cluster Count and OCID***
+
+***Congratulations!!!*** You may now **proceed to the next lab**.
+
+## Acknowledgements
+
+* **Author** - Leo Alvarado, Tammy Bednar, Product Management
+
+* **Last Updated By** - Leo Alvarado, Product Management, March 2025.
diff --git a/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/index.html b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/index.html
new file mode 100644
index 0000000..6acdb69
--- /dev/null
+++ b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/index.html
@@ -0,0 +1,62 @@
+
+
+
+
+
+
+
+
+ Oracle LiveLabs
+
+
+
+
+
+
+
+
+
+
+
+
+
Oracle LiveLabs
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json
new file mode 100644
index 0000000..72bbd59
--- /dev/null
+++ b/exadata-database-service-xs-get-started/workshops/get-started-with-exadb-xs/manifest.json
@@ -0,0 +1,54 @@
+{
+ "workshoptitle": "Get Started with Oracle Exadata Database Service on Exascale Infrastructure",
+
+ "help": "livelabs-help-db_us@oracle.com",
+
+ "tutorials": [
+ {
+ "title": "Introduction",
+ "description": "Introduction",
+ "filename": "../../introduction-gs/introduction-gs.md"
+ },
+ {
+ "title": "Get Started",
+ "description": "Login to Oracle Cloud",
+ "filename": "../../get-started-gs/get-started-gs.md"
+ },
+ {
+ "title": "Lab 1: Create Instance of Exadata Database Service on Exascale Infrastructure",
+ "description": "Learn how to Create Instance of Exadata Database Service on Exscale Infrastructure using OCI Console",
+ "filename": "../../create-vmcluster-cdb-pdb-on-exascale/create-vmcluster-cdb-pdb-on-exascale.md"
+ },
+ {
+ "title": "Lab 2: Discover VM Cluster, Container Database, & Pluggable Database Details",
+ "description": "Learn how to Discover Environment Details using OCI Console",
+ "filename": "../../discover-env-details-on-exascale/discover-env-details-on-exascale.md"
+ },
+ {
+ "title": "Lab 3: Create Thin Clone of PDB",
+ "description": "Learn how to Create PDB Thin Clone on Exadata Exascale using OCI Console",
+ "filename": "../../create-thin-clone-pdb-on-exascale/create-thin-clone-pdb-on-exascale.md"
+ },
+ {
+ "title": "Lab 4: Scale Exascale Storage Vault Resources",
+ "description": "Learn how to Scale Exascale Storage Vault Resources using OCI Console",
+ "filename": "../../scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md"
+ },
+ {
+ "title": "Lab 5: Configure & Validate Notifications for Monitoring ECPU Scaling Changes",
+ "description": "Learn how to Configure & Validate Notifications for Monitoring ECPU Scaling Changes",
+ "filename": "../../configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md"
+ },
+ {
+ "title": "Lab 6: Discover Exadata Database Service on Exascale Infrastructure Environment Details using APIs",
+ "description": "Learn how to Discover Environment Details using APIs",
+ "filename": "../../discover-env-details-on-exascale-api/discover-env-details-on-exascale-api.md"
+ },
+
+ {
+ "title": "Need Help?",
+ "description": "Solutions to Common Problems and Directions for Receiving Live Help",
+ "filename":"https://oracle-livelabs.github.io/common/labs/need-help/need-help-freetier.md"
+ }
+ ]
+}
\ No newline at end of file