aws-samples/amazon-ecs-catsndogs-workshop

This is self-paced workshop designed to allow developers and system administrators to get hands on with Amazon Elastic Container Service concepts such as service and container-instance auto-scaling, spot-fleet integration, container placement strategies, service discovery, secrets management with AWS Systems Manager Parameter Store, time-based and event-based scheduling, and automated deployment pipelines.

amazon-ecs-catsndogs-workshop's Issues

No information on how to use Fargate launch type with secrets coming from Parameter Store

Initial Setup: Add cli command for deploying CloudFormation

Rather than use the console to deploy the CloudFormation template, I would like to have the option to deploy via command line. It's not hard to form the command, but could help smooth out the user interaction.

aws cloudformation deploy --template-file cfn-templates/Lab0-baseline-setup.yml --stack-name catsndogssetup --capabilities CAPABILITY_IAM

Detailed instructions for Lab 5

Port detailed instructions for Lab 5 to markdown format

Detailed instructions for Lab 7

Port detailed instructions for Lab 7 to markdown format

Add ECR lifecycle management to one of the labs

https://aws.amazon.com/blogs/compute/clean-up-your-container-images-with-amazon-ecr-lifecycle-policies/

New Path for Experienced Users

Add a new CloudFormation template that creates the cluster etc, to allow an experienced user to bypass Lab1 and 2, and start Lab3 with a fully functional cluster with task and service resources created.

Lab to demonstrate how container healthchecks improve reliability of deployments.

After the deployment pipeline has been configured, a health check should be added to the task definition for the dogs application. The health check should test for the presence of particular file (for example, 1.jpg).

From the IDE, the Dockerfile is intentionally modified to ensure the dog memes don't get pulled in to the image at build time.

The changes are then committed and the pipeline will build the new image and attempt to deploy. Based on the roll out configuration of the dogs service. The new version of dogs, with the missing images, should not make it in to production, the deployment should fail, but their should be at least 50% of the current dogs containers still running, ensuring that there is no loss of service.

Detailed instructions for Lab 2

Port detailed instructions for Lab 2 to markdown format

LAB7 Cloudformation name does not exist

Cloudformation template Lab7-blue-green-canary.yml does not match with the cloudformation template name for LAB7 listed on cnf-templates directory.

Lab0-baseline-setup.yml Error in Domain property

There is an error in the syntax of the Domain property for the NATGateway1EIP resource; "Vpc" is incorrectly capitalized and should be "vpc".

6.1 - Step 9 - Incorrect Git Command

Step currently states:
git command -m ‘changing background color’

Should be
git commit -m "changing background color"

LAB5 configuring AWS CLI

Include a step that would teach how to configure the AWS CLI. Potentially add an option for Powershell CLI.

5.4 - Step 5 - Should Cloud9 be used here?

This step is the first time that the CLI is used. Should we use Cloud9 here? We could move the Cloud9 installation step from Lab 6.

6.1 - Step 9 - Format of git commands does not not rest of lab

The commands are shown as steps with i, ii and iii. This should be shown as a single block of code like the other git command sin this lab.

Add diagrams to each lab

Consider adding diagrams of the current state of the cluster and services as the workshop progresses. This will aid in the understanding of what has been deployed.

6.2 - Step 12 - Missing environment variable values

The step asks you to create the following environment variables but shows the values as blank:
AWS_DEFAULT_REGION:
AWS_ACCOUNT_ID:

Should be:
AWS_DEFAULT_REGION: for example: eu-west-1
AWS_ACCOUNT_ID: for example: 12345567891011

5.2 - Step 8 - Spread placement based on instance type.

If you include spread placement based on instance type the mxnet service will fail to create.

Remove step 8.

Lab0-baseline-setup.yml Please add DependsOn attributes to VPC related resources

Please include DependsOn attributes to the VPC related resources to prevent potential CF template rollbacks.

Move detailed instructions to markdown or ascidoc

The detailed instructions are currently in MS word format. It would be great to move this over to markdown or ascidoc so that it is easier to consume.

Container Networking Enhancement

Scenario:
Have the user upgrade the ECS agent the your container instances to the latest version. Then configure and update your task definitions to use container networking.

Detailed instructions for Lab 4

Port detailed instructions for Lab 4 to markdown format

Lab 2 (Detailed instructions - 2.2 - 11ii) - Incorrect "RequestCount"

Enter: Add 20 tasks when 2000 <= RequestCount < 000

I believe 000 should be 4000 instead.

Detailed instructions for Lab 3

Port detailed instructions for Lab 3 to markdown format

Detailed instructions for Lab 1

Port detailed instructions for lab 1 to markdown format.