Member-only story

🔑Setting up Cert-Manager with Ambassador API Gateway

Test Case for: ACME HTTP01 Challenge, Lets Encrypt, and AWS

⚗ Kevin Summersill 🔋
8 min readApr 28, 2020
Ambassador API Gateway

✔ 1. 🔌 Install Ambassador either via the CLI or Manually

🔷 This article will start off with the assumption that you already have installed Ambassador within your Kubernetes environment. If not, then click on this link to get started: Using CLI to Install Ambassador.

🔷 You can also install manually via a YAML file which is how I installed Ambassador. Which you can view here: Manually Installation with YAML.

✔2. 🔱 Setting up the Elastic Load Balancer Endpoint for AWS

🚩 This is a very critical step. If you do not have an endpoint from AWS after setting up the L4; you will NOT be able to move forward. If you are using AWS please setup your Ambassador service using either L4 or L7 TLS configuration. The example we will use is L4. You can find more on how to set up this configuration at Running L4 Load Balancer.

Note: Make sure that you have properly pointed your domain to the ELB service created for Ambassador.

✔3. Setting up Cert Manager with 0.14.2

This example utilizes the 0.14.2 release but you should be able to use any release that isn’t too vastly different on ACME…

--

--

⚗ Kevin Summersill 🔋
⚗ Kevin Summersill 🔋

Written by ⚗ Kevin Summersill 🔋

Enterprise Solution Architect | Certified K8s Administrator/Developer ⚓ | SAFe SPC | Cert Terraform | AWS Solutions Architect | Dev*Ops/GitOps Engineer 🔥

No responses yet