- The Mapping Object
- Automatic Retries
- Canary Releases
- Circuit Breakers
- Cross-Origin Resource Sharing
- Method-based Routing
- Prefix Regex
- Traffic Shadowing
- Developer Portal
- Edge Policy Console
- The Ambassador Module
- Gzip Compression
- Host CRD, ACME Support, and External Load Balancer Configuration
- Ingress Controller
- Troubleshooting Ambassador
- Custom Filters
- Knative Serverless Framework
- Prometheus monitoring
- Frequently Asked Questions
Sometimes, for additional security or authentication purposes, you will want the server to validate who the client is before establishing an encrypted connection.
To support this, Ambassador can be configured to use a provided CA certificate to validate certificates sent from your clients. This allows for client-side mTLS where both Ambassador and the client provide and validate each other's certificates.
Create a certificate and key.
This can be done with a single command with
openssl:openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365
Enter a passcode for PEM files and fill in the certificate information. Since this certificate will only be shared between a client and Ambassador, the Common Name must be set to something. Everything else can be left blank.
Note: If using MacOS, you must add the certificate and key as a PKCS encoded file to your Keychain. To do this:
key.pemcreated above in PKCS formatopenssl pkcs12 -inkey key.pem -in cert.pem -export -out certificate.p12
Open "Keychain Access" on your system and select "File"->"Import Items..."
Navigate to your working directory and select the
certificate.p12file we just created above.
Create a secret to hold the client CA certificate.kubectl create secret generic client-cacert --from-file=tls.crt=cet.pem
Configure Ambassador Edge Stack to use this certificate for client certificate validation.
First create a
Hostto manage your domain:apiVersion: getambassador.io/v2kind: Hostmetadata:name: example-hostspec:hostname: host.example.comacmeProvider:email: firstname.lastname@example.org
Then create a
TLSContextto configure advanced TLS options like client certificate validation:---apiVersion: getambassador.io/v2kind: TLSContextmetadata:name: example-host-contextspec:hosts:- host.example.comsecret: host.example.comca_secret: client-cacertcert_required: false # Optional: Configures Ambassador to reject the request if the client does not provide a certificate. Default: false
Note: Client certificate validation requires Ambassador Edge Stack be configured to terminate TLS
Ambassador is now be configured to validate certificates that the client provides.
Test that Ambassador is validating the client certificates with
Linux:curl -v --cert cert.pem --key key.pem https://host.example.com/
MacOS:curl -v --cert certificate.p12:[password] https://host.example.com/
Looking through the verbose output, you can see we are sending a client certificate and Ambassador is validating it.
If you need further proof, simply create a new set of certificates and try sending the curl with those. You will see Ambassador deny the request.