Image for running HAProxy with TLS certificte and private key stored in Fortanix SDKMS.
555
This container runs an HAProxy with a certificate and private key stored in SDKMS.
To run this container, you need to have access to Fortanix SDKMS. Please create an account at https://sdkms.fortanix.com, or use a service instance hosted in your environment.
docker.envCustomize the following docker.env file with the appropriate API key of the application added to SDKMS.
FORTANIX_API_ENDPOINT=https://sdkms.fortanix.com
FORTANIX_API_KEY=<insert your API key>
To specify a private key and certificate stored in SDKMS to be used by HAProxy, use the following syntax to specify the location instead of a file name pkcs11:slot_1-label-<key_name>. See the following haproxy.cfg file for example:
# Example haproxy.cfg file
global
maxconn 100
tune.ssl.default-dh-param 2048
defaults
mode http
timeout connect 5s
timeout client 5s
timeout server 5s
frontend myfrontend
bind :443 ssl crt pkcs11:slot_1-label_4096-key:pkcs11:slot_1-label_4096-cert
default_backend mybackend
backend mybackend
server sdkms sdkms.fortanix.com:443 ssl verify none
FROM fortanix/sdkms-haproxy
COPY haproxy.cfg /usr/local/etc/haproxy/haproxy.cfg
$ docker build -t my-haproxy .
sudo docker run -d --name my-running-haproxy --env-file docker.env -p 8443:443 my-haproxy
sudo docker run -d --name my-running-haproxy --env-file docker.env -p 8443:443 -v /path/to/etc/haproxy:/usr/local/etc/haproxy fortanix/sdkms-haproxy
Note that your host's /path/to/etc/haproxy folder should be populated with a file named haproxy.cfg.
Go to website at https://localhost:8443
Content type
Image
Digest
Size
86.8 MB
Last updated
almost 9 years ago
docker pull fortanix/sdkms-haproxy