Stefano Vozza

Hmmm, that is very odd but it's not the cause of your issue. That's the policy that allows the ECS task to assume the role that you provision using the...

Firgot to close this after our debugging call!

Ah apologies, we will fix that. It should be pointing here: https://aws-solutions.github.io/workload-discovery-on-aws/workload-discovery-on-aws/2.0/debugging-the-discovery-component.html There is also troubleshooting doucmentation here: https://docs.aws.amazon.com/solutions/latest/workload-discovery-on-aws/troubleshooting.html Also, there is an Applications Insight dashboard where there may be...

The issue template has been fixed to no longer have this broken link.

We have been gradually migrating to the new SDK over the past few releases and will continue to do so until they're all updated.

Thanks for raising this so we can track it! At the very least we should document this in the troubleshooting guide.

I've been thinking about this and adding more CFN parameters for this scenario is something I want to avoid. With the release of v2.2.0 on Wednesday, the solution now has...

We added documentation to the troubleshooting section of the implementation for this issue: https://docs.aws.amazon.com/solutions/latest/workload-discovery-on-aws/troubleshooting.html#gremlin-lambda-times-out.

Given that this is just middleware under the hood, I think we can simplify the API here. We already allow to users to pass middleware into their routes, I don't...

I'll answer your points in reverse order @dreamorosi. > This is mainly stylistic, but considering that this feature is expected to be the foundation for the OpenAPI schema one, these...