shield-enabled filter not working for Elastic IPs
See original GitHub issueHello,
A policy like this will return a list of all EIPs in the account instead of just the ones without shield protection enabled.
policies:
- name: check-eip-shield
resource: network-addr
filters:
- type: shield-enabled
state: false
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Troubleshoot Elastic IP addresses on EC2 instances - AWS
I'm receiving errors when allocating or releasing an Elastic IP address associated with my Amazon Elastic Compute Cloud (Amazon EC2) ...
Read more >aws.elastic-ip — Cloud Custodian documentation
A resource matches the filter if a diff exists between the current resource and the selected revision. Utilizes config as a resource revision...
Read more >Unassociated Elastic IP Addresses | Trend Micro
The filtering process should return the Elastic IPs that are not currently associated with any running EC2 instances or Elastic Network Interfaces (ENIs)....
Read more >How can I select all elastic IPs that are not assigned to an EC2 ...
I know that the --query option uses JMESPath to filter results, but I have no idea how to tell it to return me...
Read more >Restricting connections with IP filtering | Elasticsearch Guide ...
If a node's IP address is on the blacklist, the Elasticsearch security features allow the connection to Elasticsearch but it is be dropped...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@thisisshi small fix that resolved it for me in this PR https://github.com/capitalone/cloud-custodian/pull/2556
closing via #2556 and #2551