Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

DRAFT

Overview

various service endpoints: Managing Access to open platforms

Deployment Design

Our services are deployed on AWS, connected to an externally managed database(mongodb).

Components:

  • ECR to store our images for each environment(aplha, beta, gamma, live).

  • ECS(fargate) to deploy our container service.

  • Network for our services attached to internet gateway for external access and some security groups and route table for managing traffic access.

  • Load balancer to manage traffic to our service.

Infrastructure

Currently we have aws folder in the voluntarily repo containing cloudformation scripts and few other bash scripts that will deploy each environment based on environment specific config file. This is a manual setup for each environment.

Voluntarily Service

Once the infrastructure is setup, it will deploy the service based on task definitions for the ECS cluster. The CI pipeline then builds and pushes new image to ECR and runs a update command for ECS service to pull the latest image to roll out a new version of service. CI only deploys alpha and beta currently, other environments are deployed manually.

Things missing here:

  • cloudflare setup

  • are we using the route53 records? I was unable to find/understand how they link up to the load balancer

  • env vars set up detailed to explain what in required for service to run

  • No labels