AWS config source pass supplementaryConfiguration data with resource
See original GitHub issueIs your feature request related to a problem? Please describe.
Any reason why we do not return supplementaryConfiguration
along with configuration
. This would be helpful since this seems to contain tag information on resources which would be useful for further value filters.
https://github.com/cloud-custodian/cloud-custodian/blob/master/c7n/query.py#L350
Describe the solution you’d like
We can either add it to the resource data by default , or can create an option on the config
source that will then add it.
for example:
policies:
- name: sns-test
resource: aws.sns
source: config
supplimentary-config: true
query:
- clause: "tags.key = 'tag-check'"
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Supported Resource Types - AWS Config
AWS Config records the configuration details of Dedicated hosts and the instances that you launch on them. As a result, you can use...
Read more >Selecting Which Resources AWS Config Records
You can use the AWS Config console to select the types of resources that AWS Config records. Sign in to the AWS Management...
Read more >ConfigurationItem - AWS Config
A list that contains detailed configurations of a specified resource.
Read more >Record Configurations for Third-Party Resources - AWS Config
You can publish the configuration data of third-party resources into AWS ... From the File menu, choose New, then choose Project From Existing...
Read more >How to query your AWS resource configuration states using ...
Enable Amazon S3 configuration snapshot delivery in AWS Config. The first step in setting up Amazon Athena so it can query your AWS...
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
grep through the source for ConfigSource subclasses (there are at least a half-dozen) and do one for sns would be the recommend.
there are problems with resource group tagging that make it less then ideal for lambda usage. it needs api to get tags on a single resource, prioritizing as a feature request to your account team would be appreciated.