This section provides an overview of what amazon-web-services is, and why a developer might want to use it.
It should also mention any large subjects within amazon-web-services, and link out to the related topics. Since the Documentation for amazon-web-services is new, you may need to create initial versions of those related topics.
Current Limitations (As of 2016-10-03)
Automation with Jenkins
There is a great AWSEB Deployment Plugin for Jenkins that will plug-n-play for deployment to Elastic Beanstalk (blue/green deployments with automatic idle termination is just a checkbox away).
Before you can add ECS instances to a cluster you must first go to the EC2 Management Console and create ecs-optimized instances with an IAM role that has the AmazonEC2ContainerServiceforEC2Role policy attached.
Launch Instance button.Community AMIs, search for ecs-optimized, and select the one that best fits your project needs. Any will work. Click next.Configure Instance Details, click on the create new IAM role link and create a new role called ecsInstanceRole.AmazonEC2ContainerServiceforEC2Role policy to that role.default cluster. If you want to launch into your own cluster instead of the default, choose the Advanced Details list and paste the following script into the User data field, replacing your_cluster_name with the name of your cluster.#!/bin/bash
echo ECS_CLUSTER=your_cluster_name >> /etc/ecs/ecs.config
NOTE: If you a creating a web server you will want to create a securityGroup to allow access to port 80.
aws ecr create-repository --repository-name example-repositoryaws ecr get-login --region us-east-1 | shdocker build -t example-image .docker tag example-image:latest example-namespace/example-image:latestdocker push example-namespace/example-image:latestaws ecs register-task-definition --cli-input-json example-task.jsonaws ecs run-task --task-definition example-task