{"id":4497,"date":"2025-05-03T16:25:22","date_gmt":"2025-05-03T16:25:22","guid":{"rendered":"https:\/\/geekmungus.co.uk\/?p=4497"},"modified":"2025-05-03T16:25:23","modified_gmt":"2025-05-03T16:25:23","slug":"example-website-workload-aws-elastic-container-service-aws-with-alb-route53-and-certificate","status":"publish","type":"post","link":"https:\/\/geekmungus.co.uk\/?p=4497","title":{"rendered":"Example Website Workload – AWS Elastic Container Service (AWS) with ALB, Route53 and Certificate"},"content":{"rendered":"\n

The below gives a simple example showing how you can deploy a containerised workload: a NGINX web server in this example which has two (or more) containers (tasks) running on AWS Fargate, presented behind a “Service” definition which is then presented to the Internet via an Application Load Balancer (ALB) where a certificate is obtained and added to the ALB, and AWS Route53 is used to create the DNS record automatically to point at the ALB.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The example offers limited customisation, deploys the EU-WEST-2 Region <\/strong>(London) with two subnets in different Availability Zones<\/strong>: EU-WEST-2A and EU-WEST-2B.<\/p>\n\n\n\n

The example uses the domain tristanself.co.uk<\/strong>, which has its nameservers running within AWS Route53, allowing records to be added, changed and removed programatically. However you may substitute in your own domain name as required, however you must ensure that have obtained the AWS Route53 Hosted Zone ID first, which along with the domain name needs to be entered into the variables.tf<\/strong> file.<\/p>\n\n\n\n

The example uses a local Terraform state storage, however you may easily swap this to use remote state, see the documentation\u00a0https:\/\/geekmungus.co.uk\/?p=4120<\/a> if you require it.<\/p>\n\n\n\n

Repository<\/h1>\n\n\n\n

The example Terraform definitions can be found within Gitlab:<\/p>\n\n\n\n