Feature | Reference ECS cluster implementation

[angelofenoglio]

Describe the Feature

Implement a reference ECS layer in the same fashion as the current EKS demoapps found in the ref arch using a demo application. It should encompass the cluster/service/task definition, ECR storage of the image and traffic routing via ALB.

Use the following definitions:

• Apps

  • Emojivoto: https://github.com/BuoyantIO/emojivoto
  • 1 frontend, 2 backends (APIs), 1 background worker
  • All Private Endpoints:
  • emojivoto.ecs.devstg.aws.binbash.com.ar
  • emojivoto-voting.ecs.devstg.aws.binbash.com.ar
  • emojivoto-emoji.ecs.devstg.aws.binbash.com.ar

• Network

  • ALB: 80 redirect, 443 forward to ECS service
  • TLS: ACM => *.ecs.devstg.aws.binbash.com.ar (WC)
  • DNS: all 3 endpoints above
  • Requires NAT Gateway for ECS to pull from the public Container Registry: consider adding a conditional block in TF to check for the NATGW

• ECS

  • Tasks and services defined by TF (via maps)
  • Image tags set via TF

• Config and Secrets

  • Not in this iteration

• Monitoring

  • Logs: CloudWatch
  • Metrics: CloudWatch
  • ALB Logs: no

• Scalability

  • Not in this iteration

• Documentation

  • Overview, pre-reqs, diagram (ref: https://res.cloudinary.com/practicaldev/image/fetch/s--w2KBP6ZS--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://cdn-images-1.medium.com/max/2000/1%2At5C_XDfg9Ymys9Jea7FDxw.png)

• Make use of these modules:

  • binbashar/terraform-aws-ecs
  • binbashar/terraform-aws-alb