- Reduce Over Privileges - Discover existing privileges to PostgreSQL databases and convert them to on-demand access flows to reduce over-privileges.
- Self Service Access - Empower your developers to gain self-servable access to databases using Slack.
- Automated Approval Workflows - Create approval workflows to specific sensitive databases.
- Restricted Third Party Access - Grant third-party (customer or vendor) time-based access to specific databases with MFA verification.
- Review Access - View a detailed access audit of who was granted access to which databases with what permission level and why.
Is your PostgreSQL running on a cloud service?
- Click on Integrations Catalog.
- Under Data Sources, look for PostgreSQL and click Connect
- Specify the integrations details:
- Integration name – type the name of the integration
When building an Access Flow you will reference this name
- Select the Connector – specify the Connector name with access to this PostgreSQL
- Hostname – specify the hostname of the PostgeSQL you are connecting
AWS - Identify the secret
If you chose a Connector installed on an AWS account you will need to enter a Secret ID from within your AWS Secrets Manager
- Region – Choose the region where the secret resides
- Secret ID – Choose the secret ID that is used to access this PostgreSQL with admin privileges. If you don't have one you can create one
- Click Connect
GCP - Identify the secret
If you chose a Connector installed on an GCP account you will need to enter a Secret ID from within your GCP Secrets Manager
- Project - the project ID
- Secret ID - Choose the Secret ID that is used to access this PostgreSQL with admin privileges. If you don't have one you can create one using this GCP guide.
Look for the Secret ID in your Secret Manager (via Google console)
- Click Connect
Have multiple PostgreSQLs? Use the API
You can check out the Apono API reference to easily integrate multiple integrations.
Updated 10 days ago