Skip to main content
Launch this lab in the IP Lab Portal, then follow the steps below in the AWS console. Open IP Lab Portal

​
Overview

​
Prerequisites

  1. Good knowledge of AWS service
  • Elastic Container Service (ECS)
  • Elastic Compute (EC2)
  1. Laptop/Desktop
  2. Internet Browser
  3. Internet connection

​
Challenge Instructions

  1. Region : Make sure to use us-east-1 region to create all the resources.
  2. You will be provided with the requirements of the challenge. If you are new to AWS Cloud, we recommend you go through our hands-on Labs before taking this challenge.
  3. Challenge Duration: 1 Hour

​
How to submit the challenge

  1. After building the infrastructure, click on the Check my work button, to validate if you have built the required infrastructure and completed the challenge successfully
  2. Validation status
  • Success - You have completed the challenge successfully.
  • Failed - You have failed to complete the challenge.
  1. Once you have successfully validated the challenge, click on End lab button to end the challenge.

​
Launching Challenge Environment

  1. To launch the challenge environment, Click on the Launch lab button.
  2. Please wait until the cloud environment is provisioned. It will take less than a minute to provision.
  3. Once the Challenge is started, you will be provided with IAM user name, Password, Access Key, and Secret Access Key.
Note : You can only start one challenge at any given time

​
Lab guide

​
Sign in to AWS Management Console

  1. Click on the Open console button, and you will get redirected to AWS Console in a new browser tab.
  2. On the AWS sign-in page,Leave the Account ID as default. Never edit/remove the 12 digit Account ID present in the AWS Console. otherwise, you cannot proceed with the challenge.
  3. Now copy your User Name and Password in the Lab Console to the IAM Username and Password in AWS Console and click on the Sign in button.
  4. Once Signed In to the AWS Management Console, Make the default AWS Region as US East (N. Virginia) us-east-1.

​
Cloud Challenge Details

In this challenge, your Amazon Elastic Container Service (ECS) skills are put to the test. You’ll be given a requirement and you have to reach it using your knowledge of Elastic Container Service (ECS), Task definitions and docker used for this challenge. This Challenge will help you understand the real-time scenarios. A company XYZ wants to automatically scale its application on an Elastic Container Service (ECS) using task definitions and attach to the task running on instance. The below are the tasks that need to be performed by you in order to create the stack.
  1. Create Key Pair
  2. Launch ECS Cluster:
  • Use Amazon EC2 and create New Autoscaling group
  • EC2 Instance Type: t2.micro
  • Capacity: 1-2
  1. Build Task Definition:
  • Container details: Enter httpd
  • URL: Enter httpd2:4
  1. Port Map:
  • Port: 80
  • Protocol: TCP
  1. Infrastructure Requirements:
  • Task size**: .25 vCPU and .5 GB**
  1. Deploy service and run HTTPD container:
  • Configurations: REPLICA as service type
  • Desired task: 1
  1. Run container in ECS cluster:
  • Edit inbound rules in Security group, SSH as Type and IPv4 as Source.
  1. Access the main EC2 instance using SSH and perform Docker commands.
  2. Click on the Validate to complete the challenge.
End lab
  1. Sign out of the AWS Account.
  2. You have successfully completed the challenge.
  3. Click on End lab button in the IP Lab Portal and wait till the process gets completed.

​
What gets checked

When you press Check my work, the platform verifies each of these:
  • Check ECS Cluster Exists — Check ECS cluster is created or not
  • Create ECS Task Definition — Check whether ECS task definition created or not
  • Create ECS Service — Check whether ECS service created or not
  • Launch an EC2 Instance — Check whether an EC2 Instance is launched or not.
  • Validate EC2 Instance Type t2.micro — Check whether the EC2 instance type is t2.micro.
  • Launch EC2 AMI type Amazon Linux — Check whether the EC2 instance is launched using an Amazon AMI.