This guide aims to assist in deploying the Jamf AD CS connector behind an application load balancer in AWS, detailing steps to export the server certificate from the IIS server created by the ADCS Connector installation tool and import it into AWS ACM for use on the load balancer.
Note: This guide does not include configuring or deploying an AWS load balancer.
- Access to the AD CS connector host (IIS server)
- Knowledge of the installation location on the IIS server
- Access to AWS to create ACM certificates
For a reverse proxy/ALB setup, it's necessary to upload the same server cert used by IIS to ACM.
- Log into the AD CS connector Windows host.
- Open IIS Manager. You can use
Windows + R
and typeinetmgr
, or search for IIS. - In the left pane, expand the site (probably the only one), click Sites, then select AdcsProxy.
- In the right pane, under Actions, click on Bindings.
- Select the HTTPS binding, click Edit, then click View next to the SSL Certificate to see the certificate details.
- Open
mmc
(Windows + R and typemmc
). - Go to File → Add/Remove Snap-In.
- Select Certificates and click Add.
- Choose Computer Account, click Next, then select Local Computer and click Finish and then OK.
- Expand Certificates (Local Computer) in the left pane.
- Navigate to Personal → Certificates.
- Locate the certificate (usually the fqdn of the ADCS connector host), right-click, select All Tasks → Export.
- Follow the wizard to export the certificate with the private key and all extended properties. Set a memorable password as you'll need it later.
- Convert the server certificate from pfx to pem format using OpenSSL commands:
- Export the key and remove the password.
- Export the cert.
- Convert the chain cer to pem.
- Upload them to ACM and associate the ACM cert with your load balancer.
To ensure health checks pass without the client cert:
- Open IIS Manager, select the site.
- Double Click on SSL Settings.
- Uncheck Require SSL. Restart the site afterwards.
Check if the load balancer is configured correctly:
- ELB Security Policy should support TLS 1.2 as Jamf's AD CS connector does not support TLS 1.3.
- Security Group Ports should allow communication as needed.
If AWS ACM shows "Key does not match certificate," ensure the correct exporting and splitting of the server cert.