AWS - Understanding Security Group

-

 

In this post will go in detail on a simple ALB to EC2 setup.


I am configuring NodeJS on my EC2 instance.

[root@ip-172-31-9-46 ~]# yum install npm

[root@ip-172-31-9-46 ~]# npm install express


Starting the application using the below command.

[root@ip-172-31-9-46 ~]# node app.js

App1 is listening on port 3000

App2 is listening on port 4000



Now, I configured a target group:

In the target group we must give the application port and health check port.




NOTE: We cannot mention any security group under Target group.

Next, I am going to create a ALB.



Our ALB listens on port 80. So the ABL DNS/welcome should route the traffic to backend machine.

Eg: http:// demo-alb-123456.us-east-1.elb.amazonaws.com/welcome

Now, our EC2 instance at the backend should accept traffic from ALB on port 3000/4000.

Even though ALB has an IP address range which is dynamic, so create a security group based on IP is not the right solution.

Hence, we will create a security group and attach to ALB. This security group will accept all incoming traffic from its own security group IP. Like A calling A. But the idea is to make the load balancer source security group as A (sg-099c50cd040c70f6b)


Let’s attach this to the ALB.


Launch_wizard_1 accepts traffic on port 80 from outside.

Finally, we create a security group at the EC2 instance layer to accept any incoming traffic on port 3000/4000 from the source security group sg-099c50cd040c70f6b which is my load balancer.




Our target group is healthy.





Comments

Post a Comment

Popular posts from this blog

SRE/DevOps Syllabus

-
Image
  DEVOPS/SRE Principles. Git What is Git? Architecture of Git. Working principle of Git. Create and cloning a repo. Version control branching. Version control commit. Version control managing workflows. Git hooks. Git Reflog. Git Stash. Git Cherry Picking. Undoing changes in different states of Git. Git based terraform template management. AWS CI/CD SDLC Automation. Code Commit. Code Build. Code Deployment. Code Pipeline. Elastic Beankstalk. Code Artifact. CodeGuru. Terraform Terraform Basics. Terraform State. Working with Terraform. Terraform with AWS. Remote State. Terraform Provisioners. Terraform Import, Tainting and Debugging. Terraform Modules. Terraform Functions and Conditional Expressions. Automation using Python - AWS AWS lambda. Automating EC2 with Lambda. Automating S3 with Lambda. Automating VPC with Lambda. Cost optimization with Lambda. SNS,SQS and SES with Python. Managing and Automating AWS Security with Python. Kubernetes - CKAD Application Developer. Kubernetes A...
Read more

AWS Code Commit - CI/CD Series Part 1

-
Image
  This is a multi-part series to show how to implement a CI/CD pipeline in AWS. In this post, We will see how to use AWS Code Commit. AWS CodeCommit is a fully managed source control service that allows you to store and manage your code securely in the cloud.  It provides a private Git repository for your code and supports all Git commands and workflows. CodeCommit also integrates with other AWS services like AWS CodePipeline and AWS CodeBuild, allowing you to automate your entire software release process. This can help you streamline your development workflows and improve the overall efficiency of your team. I created a repo from AWS CodeCommit -> Create Repository. And I begin with cloning the repo locally. So that I can make changes and push it. To clone the repo click on "HTTPS" under Clone URL. I make changes to index.html file. Now push it to AWS CodeCommit. Let’s verify the changes in AWS Code commit. Changes are reflected in AWS CodeCommit. We are done with Part ...
Read more

Docker - Preventing IP overlapping

-
Image
  What is IP address overlapping? When the container IP address overlaps with another IP external, then the application running on the container is not accessible from outside due to the IP address overlapping.  NOTE: This IP address overlapping can happen on the bridge interface IP or docker container IP. Let's see how to address this IP overlapping issue on the bridge interface. I already have a running container.  root@demo:~# docker run -d --name web --network mynet1 nginx:alpine 268647e11011d513d2357ce1c81e0f48787038a83d01d028d31a5b29dbdb885b root@demo:~# docker container ls CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES 268647e11011   nginx:alpine   "/docker-entrypoint.…"   4 seconds ago   Up 3 seconds   80/tcp  ...
Read more