RDS PostgreSQL

Integrate with AWS-managed PostgreSQL for JIT access management for RDS

PostgreSQL databases are open-source relational database management systems emphasizing extensibility and SQL compliance. AWS enables developers to create cloud-hosted PostgreSQL databases.

Through this integration, Apono helps you securely manage access to your AWS RDS for PostgreSQL instances.

Prerequisites

Item Description

Item	Description
Apono Connector	On-prem connection with network access to your AWS RDS for PostgreSQL instances Minimum Required Version: 1.5.3 Use the following steps to update an existing connector. NOTE: When installing the Apono connector with CloudFormation, the AWS RDS database policy is automatically created. If you do not use CloudFormation, you must create the following policy and assign it to the Apono connector role. `{ "Version": "2012-10-17", "Statement": [ { "Action": "rds-db:connect", "Resource": "arn:aws:rds-db:::dbuser:*/apono_connector", "Effect": "Allow" } ] }`
PostgreSQL Info	Information for the database instance to be integrated: Instance ID Database Name
AWS Tag	(Optional) Metadata label assigned to AWS resources Adding an AWS tag, enables Apono to discover and add resources on your behalf. When adding an AWS tag, use the following information: Tag key: apono-secret Value: (AWS Secret)

Apono Connector

On-prem connection with network access to your AWS RDS for PostgreSQL instances Minimum Required Version: 1.5.3 Use the following steps to update an existing connector.

NOTE: When installing the Apono connector with CloudFormation, the AWS RDS database policy is automatically created.

If you do not use CloudFormation, you must create the following policy and assign it to the Apono connector role.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": "rds-db:connect",
            "Resource": "arn:aws:rds-db:*:*:dbuser:*/apono_connector",
            "Effect": "Allow"
        }
    ]
}

PostgreSQL Info

Information for the database instance to be integrated:

Instance ID
Database Name

AWS Tag

(Optional) Metadata label assigned to AWS resources Adding an AWS tag, enables Apono to discover and add resources on your behalf. When adding an AWS tag, use the following information:

Tag key: apono-secret
Value: (AWS Secret)

Create an AWS RDS PostgreSQL user

You must create a user in your AWS RDS PostgreSQL instance for the Apono connector and grant that user permissions to your databases.

Follow these steps to create a user and grant it database permissions:

Create a new user with either Built-in authentication or IAM authentication.

You can use only one authentication option on the RDS instance at a time.

Built-in authentication identifies a user through a username and password.

CREATE USER apono_connector WITH PASSWORD 'secret_passwd';

Be sure to select a strong password for the user.

After enabling IAM on your RDS instance, create an AWSAuthenticationPlugin user for the Apono connector. AWSAuthenticationPlugin is an AWS-provided plugin that works seamlessly with IAM to authenticate your users.

To create the user, run the following commands from your Postgre client.

CREATE USER apono_connector;
GRANT rds_iam TO apono_connector;

From your preferred client tool, grant rds_superuser access to the user.

ALTER USER apono_connector WITH CREATEROLE;
GRANT rds_superuser TO apono_connector;

Permission	Description
ALTER USER apono_connector WITH CREATEROLE;	Allows Apono connector to create, alter, and drop user roles
GRANT rds_superuser TO apono_connector;	Assigns the RDS superuser role to the Apono connector, providing comprehensive permissions for database management

Permission

Description

ALTER USER apono_connector WITH CREATEROLE;

Allows Apono connector to create, alter, and drop user roles

GRANT rds_superuser TO apono_connector;

Assigns the RDS superuser role to the Apono connector, providing comprehensive permissions for database management

(IAM authentication only) Create and attach the following IAM policy to your identity center permissions set or role.

{
     "Version": "2012-10-17",
     "Statement": [
         {
             "Effect": "Allow",
             "Action": [
                 "rds-db:connect"
             ],
             "Resource": [
                 "arn:aws:rds-db:*:*:dbuser:*/${SAML:sub}"
             ]
         },
         {
             "Effect": "Allow",
             "Action": [
                 "rds:DescribeDBInstances"
             ],
             "Resource": [
                 "arn:aws:rds:*:*:db:*"
             ]
         }
     ]
 }

(Built-in authentication only) Create an AWS secret with the credentials from step 1.

When using IAM authentication, a secret does not need to be created.

The service account and its permissions are managed through IAM roles and policies. The service account is used to authenticate the PostgreSQL instance instead of a secret.

Integrate Amazon RDS for PostgreSQL

Follow these steps to complete the integration:

On the Catalog tab, click AWS RDS PostgreSQL. The Connect Integration page appears.
Under Discovery, click one or more resource types to sync with Apono.

Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage Access Flows to these resources.

Click Next. The Apono connector section expands.
From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating an AWS connector.

Click Next. The Integration Config section expands.

Define the Integration Config settings.

Setting

Description

Integration Name

Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

Auth Type

Authorization type for the MySQL service account user

Option

Description

IAM Auth

IAM authentication

User / Password

Built-in authentication

Option

Description

IAM Auth

IAM authentication

User / Password

Built-in authentication

Region

Location where the PostgreSQL database is deployed

Instance ID

ID of the PostgreSQL instance

Database Name

Name of the PostgreSQL database

SSL Mode

(Optional) Mode of Secure Sockets Layer (SSL) encryption used to secure the connection with the SQL database server

Option

Description

require

An SSL-encrypted connection must be used.

allow

An SSL-encrypted or unencrypted connection is used. If an SSL encrypted connection is unavailable, the unencrypted connection is used.

disable

An unencrypted connection is used.

prefer

An SSL encrypted connection is attempted. If the encrypted connection is unavailable, the unencrypted connection is used.

verify-ca

An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass.

verify-full

An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass. Additionally, the server hostname is checked against the certificate's names.

Option

Description

require

An SSL-encrypted connection must be used.

allow

An SSL-encrypted or unencrypted connection is used. If an SSL encrypted connection is unavailable, the unencrypted connection is used.

disable

An unencrypted connection is used.

prefer

An SSL encrypted connection is attempted. If the encrypted connection is unavailable, the unencrypted connection is used.

verify-ca

An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass.

verify-full

Enable Audit

(Optional) Feature that allows Apono to ingest and aggregate session audit logs

Click Next. The Secret Store section expands.
Associate the secret or credentials.

A secret is not needed for IAM authentication.

Click Next. The Get more with Apono section expands.

Define the Get more with Apono settings.

Setting Description

Setting	Description
Credential Rotation	(Optional) Number of days after which the database credentials must be rotated
Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview. NOTE: You can also add the `custom_access_details` parameter to the `apono_integration` schema using Terraform. For more information, learn how to integrate with Apono in the Terraform Registry.
Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

Credential Rotation

(Optional) Number of days after which the database credentials must be rotated

Custom Access Details

(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview. NOTE: You can also add the custom_access_details parameter to the apono_integration schema using Terraform. For more information, learn how to integrate with Apono in the Terraform Registry.

Integration Owner

(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners:

From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.

NOTE: When Resource Owner is defined, an Integration Owner must be defined.

Resource Owner

(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners:

Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

NOTE: When this setting is defined, an Integration Owner must also be defined.

Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your RDS for PostgreSQL database.

PreviousAmazon Redshift NextAWS RDS MySQL

Last updated 1 day ago