Stefano Vozza
Stefano Vozza
The discovery process in not crashing but It looks like there are only 1734 resources in the entire aggregator, that seems very low for an organization wide aggregator. When you...
The results of the SQL query means it looks like the issue is that AWS Config is not enabled in any regions in that account. Try enabling it in `us-east-1`...
Yeah, it needs to be enabled in each region you're interesting in.
That's strange. Are there any errors in the discovery process logs?
What version of the solution are you using? We did add a fix to this for the new version (2.1.0) released a few weeks ago.
So it looks like the fix released in v2.1.0 only partially fixed this bug. We will have to investigate what other edge cases are causing the problem. I have noticed...
@JacobReynolds is correct and so is the fix posted. I have tidied up the lambda function a bit and added steps on how to patch in this [comment](https://github.com/aws-solutions/workload-discovery-on-aws/issues/509#issuecomment-1934666948).
This was fixed in v2.1.6.
Thanks for your request. We will add this to the backlog and evaluate it for a future release
Thanks for this suggestion and the example PR too.