Use special character in DB password DMS endpoint

Having the exact same issue. Did you find a solution in the meantime?

Same issue, is it a bug after aws update dms. I didn't faced it before (same password)

The curly braces {} are reserved characters for DMS allowing you to escape "unusual" characters that might otherwise cause problems for the connection string. It is therefore not possible at present to use them in the database password for the account used by DMS. We are aware of the limitation and will work to resolve it in the future.

JohnW@AWS wrote:
The curly braces {} are reserved characters for DMS allowing you to escape "unusual" characters that might otherwise cause problems for the connection string. It is therefore not possible at present to use them in the database password for the account used by DMS. We are aware of the limitation and will work to resolve it in the future.

Hi,
Any updates on this issue.
I need to set up source endpoint for DMS and the password contains both the characters ;}

Edited by: sendhil on Aug 25, 2020 3:34 AM

Edited by: sendhil on Aug 25, 2020 3:36 AM

It's not really acceptable that DMS has tighter password restrictions than the source/target databases it works with.

For Oracle RDS we can (and do) use long machine generated passwords with many special characters such as !#$%&*+,-.:;<=>?[]^_{|}~... because we want the highest entropy possible. Notice that we even use curly braces { and } ... so it will be very frustrating if we have to start reducing things down to the lowest common denominator just because of DMS. :-/

Any word on when this restriction will be lifted?