Stefano Vozza

Another thing we were thinking of is that if you've tagged your resource with a key called `Name` we could default to that.

This is something that's come up with other customers too, the fine grained permissions this would allow would definitely be very useful.

This was fixed in v1.1.4.

So if I've got this right would you like to see the graph expand out more than one level as it does currently? I'm thinking we may keep the default...

Thanks for this request, I like this idea.

Very exciting!

The filters and users are not stored in the database so you are probably just better off backing up the Cognito user pool (I've used this before https://www.npmjs.com/package/cognito-backup-restore), the `aws-perspective-amplifystoragebucket-*`...

This issue is a scaling limitation with v1.x.x as the discovery process made an API call to AWS Config for every resource it found. For regions with ~2500 resources, this...

In the meantime, you can use the paginated `getResources` GraphQL query added in v2.0.0 to get all the resources in the database.

Closing due to inactivity