- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- AWS CloudGuard IaaS: Change external interface top...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AWS CloudGuard IaaS: Change external interface topology via cli/bash
Hi.
I have a deployment of a R80.40 AMI, dual homed, with eth0 on a private subnet and eth1 on a public subnet.
On the cloud-init script, I remove the default route from eth0, add it to eth1, and add a static route for 10.0.0.0/8 on eht0.
When Management server tries to auto-configure it via tagging it is failing saying that "all the interfaces have a EXTERNAL policy, that is not allowed".
I confirm that if I go through SmartConsole, and change the topology of eth0 to Internal the error disappears.
The problem that I have is that I want to script this change using cli, or know how I could avoid the problem in a first instance.
Any suggestions ?
Thanks in advance
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You've asked this question a second time here: https://community.checkpoint.com/t5/CloudGuard-IaaS/Multi-homed-EC2-How-to-force-topology-for-auto-p...
As that thread has discussion, I am going to lock this thread.
As that thread has discussion, I am going to lock this thread.