I'm trying to figure out how to list all of my resources in AWS, but only the ones that I've personally created. I've heard suggestions about using the Tag Editor, but that shows a lot of default resources that I didn't create. It feels like a lot of folks have this issue, but I'm not sure if I'm asking for too much here. Can anyone help me figure out how to accurately filter my resources?
4 Answers
I think you raise a good point! This should be a feature request for the AWS console. Many new users probably struggle with this. But keep in mind that most major AWS customers don't use the console much for resource creation; they rely on Infrastructure as Code (IaC) or the command line for managing resources. That could make it tricky to justify making this a priority for AWS.
If you tag your resources properly when you create them, it makes things way easier. Try using tags like 'created-by' or 'owner' for better organization. Then, you can just filter them in the Cost Explorer to find what belongs to you. There are also ways for AWS to automatically add tags if you want to set that up. Just keep in mind that by default, it's not straightforward to sift through everything if you haven’t tagged accordingly.
I discovered that if I give a resource a name, it pops up in Resource Explorer as "Tags 1" which helps a lot! Filtering by those tags is definitely the way to go.
The way I see it, if you have CloudTrail enabled, you could look through those logs to track what you've created. It might be easier if you bring those logs into Athena, but just a heads up, it can be a bit complicated to set up. Also, tagging really helps, so you might want to start doing that if you can.
Honestly, it's tough to pinpoint what you've created when using the web console because it automatically generates a ton of resources behind the scenes. For instance, when you start creating tasks, it sets up service-linked roles and might create additional dependencies like VPCs and security groups you didn't ask for. The console focuses on convenience, not transparency about who created what.
True, but if AWS can improve the console for those occasional users, it might save some headaches down the line for everyone, right?