React Environment Variables Packaging your ReactJS application as a Docker container provides all of the usual Docker benefits: portability, ease of maintenance, cloud support, standardization, and on and on and on. One pitfall of using client-side rendering with React is with the use of environment variables. Lets look at a quick example: In this example,
This is the final post of this series. If you have not yet done so, go back and read the previous posts. Terraform and Amazon ECS – Part 1 Terraform and Amazon ECS – Part 2 Terraform and Amazon ECS – Part 3 This post will wrap up with the creation of the service definitions
If you have not already done so, read Terraform and Amazon ECS – Part 1 and Terraform and Amazon ECS – Part 2 before proceeding. Now that we have a VPC and a Load Balancer to route traffic to our APIs, its time to create our ECS Cluster and all of the services and associated
If you have not already done so, read Terraform and Amazon ECS – Part 1 to get started. I left off having created all of the resources for the VPC which will house the rest of the infrastructure for this application. So, the next step is going to be added some components into the VPC
Preface Amazon’s Elastic Container Service (ECS) is a platform for deploying Docker containers into the AWS Cloud. It provides a rich set of tools for integrating your containerized application with other AWS services as well as features for managing and monitoring your application. Read more about Amazon ECS. I’ll be deploying a small, five-container application