# Handling NHS Digital Certificates in AWS

**Category:** [open forum](https://openhealthhub.org/c/open-forum/9)
**Created:** 2022-03-19 08:18 UTC
**Views:** 489
**Replies:** 0
**URL:** https://openhealthhub.org/t/handling-nhs-digital-certificates-in-aws/2632

---

## Post #1 by @mayfield.g.kev

We're just about to expand our connections to NHS Digital API's (MESH, LDAP and PDS).

I'm not sure which certs I need for which system + environment but it sounds like I would need a few. 

![Screenshot 2022-03-19 at 08.12.12|690x331](upload://mvWgkBP9sf1rjM6KcUmDOnCzHZY.png)

Previously I've added the certificates to java based Apache Camel and deployed a security proxy to AWS ECS. So the consuming client just works with our security and calls our ECS security proxy, this adds/removes the necessary headers and then sends the request out on a connection which uses the SSL/TLS certificate.

However that needs a lot of java config and wondering if there is something more flexible?
Something like a reverse proxy where I can apply a cert to the outbound connection.
(I'll probably still handle the http headers in code as this can get complicated)

---


**Canonical:** https://openhealthhub.org/t/handling-nhs-digital-certificates-in-aws/2632
**Original content:** https://openhealthhub.org/t/handling-nhs-digital-certificates-in-aws/2632