15. route53 policies
"Hello, I'm Kiran Pawar, a passionate Cloud and Devops Engineer with a strong background in cloud automation, configuration, and deployment. My journey in the world of technology has been a thrilling adventure, where I've had the privilege to work with cutting-edge tools and practices.
🚀 As a DevOps Engineer:
I specialize in automating, configuring, and deploying instances in cloud environments and data centers. My expertise extends to DevOps, GitOps, CI/CD pipeline management, HashiCorp Terraform, and containerization. I'm proficient in AWS and Linux/Unix administration, ensuring robust infrastructure and application performance.
🔧 My Tech Stack:
Front-end skills: HTML, CSS, SCSS, Tailwind CSS, Bootstrap, React, Material-UI, JavaScript DevOps toolbox: GIT, OWASP,Nexus,Trivy, Github, Gitlab, Terraform, Ansible, Docker, Kubernetes, Helm, Jenkins, Prometheus, Grafana, Argo CD, AWS EKS.
🌐 My Cloud Expertise:
I have hands-on experience managing AWS services, including EC2, S3, EBS, VPC, ELB, RDS, IAM, Route53, and more.
🔒 Networking and Security:
My skills include managing networking concepts such as TCP/IP protocols, security policies, and subnet interfacing. I have a strong understanding of infrastructure and networking, covering topics like firewalls, IP addressing, DNS, and more.
💡 What Sets Me Apart:
I bring a positive attitude, a strong work ethic, and a collaborative spirit to every project. I'm a self-starter, a fast learner, and an effective team player with strong interpersonal skills. In addition to my DevOps skills, I've developed shell scripts (Bash) for automating tasks and have proficiency in Python scripting. My ability to communicate and manage projects, along with a track record of resolving client issues, adds value to every team I work with. If you're looking for a DevOps engineer who is also well-versed in front-end technologies, feel free to connect with me. Let's explore new possibilities and create exceptional technical solutions together!"
Step: 1 Create an instance. Step: 2 run below commands and make sure you are changing domain name accordingly and also make sure all your subdomains were recorded in route53, watch myvideo day 00 video if you have doubt.
Example my records for route53 policies ( cloudvishwakarma.in failover.cloudvishwakarma.in latency.cloudvishwakarma.in weighted.cloudvishwakarma.in geolocation.cloudvishwakarma.in www.cloudvishwakarma.in; ) step: 3 Once done create an AMI image for the same step: 4 Copy the current AMI image to AP-MUMBAI an deploy instance with it step: 5 You can follow the day15 video accordingly to achieve the task
Routing Policies with Route53
Route53 Explanation:
Hosting a website on AWS EC2 instances requires ensuring constant availability for users, even if some instances fail. Route 53 employs health checks to monitor instance health and automatically directs traffic away from unhealthy instances, ensuring seamless user experience.
Route53 Routing Policies:
Latency: Route traffic to the AWS region with the lowest latency, enhancing application performance by minimizing response time for users.
Weighted: Ideal for load balancing traffic between different versions of a website, gradually rolling out new features to a percentage of users.
Failover: Automatically redirects traffic to a secondary server if the primary server fails.
Geo-Location: Allows routing traffic based on the geographic location of users, optimizing performance and compliance.
Steps:
Deploy EC2 instances and create necessary certificates, then create an AMI image.
Deploy instances with the AMI in multiple regions.
Configure failover records with health checks for each server.
Set up primary failover records, directing traffic to the primary instance and failing over to secondary instances if necessary.
Verify failover functionality by editing files on instances and observing traffic redirection.
Monitor traffic using cloud shell and demonstrate health checks.
Test latency by creating records and changing values to observe regional routing.
Implement weighted routing by distributing traffic between regions.
Showcase Route53 resolver capabilities.
Interview Question:
Q: Could you please identify global AWS services?
A: Route53 and IAM are global services. Although some may consider S3 as global, it operates within specific regions. For instance, when configuring VPC endpoints, specific regions like NV might be requested due to service availability constraints.
