Amazon EC2 Container Service

We started using Amazon EC2 Container Service 3 years ago because it was the easiest containers orchestration tool to start with. At the time it was missing a lot of features compared to other tools, but it was still the fastest way to deploy a container on AWS. As with any AWS product, over time they caught up and improved it significantly. Today it probably one of the best tools in its category. It might not have all the feature Kubernetes has, but it also has less complexity. And it definitely has all the features a small company/team needs.

To load data from our Amazon S3 data warehouse into the Elasticsearch cluster, I developed a Spark application that uses PySpark to extract data from S3, partition, then batch-send each partition to Elasticsearch to increase parallelism. The Spark job enables fielddata: true for text columns with low cardinality to allow sub-aggregations by text columns and prevents data duplication by adding a unique _id field to each row in the dataframe.

The job can then be run by data scientists in Flotilla, an internal data platform tool for running jobs on Amazon EC2 Container Service, with environment variables specifying which schema and table to load.

With a little forethought, ECS can handle a good portion of my development stack as though it were production. 12 Factor configuration makes this a breeze. Amazon EC2 Container Service

Used EC2 for web service server and application testing for more containers. Amazon EC2 Container Service

Amazon EC2 is our primary application hosting solution. Most applications are not exposed on the internet and use a virtually private cloud to interact with each other. Amazon EC2 Container Service

I don't like AWS BUT Pagely's VPS-3 makes it work. I still use FireHost for most things Amazon EC2 Container Service