We already created a EC2 server setup and configured and uses simple routing policy. We deleted the A record that specified simple routing. We will create one with weighted policy now. In this policy, requests for your domain that come to Route 53 will be forwarded to different regions or even different ELBs based on weight specified.
We will create an EC2 server setup and configure and use simple routing policy in first part of this lab. For continuity and incurring less cost, it is better you do all the five parts of this lab together.
Login to AWS console and go to Route 53.
Amazon Route 53 is a DNS web service that effectively connects user requests to infrastructure running in AWS such as EC2 instances, ELB load balancers, or S3 buckets. It can also be used to route users to infrastructure outside of AWS.
Route 53 is designed to be extremely reliable, highly available, scalable and cost effective. Amazon Route 53 is fully compliant with IPv6 as well.
This is a continuation of the previous VPC lab.
Steps:
Go to VPC Dashboard and click on Network ACLs tab.
Verify current Network ACLs and all inbound and outbound rules.
Create New Network ACL
This is a continuation to the lab ‘Creating and Using Amazon VPC – Part 1’. We will use NAT instance and NAT gateway to allow the private server to access internet in a secure way.
Steps:
Launch a new EC2 instance as NAT instance
We will create a VPC with a public and private subnet and try accessing them both from internet. We will be creating the VPC without using the Wizard available.
Steps:
Log in to the AWS console and go to VPC dashboard.
Go to ‘Your VPCs’ and click on ‘Create VPC’
These are only the defaults. Many of these can be changed by contacting AWS or other ways. Refer to the reference link for details.
Flow logs per single network interface, single subnet, or single VPC in a region = 2
VPCs per region = 5
Amazon VPC provides following features to increase and monitor the security for your VPC:
Security groups - Act as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic at the instance level.
Network access control lists (ACLs) - Act as a firewall for associated subnets, controlling both inbound and outbound traffic at the subnet level.
NAT is a method of remapping one IP address space into another. Advanced NAT implementations feature IP masquerading, which allows to share one Internet-routable IP address of a NAT gateway for an entire private network. In AWS, you can either use a NAT instance or a NAT gateway.
Please first use the contact form or facebook page messaging to connect.
Offline ContactComplete the form below, and we'll send you an e-mail every now and again with all the latest news.
CloudMaterials is my blog to share notes and learning materials on Cloud and Data Analytics. My current focus is on Microsoft Azure and Amazon Web Services (AWS).
I like to write and I try to document what I learn to share with others. I believe that knowledge is useless unless you share it; the more you share, the more you learn.
Recent comments