Skip to content

Docs around SSL support for RDS#635

Merged
quetzalliwrites merged 3 commits into
mainfrom
doc-206-doc-rds-add-ssl-support-at-proxy-level
May 12, 2026
Merged

Docs around SSL support for RDS#635
quetzalliwrites merged 3 commits into
mainfrom
doc-206-doc-rds-add-ssl-support-at-proxy-level

Conversation

@HarshCasper
Copy link
Copy Markdown
Member

Fixes DOC-206

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 6, 2026

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: ac86302
Status: ✅  Deploy successful!
Preview URL: https://adbebf5c.localstack-docs.pages.dev
Branch Preview URL: https://doc-206-doc-rds-add-ssl-supp.localstack-docs.pages.dev

View logs

Copy link
Copy Markdown
Member

@cloutierMat cloutierMat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this to the documentation. I think we should probably be more forward about what we do not support, since this seems to indicate we have mostly full parity with aws, but only sslmode=require is supported and we do not enforce ssl as is suggested by force_ssl

Comment thread src/content/docs/aws/services/rds.mdx Outdated
Comment on lines +314 to +330
### Force SSL connections

To require every client to connect over SSL, set the `rds.force_ssl` parameter on a DB parameter group and associate it with your instance:

```bash
awslocal rds create-db-parameter-group \
--db-parameter-group-name force-ssl \
--db-parameter-group-family postgres17 \
--description "Force SSL connections"

awslocal rds modify-db-parameter-group \
--db-parameter-group-name force-ssl \
--parameters "ParameterName=rds.force_ssl,ParameterValue=1,ApplyMethod=pending-reboot"
```

Pass `--db-parameter-group-name force-ssl` when creating the DB instance, or attach the parameter group to an existing instance and reboot it.
Setting `rds.force_ssl=0` disables the SSL requirement, allowing clients to connect with `sslmode=disable`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not support this. Currently SSL is always enabled (like in AWS), but never enforced (force-ssl=1 is ignored)

Comment thread src/content/docs/aws/services/rds.mdx
Comment thread src/content/docs/aws/services/rds.mdx Outdated

## SSL/TLS Support

LocalStack's RDS PostgreSQL emulation supports SSL/TLS-encrypted client connections, so you can test applications that require `sslmode=require` (or stricter modes) the same way they would connect to AWS RDS.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not currently support stricter mode

Comment thread src/content/docs/aws/services/rds.mdx Outdated
PGPASSWORD=$MASTER_PW psql "host=$HOST port=$PORT dbname=$DB_NAME user=$MASTER_USER sslmode=require"
```

The DB instance uses a self-signed certificate, so clients that pin certificate authorities (`sslmode=verify-ca` or `sslmode=verify-full`) will need to disable certificate verification or supply their own trust anchors.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sslmode=verify-ca or sslmode=verify-full currently not supported

@quetzalliwrites
Copy link
Copy Markdown
Collaborator

tyvm for the solid review @cloutierMat ! :)

i'll let harsh address your feedback

@quetzalliwrites
Copy link
Copy Markdown
Collaborator

ping @HarshCasper this still has feedback waiting for you :)

HarshCasper and others added 2 commits May 11, 2026 20:38
Co-authored-by: Mathieu Cloutier <79954947+cloutierMat@users.noreply.github.com>
@HarshCasper HarshCasper requested a review from cloutierMat May 11, 2026 15:15
Copy link
Copy Markdown
Member

@cloutierMat cloutierMat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Harsh for adding this documentation and addressing the comments.

@quetzalliwrites quetzalliwrites merged commit 8379b1e into main May 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants