AWS

Vanakkam all Check out the new pricing details for IPv4 . Intention is to have the users move from IPv4 to IPv6 AWS : New charge for public IPv4 addresses. Effective February 1, 2024 there will be a charge of $0.005 per IP per hour for all public IPv4 addresses, whether attached to a service or not This change applies to all AWS services including Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service (RDS) database instances, Amazon Elastic Kubernetes Service (EKS) nodes, and other AWS services that can have a public IPv4 address allocated and attached, in all AWS regions Monitor using Public IP Insights In order to make it easier to monitor, analyze, and audit your use of public IPv4 addresses, use Public IP Insights, a new feature of Amazon VPC IP Address Manager that is available to you at no cost. Amazon VPC IP Address Manager Public IP Insights is free, which is running on Amazon VPC IP address Manager. But what about VPC IP address Manager. In fact, you are charged for every public IP address that is assigned to something that it manages, according to the VPC Address Manager documentation Amazon BYOIP You will not be charged for IP addresses that you own and bring to AWS using Amazon BYOIP (Bring Your Own IP address) Optimize Track and monitor your idle and in-use public IPv4 addresses and identify use of optimization. Detailed note on how to optimize the usage in covered in amazon documentation Note : Remove your unattached IP addresses to save cost Google Cloud Platform ( GCP ) Static and ephemeral IP addresses in use on standard VM instances will be charged at $0.005/hr from February 1, 2024. Static and ephemeral IP addresses in use on preemptible and Spot VM instances will be charged at $0.0025/hr from February 1, 2024. Static and ephemeral IP addresses in use on Cloud NAT Gateways will be charged $0.005/hr from February 1, 2024

Ponniyin Selvan is a Tamil historical novel written by Kalki Krishnamurthy, while AWS is a cloud computing service provided by Amazon. However, if we were to draw comparisons based on certain characteristics, we could say that some Ponniyan Selvan characters can be compared to AWS tools as follows Aditha Karikalan – Amazon EC2: Aditha Karikalan was a great warrior and leader, and he had a vast army at his disposal. Similarly, Amazon EC2 is a powerful and scalable cloud computing service that allows users to launch and manage virtual servers. Vandiyathevan – Amazon S3: Vandiyathevan was a messenger who travelled long distances to deliver messages to different people. Similarly, Amazon S3 is a simple storage service that allows users to store and retrieve data from anywhere on the web. Nandini – Amazon Rekognition: Nandini was a seductive and charming character who had a way of manipulating people to get what she wanted. Similarly, Amazon Rekognition is a powerful image and video analysis tool that uses machine learning to recognize faces, objects, and scenes. Arulmozhi Varman – Amazon DynamoDB: Arulmozhi Varman was a wise and intelligent ruler who had a deep understanding of his kingdom and its people. Similarly, Amazon DynamoDB is a fast and flexible NoSQL database that can handle large amounts of data with ease. Pazhuvettarayar – AWS CloudTrail: Pazhuvettarayar was a shrewd and cunning politician who was always trying to stay one step ahead of his enemies. Similarly, AWS CloudTrail is a service that provides a detailed record of user activity and API calls in the AWS environment, making it easier for users to identify and troubleshoot issues. Poonguzhali – AWS Lambda: Poonguzhali was a resourceful and clever character who was able to find solutions to difficult problems. Similarly, AWS Lambda is a serverless computing service that allows users to run their code without having to worry about servers or infrastructure. Kandanmaran – AWS Security Hub: Kandanmaran was a vigilant and cautious character who was always on the lookout for threats to his kingdom. Similarly, AWS Security Hub is a security service that helps users manage and prioritize their security alerts and findings across their AWS accounts, making it easier to identify and remediate security risks Kundavai – Amazon CloudFront: Kundavai was a thoughtful and strategic thinker who was always looking for ways to improve the well-being of her people. Similarly, Amazon CloudFront is a content delivery network that helps users deliver their content faster to their customers by caching it at edge locations around the world. Azhwarkadiyan – AWS Elastic Beanstalk: Azhwarkadiyan was a loyal and dependable friend who was always ready to lend a helping hand. Similarly, AWS Elastic Beanstalk is a service that makes it easy for users to deploy, manage, and scale their web applications without having to worry about the underlying infrastructure. These comparisons are just for illustrative purposes, and it’s important to note that they are not meant to be taken too seriously. Both Ponniyan Selvan and AWS are complex entities with their own unique characteristics and features, and they should be appreciated on their own terms

Problem Statement Amazon Web Services (AWS) offers several types of load balancers to distribute incoming network traffic across multiple resources like Amazon EC2 instances or containers. While we design Application and it’s Infrastructure components, we come across a stage where we need to Decide about the Load balancer to be used.   Here’s an easy explanation of four common popular types:   Application Load Balancer (ALB): Think of ALB as a smart traffic cop for web applications. – Can easily implement a Web Application Firewall WAF to protect against exploits. It operates at the application layer (Layer 7) and can route traffic based on content in the request, like URL paths or headers. Ideal for modern web applications, microservices, and API gateways. Btw, What is Layer 7? There are Seven Layers in the OSI Model (Open Systems Interconnection). Layer 7 is the topmost Application Layer and directly interacts with User applications. It includes HTTP, FTP and SMTP Protocols. Network Load Balancer (NLB): NLB is like a high-speed traffic router for TCP and UDP traffic. It operates at the transport layer (Layer 4) and is highly scalable and performs well with ultra-low latency. Suited for handling massive amounts of connections or when you need to forward raw network packets. Layer 4 – Wait, it’s again another Layer in OSI Model? Yes, it is called a Transport Layer. It ensures end-to-end communication and data integrity between two devices on a Network. It includes TCP and UDP Protocols. Classic Load Balancer (CLB): CLB is the older version and offers basic load-balancing capabilities. It balances traffic at both Layer 4 (TCP/UDP) and Layer 7 (HTTP/HTTPS). While still available, it’s generally recommended to use ALB or NLB for more advanced features and better performance. Gateway Load Balancer (GWLB): It’s primarily used for scenarios where you need to distribute traffic across multiple network appliances, such as firewalls, intrusion detection systems (IDS), and other security or networking devices. GWLB is highly available, with redundancy built-in across multiple Availability Zones (AZs) to ensure fault tolerance. It helps improve network security by allowing you to integrate various security appliances and inspect traffic as it passes through. Just like other load balancers in AWS, GWLB uses target groups to direct traffic to specific resources. In this case, the resources are network appliances. Suppose you have multiple security appliances, like firewalls and intrusion detection systems, in your network architecture to inspect incoming and outgoing traffic for threats. By placing a GWLB in front of these appliances, you can ensure that all traffic is evenly distributed across the security devices, helping you scale and secure your network effectively. Remember, the choice of load balancer depends on your specific application’s needs. ALB is a popular choice for most modern web applications, NLB for high performance and scalability, and CLB may be used for simple scenarios.   Summary: Hope you Now know about the Load Balancers and wait for our Blog if you got lost by the terms referred to here as Protocols.