Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
EC2 Snapshots gets lots of stuff, takes very long
See original GitHub issueI’m trying Cartography on an AWS account that is practically empty (just a few users), and noticed that it takes a while to run. What really stands out is that it takes over 9 minutes to get EBS snapshot data. And this account does not have (and never had) any EBS volumes in any regions.
Yet, when I debug get_snapshots() in snapshots.py, I see that client.get_paginator('describe_snapshots') returns many thousands of records despite the fact that there is no snapshot data in any region visible in the AWS Console.
So, what is describe_snapshots returning exactly, and do we need all that?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@danielsaporo There’s public EBS snapshots for public datasets, and there’s a lot of them. This is similar to public AMIs. See, for example, how I changed that to only pull AMIs from owned accounts, but then introspected the graph to find other images that should be fetched: https://github.com/lyft/cartography/blob/master/cartography/intel/aws/ec2/images.py#L17-L59
Thanks for fixing this. What is the process to upgrade to a newer version of Cartography that includes this fix? Do I need to wait for some kind of release to happen first?