Understanding AWS VPC Security and Route 53: Learning AWS for 30 Days. || Day 5 &6

Introduction

Here in today's blog, we will look after VPC security like NACL, and Security Group and we move on to another topic i.e. Route 53. Here we will look at how VPC security Works and how DNS resolving happen. This blog is part of a 30-day AWS Journey where we will look after the aws services and this blog is for day 5 and day 6 learning.

VPC Security

✅Virtual Private Cloud (Amazon VPC) allows us to create logically isolated servers in AWS and give us complete control over our virtual network environment, including IP address range selection, creation of subnets, and configuration of route tables and network gateways.

✅Security is the Shared responsibility between both AWS and the organization.

✅The Security group is applied on an Instance Level whereas NACL is on Subnetes Level.
We can allow and deny the traffic flowing in and out of NACL whereas We can only set rules for Allowing the Traffic in the Security Group.

✅NACL is important in case any mistake is done at the Instance level in allowing the traffic the NACL helps us to block that traffic as NACL Configuration is applied at Whole Subnet.

We will look after the practical implementation of VPC on day 7.

Route 53

Amazon Route 53 is a Domain Name System (DNS) web service. Route 53 performs three main functions in any combination: domain registration, DNS routing, and health checking.

DNS resolves the load balancer IP Address.

DNS not only resolves the IP Address But also helps in health Checking.

When a Health Check detects that a resource is not healthy, we can set up Amazon Route 53 to automatically route traffic away from that resource to healthier ones. This can help ensure that our users are directed to functional resources and reduce the impact of outages or failures.