search

aws-solutions / workload-discovery-on-aws

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.
https://aws.amazon.com/solutions/implementations/workload-discovery-on-aws/
Apache License 2.0
727 stars 88 forks source link

Region not discovered and missing resources in other region #526

Closed vmorkunas closed 5 months ago

vmorkunas commented 5 months ago

Describe the bug AWS region us-east-1 is not discovered and most of eu-central-1 region resources missing

To Reproduce Steps to reproduce the behavior:

  1. Deploy CF regional templates in each region (3) and global template in eu-west-1
  2. Import single account with 3 regions: eu-west-1, eu-central-1, us-east-1
  3. After next scan it finds only eu-west-1 and eu-central-1 region resources
  4. us-east-1 region in accounts section is marked as not discovered and eu-central-region find only target groups

Expected behavior All regions imported properly and resources are not missing

Screenshots bug2 bug

Browser (please complete the following information):

Additional context Checked disovery guide but there are no errors in logs. CF templates are green in each region and the global one is green too. Authorisations are present in aws config in target account

vmorkunas commented 5 months ago

Issue was wrong aggregator region in regional CF templates. Once fixed, AWS Config aggregator in account where solution was hosted was able to pull all data.

svozza commented 5 months ago

It can take more than one scan after the resources have been added for the resources from Config to appear but the us-east-1 issue is strange. When you go to the the AWS Config -> Aggregators what do you see if you click on the link in the first screenshot here that that says 3 account(s)?

Screenshot 2024-06-05 at 13 34 41 Screenshot 2024-06-05 at 13 34 55
svozza commented 5 months ago

Issue was wrong aggregator region in regional CF templates. Once fixed, AWS Config aggregator in account where solution was hosted was able to pull all data.

Ah good stuff!