# AWX connectivity to AWS RDS Postgres issues when forcing SSL

**URL:** <https://forum.ansible.com/t/awx-connectivity-to-aws-rds-postgres-issues-when-forcing-ssl/10313>\
**Category:** Get Help\
**Tags:** ssl, aws, awx, postgresql\
**Created:** [October 15, 2024, 9:51pm UTC](https://forum.ansible.com/t/awx-connectivity-to-aws-rds-postgres-issues-when-forcing-ssl/10313 "2024-10-15T21:51:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![td784](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@td784](https://forum.ansible.com/u/td784)\
**Post date:** [October 15, 2024, 9:51pm UTC](https://forum.ansible.com/t/awx-connectivity-to-aws-rds-postgres-issues-when-forcing-ssl/10313/1 "2024-10-15T21:51:05Z")

</div>

Hi team,

I am having issues with getting the awx\_task deployment, and awx\_web deployment to connect to an AWS RDS database when we enable the `rds.force_ssl: 1` parameter.

When this parameter is turned on and we have the `ssl_mode` of the postgres configurations secret set to `require`, we are recieving the following error:

```auto
django.db.utils.OperationalError: connection failed: ems not enabled

```

These are running on FIPS enabled AMI’s in an EKS cluster, and when we checked the status, we were able to see that FIPS was enabled but the setup was logging as incomplete.

We are able to get AWX running when we turn the `rds.force_ssl` parameter to false, but this is a requirement to have this setting enabled for running in our environment.

Any help would be greatly appreciated in this space.

Cheers.