ServiceGraph Connector for AWS don't fetch resources

Jarkko — Mon, 30 Sep 2024 12:53:35 GMT

Hello,

Anyone have any idea why ServiceGraph connector for AWS does not fetch all the resources on every run? For example Lambda functions and s3 buckets are fetched occasionally. Sometimes all of them are fetched and sometimes none?

And is there any way to enforce ServiceGraph connector for AWS to fetch all resources available on AWS side? The documentation I've found is somewhat sketchy.

Re: ServiceGraph Connector for AWS don't fetch resources

Jarkko — Wed, 02 Oct 2024 13:54:50 GMT

The solution found. We just need to set last_run_datetime to empty value for datasources with name starting with SG-AWS- in sys_data_source table to enforce ServiceGraph connector for AWS fetch all available AWS resources.

If last_run_datetime is set for datasource it fetches only aws resources added/modified after last_run_datetime - 2 .

last_run_datetimes are not accessible from UI, but we can nullify it with the following background script

var gr = new GlideRecord('sys_data_source'); gr.addEncodedQuery('nameSTARTSWITHSG-AWS-'); gr.query(); while(gr.next()){ gr.last_run_datetime = ''; gr.update(); }

question ServiceGraph Connector for AWS don't fetch resources in Community Central forum

ServiceGraph Connector for AWS don't fetch resources

Re: ServiceGraph Connector for AWS don't fetch resources