Workload Discovery on AWS is a solution to visualize AWS Cloud workloads. With it you can build, customize, and share architecture diagrams of your workloads based on live data from AWS. The solution maintains an inventory of the AWS resources across your accounts and regions, mapping their relationships and displaying them in the user interface.
Feature name
In the resources screen, it would be really useful to be able to search/filter for accounts by name, not just by ID
Is your feature request related to a problem? Please describe.
No
Describe the feature you'd like to see implemented
Currently when filtering by account we have to search by account ID. Nobody knows accounts by ID only by name so we have to keep a mapping file in externally or look it up in the AWS console which is needlessly complex. If we could search by acct name and also include the name next to the ID when viewing the results it would significantly enhance usability.
Describe the value this feature will add to AWS Perspective
This feature would significantly enhance usability when filtering resources by account.
Describe alternatives you've considered
We currently use an external mapping file to map account names to IDs. This is clunky and slows down interaction with the tool.
Feature name In the resources screen, it would be really useful to be able to search/filter for accounts by name, not just by ID
Is your feature request related to a problem? Please describe. No
Describe the feature you'd like to see implemented Currently when filtering by account we have to search by account ID. Nobody knows accounts by ID only by name so we have to keep a mapping file in externally or look it up in the AWS console which is needlessly complex. If we could search by acct name and also include the name next to the ID when viewing the results it would significantly enhance usability.
Describe the value this feature will add to AWS Perspective This feature would significantly enhance usability when filtering resources by account.
Describe alternatives you've considered We currently use an external mapping file to map account names to IDs. This is clunky and slows down interaction with the tool.
Additional context