Skip to content
This repository has been archived by the owner on Jul 2, 2019. It is now read-only.

Production Deployment

Jump to bottom
Peter Keeler edited this page Oct 29, 2018 · 3 revisions

AWS

The official copy of The Agony Engine is deployed in AWS. There is a fair amount of infrastructure that needs to be set up.

  • AutoScaling Group of EC2 instances
  • ECS cluster, IAM roles, security groups
  • RDS MySQL (Aurora) database
  • ActiveMQ message broker
  • Application Load Balancer
  • Route53 for DNS to the ALB
  • ACM providing the ALB's HTTPS certificate
  • ECR for storing Docker containers
  • CodeBuild to build when code is committed to GitHub
  • CodePipeline to deploy when code is merged to the master branch

These components together provide the infrastructure to run The Agony Engine in a "highly available" way, with multiple instances of the server distributed across multiple Availability Zones. They also provide continuous delivery, automatically building and deploying the new code each time changes are merged to master.

I'm currently not running The Agony Engine in multiple regions, but it is an option.

Clone this wiki locally