- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Policy not matching AWS Data Center Objects
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Policy not matching AWS Data Center Objects
Hi CheckMates,
I am experiencing an issue where one set of gateways is not matching access rules where AWS DataCenter objects are used but another set of gateways with a separate policy are matching traffic and permitting against AWS DataCenter objects.
I have a AWS deployment where an Cross AZ Cluster, Auto Scaled Gateways and EC2 Manager all reside in separate VPCs and are peered via transit gateway. Identity Awareness is configured as per admin guide yet only one set of gateways (autoscaled) are matching traffic for the objects. The clustered gateways fail to permit traffic where AWS DC objects are used - if i replace the AWS object with a standard address object the traffic is permitted.
Can anyone advise on how I can troubleshoot/debug this?
- Labels:
-
AWS
-
CloudGuard
-
Data Center Object
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, check :
# In version R81.20 with Jumbo HFA Take 26 and higher:
# Send Data Center updates from the CloudGuard Controller to the main IP address of Active member
# on the Management Plane instead of the cluster VIP address on the Data Plane
updateClusterMemberAndNotVip=true
I think this can help you here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Look in $FWDIR/log/cloud_proxy.elg on the mgmt server - do you see updates being sent to the cluster gw?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Gil_Sudai
Yes i can see that it is failing to send the updates to the clusters EIP. Is it possible for these updates to go to the private addresses of the Cross AZ cluster and not the EIP? I do not wish for the communication between manager and gateways to go via the internet.
Thanks
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
what IP address is configured on the Cluster object ? is it the Cluster EIP ?
updates are send to the GW/Cluster object IP address.
you can change it , check sk60701
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes the IP in the cluster object is the public EIP. Am i able to change it in the database for one or both of the cross-az gateways? I would like this communication to happen privately not via public internet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, check :
# In version R81.20 with Jumbo HFA Take 26 and higher:
# Send Data Center updates from the CloudGuard Controller to the main IP address of Active member
# on the Management Plane instead of the cluster VIP address on the Data Plane
updateClusterMemberAndNotVip=true
I think this can help you here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version is your mgmt server?
If R81.20 , look for PRJ-43926 in https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/R81.20/R81.20-List-of-all-Resolved-Issues.htm?... .
From take 26 you can update the CloudGuard Controller config option to push the updated to the cluster member and not to the VIP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you both for you input. I am running R81.20 for management. I will check the above inline with what you've mentioned/referenced and see if I can resolve.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its working for me now. Added the config line to vsec.conf and upgraded to the jumbo 53 anyway.
Thank you again!