AWS Lab Manual

Lab Manual

AWS Fundamentals

Objectives of this Lab Manual This lab manual is designed to provide practical knowledge to learners to solve a real-time work related assignment You will be given a problem and it’s descriptions. You are supposed to write down the steps to resolve the problem and submit the answer on a Google Sheet. A model answer will be provided at the end.

Problem What will you do? • Create and activate a new AWS Account

Model Answer What should you do? 1. Sign up using your email address 2. Add your contact information 3. Add a payment method 4. Verify your phone number 5. Choose an AWS Support plan 6. Wait for account activation 7. Troubleshooting delays in the account activation 8. Improving the security of your AWS account 9. Get Your Account Ready

Problem What will you do? • Create your own Virtual Private Cloud (VPC)

Model Answer What should you do? 1. Sign in to the AWS Management Console. 2. Click on the VPC service under Networking and Content Delivery. 3. Click on the \"Your VPCs\" appearing on the left side of the console. 4. Click on the Create VPC to create your own custom VPC. 5. Fill in the details to create a custom VPC. Where, Name tag: It is the name of the VPC that you give to your VPC. IPv4 CIDR block: Make this address block as big as possible. For example,10.0.0.0/16. IPv6 CIDR block: We can also provide IPv6 CIDR block. Tenancy: We make it as Default. 6. The below figure shows that VPC has been created. 7. Once done, click on the Create button to create the subnet.

Problem What will you do? • Create an Amazon VPC endpoint.

Model Answer What should you do? 1. Specify the Amazon VPC. 1. Specify the service. A service is identified by a prefix list of the form com.amazonaws. <region>.<service>. 1. Specify the policy. You can allow full access or create a custom policy. This policy can be changed at any time. 1. Specify the route tables. A route will be added to each specified route table, which will state the service as the destination and the endpoint as the target.

Problem What will you do? • Set up a VPC peering in Amazon AWS

Model Answer What should you do? 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/. 2. In the navigation pane, choose Peering Connections, Create Peering Connection. 3. Configure the following information, and choose Create Peering Connection when you are done: • Peering connection name tag: You can optionally name your VPC peering connection. • VPC (Requester): Select the VPC in your account with which you want to create the VPC peering connection. • Under Select another VPC to peer with: Ensure My account is selected, and select another of your VPCs. • Choose Add tag and do the following: • For Key, enter the key name. • For Value, enter the key value. • [Remove a tag] Choose the Delete button (\"X\") to the right of the tag’s Key and Value. 4. In the confirmation dialog box, choose OK. 5. Select the VPC peering connection that you've created, and choose Actions, Accept Request.

Problem What will you do? • Configure load balancer in AWS

Model Answer What should you do? 1. Launch the two instances on AWS management console named InstanceA and InstanceB. Go to services and select load balancer. 2. Click on create load balancer 3. Select Application Load Balancer and click on create. 4. Here you are required to configure the load balancer. Write the name of the load balancer. Choose the scheme as internet facing. 5. Add at least 2 availability zones. Select us-east-1a and us-east- 1b 6. We don’t need to do anything here. Click on Next: Configure Security Groups 7. Select the default security group. Click on Next: Configure Routing 8. Choose the name of the target-group to be my-target-group. Click on Next: Register Targets 9. Choose the instanceA and instanceB and click on Add to registered. Click on Next : Review. 10. Click on the create button to finalize our configuration 11. Congratulations!! You have successfully created load balancer. Click on close.

Problem What will you do? • Create an Internet-facing Load Balancer in a VPC

Model Answer What should you do? 1. Click Services > Load Balancers. 2. Click Create. The CREATE LOAD BALANCER dialog box appears. 3. In the Load Balancer Name field, type a name for the load balancer. 4. This name must be unique for the whole Region and follow the domain names rules. 5. It must follow domain name rules. It can contain up to 32 alphanumeric characters. 6. From the VPC list, select the VPC in which you want to create the load balancer. The Availability Zone list is deactivated. 7. From the Scheme list, select internet-facing. 8. From the Subnet list, select the subnet for your back-end instances. 9. From the Security Group(s) list, select one or more security groups to associate with the load balancer. 10. Click Create to validate. The load balancer is created and appears on the Load Balancers page.

Problem What will you do? • Register Domain Name in AWS with Route 53

Model Answer What should you do? 1. Obtain a Static URL a. Open the Elastic IPs part of the EC2 console in a new window and click Allocate New Address. b. Set EIP used in: to VPC and click Yes, Allocate c. Note your new IP address and click Close. d. Select the new IP address in the Elastic IP column. Press the Actions button and choose the Associate Address option. e. Click in the Instance text box and choose the option that has your instance name. f. Make a note of your new IP address in the Elastic IP column. g. Verify that your new Elastic IP address is working by typing it into your web browser. 2. Register a Domain Name 3. Step 3: Configure DNS

Problem What will you do? • Create a public hosted zone in AWS Route 53

Model Answer What should you do? 1. Sign in to the AWS Management Console and open the Route 53 console at https://console.aws.amazon.com/route53/. 2. If you're new to Route 53, choose Get started under DNS management. 3. If you're already using Route 53, choose Hosted zones in the navigation pane. 4. Choose Create hosted zone. 5. In the Create Hosted Zone pane, enter the name of the domain that you want to route traffic for. You can also optionally enter a comment. 6. For information about how to specify characters other than a-z, 0-9, and - (hyphen) and how to specify internationalized domain names, see DNS domain name format. 7. For Type, accept the default value of Public Hosted Zone. 8. Choose Create. 9. Create records that specify how you want to route traffic for the domain and sub domains.

Problem What will you do? • Create a public hosted zone in AWS Route 53

Model Answer What should you do? 1. For each VPC that you want to associate with the Route 53 hosted zone, change the following VPC settings to true: a. enableDnsHostnames b. enableDnsSupport 2. Sign in to the AWS Management Console and open the Route 53 console at https://console.aws.amazon.com/route53/. 3. If you're new to Route 53, choose Get started 4. If you're already using Route 53, choose Hosted zones in the navigation pane. 5. Choose Create hosted zone. 6. n the Create private hosted zone pane, enter a domain name and, optionally, a comment. 7. For information about how to specify characters other than a-z, 0-9, and - (hyphen) and how to specify internationalized domain names, see DNS domain name format. 8. In the Type list, choose Private hosted zone. 9. In the VPC ID list, choose the VPC that you want to associate with the hosted zone. 10. Choose Create hosted zone.

Problem What will you do? • Configure CloudTrail in the AWS Console

Model Answer What should you do? 1. Create a Trail. 2. Configure your trail to apply to all regions. 3. Choose events to log 4. Configure logs to be stored on S3 and enable log file validation. 5. Configure CloudWatch Alarms for Security and Network related API Activity

Problem What will you do? • Create CloudWatch alarms to Monitor Amazon EC Instances & EBS.

Model Answer What should you do? 1. Click on Create Alarm. 2. Click on Select Metric and type the name of the metric into the search box. 3. Choose the metric for the instance you’re going to monitor (under EC2 > Per-Instance Metrics) and look at a 1-week graph to determine what your baselines are. Click Select Metric. 4. Name and describe your alarm. 5. Configure your thresholds. You can use the thresholds described earlier in this article for each metric. 6. Choose what to do when data is missing 7. Set up notifications for the alarm. 8. Click Create Alarm.

Problem What will you do? • Create CloudWatch alarms to Monitor the Elastic Load Balancer

Model Answer What should you do? 1. Click on Create Alarm. 2. Click on Select Metric and type the name of the metric into the search box. 3. Name and describe your alarm. 4. Configure your thresholds. You can use the thresholds described earlier in this article for each metric. 5. Choose what to do when data is missing 6. Set up notifications for the alarm. 7. Click Create Alarm.

Problem What will you do? • Create CloudWatch alarms to Monitor the RDS

Model Answer What should you do? 1. Click on Create Alarm. 2. Click on Select Metric and type the name of the metric into the search box. 3. Choose the metric for the database you’re going to monitor (which you can find in the tile labeled Per-Database Metrics) and look at a 1 week graph to determine what your baselines are. Click Select Metric. 4. Name and describe your alarm.

What have 01 Created and activated a new AWS Account we learned… 02 Created our own Virtual Private Cloud (VPC) 03 Created an Amazon VPC endpoint. 04 Completed the set up of VPC peering in Amazon AWS 05 Configured load balancer in AWS 06 Created an Internet-facing Load Balancer in a VPC

What have 07 Created an Internet-facing Load Balancer in a VPC we learned… 08 Registered Domain Name in AWS with Route 53 09 Created a public hosted zone in AWS Route 53 10 Created a public hosted zone in AWS Route 53 11 Created a public hosted zone in AWS Route 53 12 Configured CloudTrail in the AWS Console

What have 13 Created CloudWatch alarms to Monitor Amazon EC we learned… Instances & EBS. 14 Created CloudWatch alarms to Monitor the Elastic Load Balancer 15 Created CloudWatch alarms to Monitor the Elastic Load Balancer

Thank You!