DIY

After completing the lab, the player does DIY

  1. In the DIY interface
  • Read DIY ACCTIVITIES
  • Read SOLUTION VALIDATION METHOD

DIY

  1. In the DIY interface
  • Select START LAB

DIY

  1. In the AWS Console interface
  • Find EC2
  • Select EC2

DIY

  1. In the EC2 interface
  • Select Instances
  • Select lab/TravelAgencyWebServers
  • Select Details to view instance details

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers auto scaling group
  • Select Details to see the details of the auto scaling group

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling Group
  • Select Instance management
  • View instance information

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers
  • Select Details to view Desired capacity, Minimum capacity, Maximum capacity

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling Group
  • In Network, see Subnet ID information
  • In Load balancing, select Edit

DIY

  1. In the Edit TravelAgencyWebServers interface
  • Select Add a new load balancer

DIY

  1. In the Load balancing interface
  • Load balancer type, select Application Load Balancer
  • Load balancer scheme, select Internet-facing

DIY

  1. In the interface Edit TravelAgencyWebServers
  • Availability Zones and subnets, select all 3 AZ* and subnets
  • In Default routing (forward to), select Create a target group
  • Select Update

DIY

  1. In the Auto Scaling Groups interface
  • View update results
  • Select TravelAgencyWebServers Auto Scaling Group
  • Select Details to see details

DIY

  1. In the EC2 interface
  • Select Security Groups
  • Select Create security group

DIY

  1. In the Create security group interface
  • Security group name, enter TravelAgencyLoadBalancer
  • In Decription, enter Allow access to the Travel Agency Load Balancer from the Internet
  • In VPC, select lab/TravelAgencyVpc
  • Select Add rule

DIY

  1. In the Create Security group interface
  • Inbound rules, select HTTP
  • Oubound rules, select HTTP
  • Select Create security group

DIY

  1. In the EC2 interface
  • Select Security Groups
  • Select TravelAgencyWebServer security group*
  • Select Actions
  • Select Edit inbound rules

DIY

  1. In the Edit inbound rules interface
  • Select Delete
  • Select Add rule

DIY

  1. In the Edit Inbound rules interface
  • Select HTTP
  • Source select Custom, select TravelAgencyLoadBalancer
  • Select Sae rules

DIY

  1. In the EC2 interface
  • Select Load Balancers
  • Select TravelAgencyWebServers-1 Load Balancer
  • Select Description to view description information

DIY

  1. In the Load Balancer interface
  • Select Edit security groups
  • Select TravelAgencyLoadBalancer security group
  • Uncheck TravelAgencyWebServer security group

DIY

  1. In the EC2 interface
  • Select Load Balancers
  • Select TravelAgencyWebServer-1 Load Balancer
  • In Description, view and copy DNS name

DIY

  1. Open a browser
  • Paste DNS name into the browser
  • Select Enter and see the interface

DIY

  1. In the browser
  • Follow the end of DNS name: /health
  • View results

DIY

  1. In the EC2’ interface
  • Select Target Groups
  • Select TravelAgencyWebServers target group
  • Select Health checks

DIY

  1. In the interface Edit health check settings
  • In Health check path, enter /health
  • Select Advanced health check settings

DIY

  1. In the Advanced health check settings interface
  • In Unhealthly threshold, enter 2
  • In Timeout, enter 2
  • In Interval, enter 5
  • Select Save changes

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServer Auto Scaling Group
  • In Network, see Subnet ID
  • Select Edit

DIY

  1. In the Edit TravelAgencyWebServers interface
  • In Availability Zones and subnets, select lab/TravelAgencyVpc/PrivateSubnet1

DIY

  1. In the EC2 interface
  • Select Instances
  • Select lab/TravelAgencyWebServers instance
  • Select Networking
  • View edited Subnet ID
  • Select Instance state
  • Select Terminate instance

DIY

  1. In the Terminate instance interface
  • Select Terminate

DIY

  1. In the Instances interface
  • Select refresh
  • Select lab/TravelAgencyWebServers instance
  • Select Networking
  • View Subnet ID

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling Group
  • View Activity history

DIY

  1. In the browser health check
  • Select Refresh
  • View results

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TraveAgencyWebServers
  • In Network, select Edit

DIY

  1. In the Edit TravelAgencyWebServers interface
  • In Availability Zones and sunets, select lab/TravelAgencyVpc/PrivateSubnet2
  • Select Update

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • View update results
  • Select TravelAgencyWebServers Auto Scaling group
  • Select Details to see details
  • In Group details select Edit

DIY

  1. In the Group size interface
  • Desired capacity, enter 2
  • Minimum capacity, enter 1
  • Maximum capacity, enter 2
  • Select Update

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravleAgencyWebServers Auto Scaling Group
  • View Activity history

DIY

  1. In the EC2 interface
  • Select Instance
  • Select lab/TravelAgencyWebServers
  • Select Networking
  • View Subnet ID

DIY

  1. In the browser health check
  • Select Refresh
  • View results

DIY

  1. In the *EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling group
  • In Network, see Subnet ID
  • Select Edit

DIY

  1. In the Edit TravelAgencyWebServers interface
  • In Availability Zones and subnets, select lab/TravelAgencyVpc/PrivateSubnet3

DIY

  1. Tron interface Edit TravelAgencyWebServers
  • In Network there are 3 subnets:

  • lab/TravelAgencyVpc/PrivateSubnet1

  • lab/TravelAgencyVpc/PrivateSubnet2

  • lab/TravelAgencyVpc/PrivateSubnet3

  • Select Update

DIY

  1. In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling Group
  • Select Details, see details Group details
  • Select Edit

DIY

  1. In the Group size interface
  • Desired capacity, enter 3
  • Minimum capacity, enter 1
  • Maximum capacity, enter 3
  • Select Update

DIY

  1. ​​In the EC2 interface
  • Select Auto Scaling Groups
  • Select TravelAgencyWebServers Auto Scaling Group
  • View Activity history

DIY

  1. In the EC2 interface
  • Select Instances
  • Select lab/TravelAgencyWebServers instance
  • Select Networking
  • View Subnet ID

DIY

  1. In the browser health check
  • Select Refresh
  • View results

DIY

  1. In the Auto Scaling Group interface
  • Select TravelAgencyWebServers Auto Scaling Group
  • Select Details
  • View details Group details

DIY

  1. In the EC2 interface
  • Select Load Balancers
  • Select TravelAgencyWebServers-1 Load Balancer
  • Select Description and view description information
  • Copy Name ALB
  • Copy Auto Scaling group name

DIY

  1. In the DIY interface
  • Paste TravelAgencyWebServers-1 into Your ALB name
  • Paste TravelAgencyWebSersers into Your Auto Scaling group name
  • Select VALIDATE

DIY

  1. In the DIY interface
  • In VALIDATION MESSAGE appears Success! All 3 Availability Zones are covered by instances behind a Load Balancer
  • Select EXIT to return to the city interface

DIY

  1. In the city interface
  • Select ASSIGNMENTS
  • Select COLLECT

DIY

  1. Select NEXT

DIY

  1. Select COLLECT

DIY

  1. Congratulations to the player receiving the reward