Create a Post
LostBoY
Advisor

NAT in Aws Checkpoint instance

Jump to solution

Hello,

I want to host a web server which is located behind a aws chexkpoint cluster but i am unable to figure outbhow the traffic from internet will hit the firewall vpc..i have elastic ip in that account which i have mapped with the web server via firewall nat.. But when i try to access it from internet there is no traffic on firewall

Any advice on what i am missing here.

Thanks

0 Kudos
1 Solution

Accepted Solutions
HeikoAnkenbrand
Champion
Champion

Hi @LostBoY,

1) Add a AWS route table to the cluster with the internal networks
2) Add default route to the internet on the gateway.
3) Create a NAT rule:
n1.JPG
4) Creat a access rule
r1.JPG5) Hide NAT for Web Server
h1.JPG
6) Check AWS security groups (NACL) for the Elastic IP. Traffic must be allowed from the internet to Check Point firewall (cluster).

 

View solution in original post

4 Replies
HeikoAnkenbrand
Champion
Champion

Hi @LostBoY,

1) Add a AWS route table to the cluster with the internal networks
2) Add default route to the internet on the gateway.
3) Create a NAT rule:
n1.JPG
4) Creat a access rule
r1.JPG5) Hide NAT for Web Server
h1.JPG
6) Check AWS security groups (NACL) for the Elastic IP. Traffic must be allowed from the internet to Check Point firewall (cluster).

 

View solution in original post

LostBoY
Advisor
Thanks for the reply. a couple of queries here.
1) can you please explain a bit more on point 1
2)I want to host a few webservers each with a dedicated IP.. so instead of hide behind gateway ..can i use hide behind ip address ?
0 Kudos
LostBoY
Advisor

What i cant figure out is .. if i have an EIP by which i want to access the web server via Firewall ..then how do i associate that EIP with Firewall. i mean the routing part ..how will the internet know that for this particular EIP it has to reach this Firewall

0 Kudos
Ryan_St__Germai
Collaborator

If you still need help with this.

ASS now allows you to assign routing tables to the internet gateway in your VPC. So what you do is create a new route table with destination of your internal networks and make the firewalls external interface the hop for these. You then assign the route to the internet gateway. Assign elastic ips like you normally would to the internal hosts. When packets come into your VPC the internet gateway will know to route to the FW instead of directly to your internal host since you created that ingress route table.

0 Kudos