Connecting Amazon RDS (PostgreSQL) to Amazon Q Business
Note
Amazon RDS (PostgreSQL) connector remains fully supported for existing customers through May 31, 2026. While this connector is no longer available for new users, current users can continue to use it without interruption. We are continuously evolving our connector portfolio to offer more scalable and customizable solutions. For future integrations, we recommend exploring the Amazon Q Business Custom Connector Framework[1], designed to support a broader range of enterprise use cases with enhanced flexibility.
Amazon RDS (PostgreSQL) is a web service that makes it easier to set up, operate, and scale a relational database in the AWS Cloud. If you are a AWS user, you can use Amazon Q Business to index your Amazon RDS (PostgreSQL) data source.
The Amazon Q Amazon RDS (PostgreSQL) data source connector supports PostgreSQL 9.6.
You can connect your Amazon RDS (PostgreSQL) instance to Amazon Q Business—using either the AWS Management Console, CLI, or the CreateDataSource API—and create an Amazon Q web experience.
Important
As a best practice, provide Amazon Q with read-only database credentials. Also, avoid adding tables with sensitive data or personal identifiable information (PII).
Topics
Prerequisites for connecting Amazon Q Business to Amazon RDS (PostgreSQL)
Connecting Amazon Q Business to Amazon RDS (PostgreSQL) using the console
Connecting Amazon Q Business to Amazon RDS (PostgreSQL) using APIs
How Amazon Q Business connector crawls Amazon RDS (PostgreSQL) ACLs
Amazon RDS (PostgreSQL) data source connector field mappings
Learn more
-
For an overview of the Amazon Q web experience creation process using IAM Identity Center, see Configuring an application using IAM Identity Center.
-
For an overview of the Amazon Q web experience creation process using AWS Identity and Access Management, see Configuring an application using IAM.
-
For an overview of connector features, see Data source connector concepts.
-
For information about connector configuration best practices, see Connector configuration best practices.