By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

DMS endpoint connection test fails for Postgres 15, DMS 3.5.1

0

I've been successfully running DMS migrations into a Postgres 14 target for some months now. Seeing that DMS 3.5.1 now supports Postgres 15.x, I created a Postgres 15.3 database and tried to setup DMS 3.5.1 against it. Unfortunately I get the following error when running a connection test on the endpoint:

Test Endpoint failed: Application-Status: 1020912, Application-Message: Cannot connect to ODBC provider Network error has occurred, Application-Detailed-Message: RetCode: SQL_ERROR SqlState: 08001 NativeError: 101 Message: FATAL: no pg_hba.conf entry for host MY_HOST, user MY_USER, database MY_DB, no encryption

I'm using the same CloudFormation templates that were previously successful with Postgres 14. I have also verified that I can connect to the database with the same credentials (using psql).

Topics
Migration & ModernizationDatabase
Tags
AWS Database Migration ServicePostgreSQL
Language
English
bela
asked 9 months ago1618 views
5 Answers
1
Accepted Answer

Hey for PostgreSQL 15, SSL is on by default so if you are not using then try updating the rds force ssl parameter to 0 and retry

AWS
Tanzim_M
answered 9 months ago
1

I was getting same error, After modifying DMS postgress endpoint SSL mode "none" to "require", it resolved my error while doing test endpoint connection Enter image description here

Ganesh Chokhare
answered 5 months ago
0

I have the same issue as the author, how can I fix this issue?

Tan Ly
answered 7 months ago
0

Have you ensured your security group on your RDS instance allows connections from the host used for DMS?

profile picture
EXPERT
Gary Mclean
answered 9 months ago
0

Hi, support for pg v15 in DMS v3.5.1 is leading-edge: announced a week ago. See https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReleaseNotes.html

Given your the strong basis of your trial based on your previous experience (and guessing that you have proper pg_hba.conf from you v14 activity) , you may well have reached a "teething problem" of this new release. I would suggest you to open a Support case via AWS console. Service teams do not monitor re:Post for such issues.

Especially since https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.PostgreSQL.html doesn't mention any restriction specific to pg v15

Best,

Didier

profile pictureAWS
EXPERT
Didier_Durand
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content