I faced a scenario where in there is a requirement to allow public
access for multiple web servers through Fortigate in AWS. With the help
of secondary IP's & associating elastic IP's to it this can be achieved,
however there is a limitation on AWS a...
I have a scenario where there are two subnets in AWS, a public subnet
and private subnet. Most of the public subnet have web servers running
with multiple public IP's to access from the internet. Now I would like
to deploy the Fortigate Firewall in t...
I see this as Fortigate Virtual server load balancing concept, by using
this I can only do load balancing to multiple real servers or single
server. To accomplish this, we need to create multiple secondary IP's on
WAN interface and then do a double N...
Can you elaborate more on this ? One thing I would like to say is no
changes can be done in existing servers or add new server. Looking for a
solution from network/cloud perspective as a work around.
Thank you everyone for your inputs, I figured it out. Understood in
other way around, all I need to do is create secondary IP's (as many as
required) for Fortigate WAN subnet, then map an elastic IP. Followed by
mapping WAN and LAN private IP VIP's a...
Hello mwissa/Graham, I understand what you are saying; but it didn't
work out. Let me put it in this way for example. VPC1: CIDR
192.168.0.0/16Public Subnet: 192.168.0.0/24, FGT WAN interface IP:
192.168.0.50 (public IP 203.10.10.10)Web servers alrea...
