> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-6-databases.md).

# Step 6: Add Databases

Add managed databases to your Resource Group: an RDS instance, an Aurora cluster or an ElastiCache cache.

Databases are provisioned inside a Resource Group, like the workloads in Step 5. In the Resource Group's sidebar, open **Cloud Resources** and then **Databases**. It holds three services:

* **RDS → Instances**: single RDS DB instances (MySQL, MariaDB, PostgreSQL, Oracle and SQL Server)
* **RDS → Clusters**: Aurora clusters (Aurora MySQL and Aurora PostgreSQL)
* **ElastiCache**: Redis, Valkey and Memcached caches

Each service has a create wizard. When you submit it, the agent provisions the database with CloudFormation. The database inherits the Resource Group's network, security groups and KMS key, so you don't configure those again.

***

## RDS Instance

### Step 1 — RDS Instances list

In the Resource Group sidebar, open **Cloud Resources → Databases → RDS → Instances**. Summary cards show how many instances you have, how many are publicly reachable, how many are encrypted and how many are backed up. The list shows each instance's engine, class, visibility, Multi-AZ setting and status. Click **Create RDS Instance** to start.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-778c4fe21506c4f7cc9b9598f6c6858375cfd7ac%2Fdatabases-rds-instances-list.png?alt=media)

### Step 2 — Basics

Fill in the **Basics** step:

* **Name**: used as the AWS `DBInstanceIdentifier` (for example `orders-db`)
* **Description**: optional
* **Restore from snapshot**: turn on to create the instance from an existing snapshot. The engine, version, credentials and storage size come from the snapshot.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-8e4c08e217ba83ee97f08a297ef1b264a969410d%2Fdatabases-rds-instance-basics.png?alt=media)

### Step 3 — Engine

* **Engine**: `mysql`, `mariadb`, `postgres`, or one of the Oracle and SQL Server editions
* **Engine Version**: the versions available in the Resource Group's region. The list is cached for 6 hours.
* **DB Instance Class**: the classes available for that engine and version (for example `db.t4g.small`)
* **Initial DB Name**: optional; defaults to the instance name

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-a409ef6f0517039332f6ffe322f25fbb2e3b5079%2Fdatabases-rds-instance-engine.png?alt=media)

### Step 4 — Storage

* **Allocated Storage (GiB)**: the starting size
* **Enable storage autoscaling**: lets AWS grow the volume as it fills, up to the **Maximum Allocated Storage** you set. The maximum must be larger than the allocated storage.
* **Storage Type**: optional; `gp3`, `gp2`, `io1`, `io2` or magnetic (`standard`)
* **IOPS**: shown for storage types that support provisioned IOPS. It's required for `io1` and `io2`, and optional for `gp3`.
* **Storage Encryption**: **Encrypt with Resource Group KMS key**, **Encrypt with AWS-managed default key** (`aws/rds`), or **No encryption**
* **Storage KMS Key**: optional, shown when you encrypt with the Resource Group key. Leave it blank to use the Resource Group's default key.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-437bb7a07e74c147153f3a828e7f94bab047fca7%2Fdatabases-rds-instance-storage.png?alt=media)

### Step 5 — Networking

* **Visibility**: **Private (recommended)** places the instance in the network's private subnets. **Public** makes it publicly accessible.
* **Multi-AZ deployment**: turn on to keep a standby copy in a second Availability Zone
* **Availability Zone**: optional; leave it blank to let AWS choose. AWS picks the zones itself for Multi-AZ deployments.
* **DB Subnet Group Name**: optional; leave it blank to use the network's managed subnet group, or pick or type the name of another group in the same VPC

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-ffc0c663a295f204e2c2381bf8a112a4f854dff7%2Fdatabases-rds-instance-networking.png?alt=media)

### Step 6 — Auth & Backup

* **Master Username**: the database admin user
* **Store credentials in AWS Secrets Manager**: AWS generates and rotates the master password, and the secret's ARN is shown on the instance after provisioning. Turn it off to enter a **Master Password** yourself. A password you enter is stored encrypted and sent to AWS only as a hidden CloudFormation parameter.
* **Backup Retention (days)**: `0` turns off automated backups; the maximum is 35
* **Deletion protection**: blocks the instance from being deleted until you turn it off

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-67e9d698dd667657b877545c4f9ba8fee6c26326%2Fdatabases-rds-instance-auth.png?alt=media)

Scroll down for the optional settings:

* **Performance Insights**: turn on query-level monitoring, then choose its encryption key and retention. Not every instance class supports it, and the wizard warns you when the selected class doesn't.
* **IAM database authentication**: lets users sign in with IAM as well as a password
* **Database Insights Mode**: **Standard** or **Advanced**. Advanced turns on Performance Insights with 15-month retention.
* **Enable Logging**: the database log types to stream to CloudWatch Logs; the choices depend on the engine
* **Certificate Authority**: the CA certificate for the database server; leave it blank for the region's default
* **Custom Parameter Group entries**: name and value pairs added to the instance's parameter group

Click **Create & Provision**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-d3ccbb34e96fc22b0807e78fc01147e60cee5dbd%2Fdatabases-rds-instance-auth-options.png?alt=media)

### Step 7 — The agent provisions the instance

The instance's page opens with the status **Provisioning**. Click **Track Status** to open the agent's ticket, **AWSRdsInstance Resource Management - \<name>**. The agent uses the `duplo-aws-resources` skill and works through these phases:

* **Phase 0 — Acknowledge**: confirms the spec file and credentials are present and marks the request as received
* **Phase 0.5 — AWS env setup**: points the AWS CLI at the ticket's own credentials

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bab9da3564ac0be937874a708960f2dbc3bc2c9c%2Fdatabases-rds-instance-agent-start.png?alt=media)

* **Phase 1 — Preflight**: reads the spec, validates it, works out the parameter group family (for example `postgres17`) and the CloudFormation stack name, and adds any custom parameter group entries to the template
* **Phase 2 — Submit CloudFormation stack**: deploys the stack, creating it the first time and updating it on later runs
* **Phase 4 — Poll CloudFormation events**: posts progress until the stack finishes
* **Phase 5 — Finalize**: writes the results back to the instance and marks it **Ready**

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-88fd6b739e448d362468334d282e61c9c48d6632%2Fdatabases-rds-instance-agent-preflight.png?alt=media)

### Step 8 — RDS instance ready

When provisioning finishes, the instance's status changes to **Ready**. The **Overview** tab shows the engine and version, instance class, AWS status, port, Availability Zone, Multi-AZ and public-access settings, the **Endpoint** your applications connect to, and the CloudFormation stack that manages the instance.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6cb36ad2dd362bdaf82c6252982e66834ac6c684%2Fdatabases-rds-instance-overview.png?alt=media)

The other tabs show the rest of the configuration:

* **Storage**: allocated and maximum storage, storage type, IOPS and encryption
* **Networking**: the subnet group, subnets and security groups
* **Parameters**: the parameter group and any custom entries
* **Snapshots**: the instance's snapshots

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-c8fec766f65bfa48a6aa2954de518f041b1aefd2%2Fdatabases-rds-instance-storage-tab.png?alt=media)

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-963d97aedd155aacd885d880fe5317024e20a6c7%2Fdatabases-rds-instance-networking-tab.png?alt=media)

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-80cb91ec4b3072a6c22b455775d245e3a29f24fa%2Fdatabases-rds-instance-parameters-tab.png?alt=media)

***

## RDS Cluster (Aurora)

An Aurora cluster has one writer instance and up to three reader instances that share the cluster's storage.

### Step 1 — RDS Clusters list

In the Resource Group sidebar, open **Cloud Resources → Databases → RDS → Clusters**. The list shows each cluster's engine, mode, instance count, visibility and status. Click **Create RDS Cluster** to start.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-c54154fb49660cbbed227348d57464fb7ce09c72%2Fdatabases-rds-clusters-list.png?alt=media)

### Step 2 — Basics

* **Name**: used as the AWS `DBClusterIdentifier`
* **Description**: optional
* **Restore from cluster snapshot**: turn on to create the cluster from an existing cluster snapshot. The engine, version and credentials come from the snapshot.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5aa82fa44c91e74eb8a14d962051c896a5f5396f%2Fdatabases-rds-cluster-basics.png?alt=media)

### Step 3 — Engine

* **Engine**: `aurora-mysql` or `aurora-postgresql`
* **Engine Version**: the versions available in the Resource Group's region
* **Engine Mode**: **Provisioned** (you choose an instance class for each member) or **Serverless v2** (capacity scales between the **Min ACUs** and **Max ACUs** you set)
* **Initial DB Name**: optional; defaults to the cluster name

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e507310c990dd5dc40949aeb96f424f81aa51e20%2Fdatabases-rds-cluster-engine.png?alt=media)

### Step 4 — Cluster Instances

Add one to four cluster members. The first is the writer. For each member, set:

* **Name**
* **DB Instance Class**: pick from the classes available for the engine version, or type one in (for example `db.t4g.medium`, or `db.serverless` for Serverless v2 members)
* **Availability Zone**: optional

Click **Add instance** to add a reader. Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-6fdc9c61d318591eca468ac89a250c9078da20ba%2Fdatabases-rds-cluster-instances.png?alt=media)

### Step 5 — Networking & Storage

* **Visibility**: **Private (recommended)** or **Public**
* **DB Subnet Group Name**: optional; leave it blank to use the network's managed subnet group
* **Storage Type**: `aurora` (standard) or `aurora-iopt1` (I/O-Optimized)
* **Storage Encryption**: Aurora always encrypts storage. Choose the **Resource Group KMS key** or the **AWS-managed default key**. With the Resource Group key you can also pick a specific **Storage KMS Key**.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-7f99e6d053afcf0462051db1e96981d0ca15fc3a%2Fdatabases-rds-cluster-network-storage.png?alt=media)

### Step 6 — Auth, Backup & Cluster Features

* **Master Username** and **Master Password**: the database admin credentials. The password is stored encrypted.
* **Backup Retention (days)**: 1 to 35
* **Backup Window (UTC)** and **Maintenance Window (UTC)**: optional; leave the start empty to let AWS choose
* **Deletion protection**
* **IAM database authentication**
* **Enable Aurora Data API (HTTP endpoint)**: lets applications run SQL over HTTPS without a database driver
* **Performance Insights**: with its own encryption and retention settings, applied to every member
* **CloudWatch Log Exports**: the log types to stream to CloudWatch Logs
* **Database Insights Mode**: **Standard** or **Advanced**
* **Backtrack Window (seconds)**: Aurora MySQL only; how far back you can rewind the cluster without restoring from a backup
* **Custom Cluster Parameter Group entries**: name and value pairs for the cluster parameter group

Click **Create & Provision**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-8e82a7a7824909edeb4adbdb3366e7b9b23ac969%2Fdatabases-rds-cluster-auth.png?alt=media)

### Step 7 — The agent provisions the cluster

As with an RDS instance, the cluster's page opens with the status **Provisioning**, and **Track Status** opens the agent's ticket. The phases match the RDS instance's, with one extra step in Phase 1: the agent maps each cluster member onto the CloudFormation template, so each member becomes its own instance in the stack. When the stack finishes, the cluster's status changes to **Ready**. Its page shows the engine, the number of instances and the **Writer Endpoint**. From **Actions** you can start or stop the cluster, take a manual snapshot, or reboot a single member.

{% hint style="info" %}
When you delete a cluster, the agent turns off deletion protection, deletes the stack, and AWS takes a final cluster snapshot automatically. You can create a new cluster from that snapshot later, using **Restore from cluster snapshot**.
{% endhint %}

***

## ElastiCache

### Step 1 — ElastiCache list

In the Resource Group sidebar, open **Cloud Resources → Databases → ElastiCache**. Summary cards show how many caches you have, how many are encrypted, how many have snapshots and how many are Multi-AZ. The list shows each cache's engine, cluster mode, topology and status. Click **Create ElastiCache** to start.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-98d5ecab22fdb3425515dec550e16e317000f76b%2Fdatabases-elasticache-list.png?alt=media)

### Step 2 — Basics

* **Name**: used as the AWS `ReplicationGroupId` for Redis and Valkey, or the `CacheClusterId` for Memcached
* **Description**: optional

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-37d0347fee8e2e72fab6f885993d46c103c0fef7%2Fdatabases-elasticache-basics.png?alt=media)

### Step 3 — Engine

* **Engine**: **Redis**, **Valkey** or **Memcached**
* **Engine Version**: the versions available in the Resource Group's region. When you restore from a snapshot, the version comes from the snapshot.
* **Cache Node Type**: for example `cache.t4g.small`
* **Port**: defaults to `6379` for Redis and Valkey and `11211` for Memcached
* **Restore source** (Redis and Valkey only): **None (fresh)**, **ElastiCache snapshot**, or **S3 RDB seed** (one or more `.rdb` files in S3)

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bf9c9f2d8c4d3dfb2b3d70c4b2a3429221d47413%2Fdatabases-elasticache-engine.png?alt=media)

### Step 4 — Topology

For Redis and Valkey, choose a **Cluster Mode**:

* **Disabled**: a single shard with one primary and replicas. Set the **Number of Cache Clusters** (1 primary + N replicas, up to 6).
* **Enabled**: a sharded cluster. Set the **Number of Shards** and the **Replicas Per Shard**.

Multi-AZ and automatic failover are turned on for you whenever the topology has replicas.

For Memcached, set the **Number of Cache Nodes** (1 to 40), the **AZ Mode** (**Cross-AZ** or **Single-AZ**; a single node must be Single-AZ) and, optionally, the **Preferred Availability Zones**. Memcached has no replication; each node holds part of your data.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-0fe93568ce0dd4a8bc5782f8946da7626c17468e%2Fdatabases-elasticache-topology.png?alt=media)

### Step 5 — Encryption & Auth

For Redis and Valkey:

* **At-Rest Encryption**: **Resource Group KMS key (recommended)**, **AWS-managed default ElastiCache key**, or **No encryption**. With the Resource Group key you can also pick a specific **KMS Key**.
* **Transit Encryption (TLS)**: requires TLS on every client connection
* **Auth Token**: required when TLS is on; 16 to 128 characters

Memcached supports only transit encryption, on engine version 1.6.12 and later.

Click **Next**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5da7300025784736470958adf9048c3436ed7df3%2Fdatabases-elasticache-encryption.png?alt=media)

### Step 6 — Backup & Maintenance

* **Snapshot Retention (days)**: Redis and Valkey only; `0` turns off automatic snapshots
* **Snapshot Window (UTC)**: optional; leave the start empty to let AWS choose
* **Maintenance Window (UTC)**: optional; it shouldn't overlap the snapshot window
* **Auto Minor Version Upgrade**: applies minor engine upgrades during the maintenance window
* **Data Tiering**: Redis and Valkey only, and only on `cache.r6gd.*` node types
* **Parameter Group Overrides**: optional name and value pairs

Click **Create**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-809fe019e8c5b1eea9f673e436bb9784a583cb6e%2Fdatabases-elasticache-backup.png?alt=media)

### Step 7 — The agent provisions the cache

The cache's page opens with the status **Provisioning**. Click **Track Status** to open the agent's ticket, **AWSElastiCache Resource Management - \<name>**. The agent reads the ElastiCache skill and the spec, then runs **Phase 0 — Acknowledge**, **Phase 0.5** (AWS credentials) and **Phase 1 — Preflight**.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-c010c8678d78379ba3a4b6d320b37f7148fb268b%2Fdatabases-elasticache-agent-start.png?alt=media)

Phase 1 validates the spec, works out the parameter group family and the CloudFormation stack name, and adds any parameter group overrides to the template.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5a03695beb0b667c194b8fca3ccf44abde8c8e6c%2Fdatabases-elasticache-agent-preflight.png?alt=media)

In **Phase 2** the agent checks whether the stack already exists and then deploys it.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-fa023c5bb5463b02366b54caa4b1fba826207d08%2Fdatabases-elasticache-agent-cloudformation.png?alt=media)

In **Phase 4** it polls the stack until it reaches `CREATE_COMPLETE`, and in **Phase 5** it writes the results back and posts a summary with the engine, node type, topology, encryption settings and endpoints.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cc517be3096c291ff839a8ff9dab7a1fa11dbcfc%2Fdatabases-elasticache-agent-complete.png?alt=media)

### Step 8 — ElastiCache ready

The cache's status changes to **Ready**. The **Overview** tab shows the engine and version, cluster mode, AWS status, port, node type, the **Primary Endpoint** for writes, the **Reader Endpoint** that spreads reads across replicas, and the CloudFormation stack.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-71d73b6ad807abc2e897ba14a15b73e5c9c4f699%2Fdatabases-elasticache-overview.png?alt=media)

The **Cache Clusters** tab shows the topology. The **Shards / Node Groups** table lists each shard with its endpoints, and the **Cache Cluster Nodes** table lists each node with its type, status, Availability Zone and engine version. The **Encryption & Auth**, **Networking**, **Backup & Maintenance** and **Parameters** tabs show the rest of the configuration.

![](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-d4563db8db10afa8470278029e17bf639d265f8e%2Fdatabases-elasticache-cache-clusters-tab.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/quick-start/provision-new/step-6-databases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
