Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global protect behavior in Auto-scale mode #33

Closed
aymanelbacha opened this issue Sep 2, 2024 · 2 comments
Closed

Global protect behavior in Auto-scale mode #33

aymanelbacha opened this issue Sep 2, 2024 · 2 comments
Assignees

Comments

@aymanelbacha
Copy link

We're looking to have Global protect enabled for A/A HA mode in front of an ALB, is it recommended.
what will be the behavior if autoscaled, any reference documents to be shared for such configuration

@horiagunica
Copy link
Contributor

Hi @aymanelbacha !

IPSec and GP solutions in the public cloud are a bit more tricky due to the asymmetric routing issues. High level - if you want to have GP - you can do that with more or less any type of deployment (A/P, standalone, autoscale, etc.) - as long as you SNAT the traffic once it leaves the firewall towards your trust/protected VPC(s). That way - you can ensure the symmetric routing . In order for traffic to reach your FWs you would use a public LB - or you can even use an individual PIP on each firewall outside/untrust interfaces and configure your GP Portal to serve both FWs as GP gateways.

If you do NOT want to SNAT - then the issue with asymmetric routing appears as you will need to have a reserved individual subnet for each of your firewalls - dedicated per firewall. This can become tricky when using auto-scale since they would need to have that information automatically configured at bootstrapping. If you would require some additional help in this case - I recommend you reach out to your local PANW contact or visit https://www.paloaltonetworks.com/company/contact-sales .

I hope that clears up the scenario a bit!

@horiagunica horiagunica self-assigned this Sep 12, 2024
@migara
Copy link
Member

migara commented Sep 26, 2024

@aymanelbacha closing this issue for the moment

@migara migara closed this as completed Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants