Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Version: 1.0.0

Category: Database

Tier: 2

Type: Source, Target

Authentication:

  • Standard Authentication:

    • Host

    • Port

    • Username

    • Database name

    • Password

  • IAM Authentication

    • Host

    • Port

    • Username

    • Access Key

    • Secret Key

    • Region

Supported Save Mode as Target:

  • Append

  • Overwrite

See: Target Connector Save Modes

Connection Properties:

 

image-20240417-051305.png

Name

Mandatory

Description

Connection Name

Yes

Name of the connection

Description

No

Description of the connection

Host Name

Yes

Host or “Endpoint“

Port

Yes

Port number

Schema

No

Schema name in the database

Database

Yes

Name of the database for the connection

Username

Yes

Username of the database

Authentication

Yes

Type of authentication:

  • Standard

  • IAM

Password

Yes

Password of the database

 

STANDARD AUTHENTICATION:

  1. Log in to your AWS account console.

  2. On the search bar type RDS and select the RDS service

  1. Once you are in the RDS service page, Click on Databases tab on the side bar to see all your databases. 

  1. Select your RDS PostgreSQL database

  1. To Connect your Database to EazyDi app using the STANDARD authentication, you will need:

  • Host

  • Port

  • Username

  • Database name

  • Password

  1. Once you have clicked your RDS PostgreSQL database, You will see the “ENDPOINT” which will be your HOST. And the PORT number

  1. To Get your USERNAME and DATABASE NAME, go to the “CONFIGURATION” Tab and there you will see your DBNAME and MASTER USERNAME which you will use as your USERNAME and DATABASE NAME

  1. Once you have all your credentials, you can now connect your database to EazyDi app. Create a connection. Select the AWS RDS PostgreSQL connector

  1. Input all the required connection properties that you got from Step 6 and 7. The Host, Port, DBNAME, Master Username. The password is the one you set when creating your database. *Note that you will input the DBNAME in the “Database” field

  1. Once you have created a connection, you can now select a table from the list of connection objects

IAM AUTHENTICATION:

References:

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html

https://aws.amazon.com/blogs/database/using-iam-authentication-to-connect-with-pgadmin-amazon-aurora-postgresql-or-amazon-rds-for-postgresql/

  1. First, make sure that your database allows IAM Authentication. Do Pre requisites steps 1 through 3 then Navigate to Configuration Tab. Confirm that IAM DB authentication is Enabled

  1. To allow an IAM user or role to connect to your database instance or database cluster, you must create an IAM policy. After that, attach the policy to an IAM user or role. For more information, see Create and Attach Your First Customer Managed Policy.

You construct the policy document from the following four key pieces of data:

  • The Region of your cluster

  • Your AWS account number

  • The database resource ID or the cluster resource ID

  • Your database user name

For RDS:

  1. After you create your IAM user and attach your IAM policy to the user, create a database user with the same name that you specified in the policy. To use IAM authentication with PostgreSQL, connect to the database cluster, create the database user, and grant them the rds_iam role. You can connect as any user that has CREATE USER permissions and execute the following statements:

CREATE USER mydbuser WITH LOGIN; 

GRANT rds_iam TO mydbuser;

  1. Go back to dashboard and search for AWS RDS Postgresql and click connect 

  1. Click add new connection

  1. Choose Authentication as IAM authentication and fill in the required fields. The username used should be the created in step 3, add the access key and secret key of the IAM user that has the policy created in step 2, then click create connection

  1. Verify that credentials and setup are correct by checking if connection object lists will show similar to stanard authentication

  • No labels