- CheckMates
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Autoprovision of Rules in AWS
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Autoprovision of Rules in AWS
I have question about how the autoprovision of rules is processed in AWS when an internal lb is tagged. I noticed on the sms and from the cme log that all previously auto generated rules are first deleted then re-added before policy installation. Why is it implemented this way? Wouldn’t there be potential issues when the rulebase becomes very large? Also, it could potentially cause an outage. I recently encountered a scenario where the connectivity between my sms and gateway was down momentarily; the gateway was still running and functional. The cme service proceeded to remove the rules and push policy. Since the connectivity was down the policy installation failed. However if the connectivity were to be restored before policy push the gateways would receive a policy with no rules.
-
ACI
1 -
API
1 -
architecture
4 -
Automation
3 -
Automation and APIs
1 -
Aviatrix
1 -
AWS
6 -
Azure
5 -
Azure DevOps
1 -
bash
1 -
CDT
1 -
cisco
1 -
Cisco ACI
1 -
Cloud
3 -
Cloud - Automation - Orchestration
1 -
Cloud network security
2 -
Cloud Security
1 -
cloudappsecurity
1 -
CloudGuard
4 -
CloudGuard IaaS
4 -
cloudwatch
1 -
Cluster
1 -
ClusterXL
1 -
deployment
2 -
DevSecOps
1 -
DHCP
1 -
DirectConnect
1 -
firewall
1 -
Gaia
1 -
IaC
1 -
identity
1 -
loadbalancer
1 -
MDS 80.40
1 -
multi cloud
1 -
NAT
1 -
NDR
1 -
networking
1 -
next generation firewall
1 -
NSX-T
2 -
private
1 -
public
1 -
R81
1 -
R81.10
1 -
reference
1 -
script
1 -
Site to Site VPN
1 -
Smart Console
1 -
Structura.io
1 -
technical
1 -
Terraform
3 -
TGW
1 -
VMSS
1 -
vsec_lic_cli
1
- « Previous
- Next »