Stefano Vozza
Stefano Vozza
I have never seen an error like this before but it looks like it could be an SCP associated with the account that Workload Discovery was deployed to. The `arn:aws:sts::856369053181:assumed-role/OriginAccessControlRole/EdgeCredentialsProxy+EdgeHostAuthenticationClient-DEL54-P7`...
I'm not sure what you mean by deploying CloudFront in `us-east-2`? CloudFront is a global service so it doesn't have a region associated with it. The solution can be deployed...
Closing due to inactivity.
Do you have screenshots? What resources types were you trying to visualise?
VPC relationships are not depicted using arrow lines, but rather a bounding box. If you just put a VPC on the diagram it's only going to show the first order...
Closing due to inactivity.
This would definitely be a good addition but I am concerned about the complexity that would be required to give the discovery process access to make the various API requests...
Errors around resource missing will be in the ECS logs, the instructions are at the bottom of the page section titled **To retrieve the logs for the discovery component.**: (https://aws-solutions.github.io/workload-discovery-on-aws/workload-discovery-on-aws/2.0/debugging-the-discovery-component.html)....
Then it's very likely the last issue I mentioned. To verify: 1. identify a resource that is missing, for example, an EC2 instance and get the ARN. 2. Log into...
My concern here is the amount of extra whitespace having the full names would introduce into diagrams. I do wonder though if we could make this configurable in the **Diagram...