Activation of config file fails with error-Replication Slot not created in database. (4381304)

Activation of config file with postgresql RDS as source is failing with replication Slot not created in database.

Oconf log:

conf 2025-11-11 11:22:46.300823 3072360 46610304 Error while executing the query
oconf 2025-11-11 11:22:46.300845 3072360 46610304 error_code=1 state=42501 msg=ERROR: must be superuser or replication role to use logical replication slots in the 'RDS' namespace;

Postgres log

ERROR: must be superuser or replication role to use logical replication slots in the 'RDS' namespace
splextest@hostname:[22103]:STATEMENT: SELECT PG_CREATE_LOGICAL_REPLICATION_SLOT ('rds_test_slot','pgoutput')

AWS does not allow slot names starting with RDS because these prefixes are reserved for internal use. 

AWS RDS reserves certain prefixes (like rds, aws, amazon) for internal use. Slot names starting with RDS cannot be created by users, even if the user has the rds_superuser role.

• Do not create replication slots with names starting with RDS.
• You can include RDS inside the name, but not at the beginning. Examples:
  
  • ✅ slot_rds_qa1
  • ❌ rds_slot_qa1