Skip to main content

AWS Firewall- Samurai Warriors

In MNCs, we have separate Network and Security teams – which is good by the way. They have the proper tool to block incoming or outgoing traffic. For this, they set up a firewall on their side which helps them establish a Network Control Centre.

But managing this firewall is not easy and cheap because you have to purchase a license and to maintain that you need SMEs for particular that firewall. So to overcome all these issues we now have a managed service that is AWS Firewall.

So what were the current Requirements that help me go deep-dive into this?

  1. We need to block some Public URLs for our egress traffic.

  2. We want to do so with a managed service.

  3. It should be quite easy to implement

  4. No Hustle and Bustle is required for setting and maintaining the firewall

  5. It should be a centralized Service. Should have control over your multiple accounts. Ex- It would be treated as Single Control Network for multi Accounts So, to fulfill all these requirements. The first fully managed service that came to my mind is the AWS firewall.


Basic Requirements:

  1. AWS Account

  2. Basic knowledge of the Creation of VPC and Subnets and EC2 and transit Gateway

  3. Please read the first Blog Transit Gateway Setup on AWS.


The Diagram has some basic terms:

  1. Hub VPC: It’s a VPC in which your transit gateway is residing

  2. Spoke VPC: It’s your VPC that has to be exposed to the firewall

  3. Availability Zones: It’s your isolated location in which you have made your VPC

  4. VPC: Virtual Private Cloud is like your data-center

  5. Public/Private subnet: Public are those which are exposed to Internet and Private are not exposed

  6. NAT/Internet gateway: They are just like your routers which help you to connect to the outer world


[ Good Read: What Is Data Science? ]


We will do implementation in 4 Steps:

First, we will set up Transit Gateway:

  1. Click on Create Transit GATEWAY: Select NAME > SELECT DESCRIPTION > CREATE TRANSIT GATEWAY

  2. Now CREATE two ROUTE TABLE :

  3. FIREWALL-ROUTE-TABLE

  4. SPOKE-ROUTE-TABLE

  5. Now Create a TGW attachment for the VPC which you want to peer

  6. If you want to peer VPC in the different account you just need to share that Transit gateway to a particular Account and create a new attachment from that account For more information refer to this blog transit gateway.


You can check more info about: AWS Firewall.
Location: United States

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Guide to Cloud Migration With DevOps

This successful adoption of cloud technologies is attributed to scalability, security, faster time to market, and team collaboration benefits it offers. With this number increasing rapidly among companies at all levels, organizations are  looking forward to the methods that help them: Eliminate platform complexities Reduce information leakage Minimize cloud operation costs To materialize these elements, organizations are actively turning to DevOps culture that helps them integrate development and operations processes to automate and optimize the complete software development lifecycle. In this blog post, we will discuss the step-by-step approach to cloud migration with DevOps. Steps to Perform Cloud Migration With DevOps Approach Automation, teamwork, and ongoing feedback are all facilitated by the DevOps culture in the cloud migration process. This translates into cloud environments that are continuously optimized to support your business goals and enable faster, more seamless mi...
Post a Comment
Read more

Containerization vs Virtualization: Explore the Difference!

  In today’s world, technology has become an integral part of our daily lives, and the way we work has been greatly revolutionized by the rise of cloud computing. One of the critical aspects of cloud computing is the ability to run applications and services in a virtualized environment. However, with the emergence of new technologies and trends, there are two popular approaches that have emerged, containerization and virtualization, and it can be confusing to understand the difference between the two. In this blog on Containerization vs Virtualization, we’ll explore what virtualization and containerization are, the key difference between virtualization and containerization, and the use cases they are best suited for. By the end of this article, you should have a better understanding of the two technologies and be able to make an informed decision on which one is right for your business needs. Here, we’ll discuss, –  What is Containerization? –  What is Virtualization? – B...
Post a Comment
Read more

Migration Of MS SQL From Azure VM To Amazon RDS

The MongoDB operator is a custom CRD-based operator inside Kubernetes to create, manage, and auto-heal MongoDB setup. It helps in providing different types of MongoDB setup on Kubernetes like-  standalone, replicated, and sharded.  There are quite amazing features we have introduced inside the operator and some are in-pipeline on which deployment is going on. Some of the MongoDB operator features are:- Standalone and replicated cluster setup Failover and recovery of MongoDB nodes Inbuilt monitoring support for Prometheus using MongoDB Exporter. Different Kubernetes-related best practices like:- Affinity, Pod Disruption Budget, Resource management, etc, are also part of it. Insightful and detailed monitoring dashboards for Grafana. Custom MongoDB configuration support. [Good Read:  Migration Of MS SQL From Azure VM To Amazon RDS  ] Other than this, there are a lot of features are in the backlog on which active development is happening. For example:- Backup and Restore...
Post a Comment
Read more