AWS, Engineering, Network, Solving Problems
Organized and dependable candidate successful at managing multiple priorities with a positive attitude. Willingness to take on added responsibilities to meet team goals.
Organized and dependable candidate successful at managing multiple priorities with a positive attitude. Willingness to take on added responsibilities to meet team goals.
Effortless Request Management: Simplifying Operations with Automated Slack Notifications.
Fostering Effective Communication: Bridging Gaps for Successful Projects.
Creating a Study Group: Fostering Deeper Understanding in Backend Engineering and Strengthening Intimacy Among Colleagues.
Committed to providing continuous customer service excellence
Project Management Abilities
undefinedAWS, Engineering, Network, Solving Problems
I have developed a keen interest in AWS services and have been diligently studying them. Recently, I learned about the topic that EC2 is not actually inside a subnet. Although I configured EC2 with settings like subnets, security groups, Public IP, and Private IP through the console, I couldn't grasp the architecture clearly.
However, this presented an opportunity for me to gain a thorough understanding of the architecture. I discovered that EC2 resides in an Availability Zone (AZ) and that ENI (Elastic Network Interface) is located in the Private Subnet or Public Subnet. As a result, EC2 can handle traffic through the Public Subnet and the Private Subnet respectively, because ENI is mapped to specific subnets (Private or Public) alongside EC2.
This led me to realize that EC2 might be mistakenly perceived as residing within a public subnet, but in reality, it is not the case. The bottom line is that EC2 exists within an Availability Zone.