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.
Is your feature request related to a problem? Please describe.
We currently JSON stringify the relationships field retrieved from AWS Config and write it to the Neptune DB. This has caused problems for customers (GH-316, GH-331 (https://github.com/aws-solutions/workload-discovery-on-aws/issues/316) ) because some nodes have a lot of relationships (e.g., a tag that is an account number can have 1000s of relationships), which can cause payload too large exceptions in the Gremlin AppSync lambda resolver.
Describe the feature you'd like to see implemented
There is no need to save this data, it is not used on the frontend and in any case the relationships are stored in the Neptune DB as edges. Therefore they are easily queried using the database’s query language.
Describe the value this feature will add to AWS Perspective
Reduced payloads, storage costs and errors.
Is your feature request related to a problem? Please describe. We currently JSON stringify the
relationships
field retrieved from AWS Config and write it to the Neptune DB. This has caused problems for customers (GH-316, GH-331 (https://github.com/aws-solutions/workload-discovery-on-aws/issues/316) ) because some nodes have a lot of relationships (e.g., a tag that is an account number can have 1000s of relationships), which can cause payload too large exceptions in the Gremlin AppSync lambda resolver.Describe the feature you'd like to see implemented There is no need to save this data, it is not used on the frontend and in any case the relationships are stored in the Neptune DB as edges. Therefore they are easily queried using the database’s query language.
Describe the value this feature will add to AWS Perspective Reduced payloads, storage costs and errors.
Describe alternatives you've considered n/a