Hero beta adds direct evidence links for findings

Hero private beta now includes direct evidence links with supported findings. When the product highlights a cost, security, performance, or operational issue, reviewers can move from the recommendation to the relevant AWS context without reconstructing the investigation from separate dashboards.

Prioritization is only useful when an engineer can verify it. The evidence view is designed to make that verification faster while keeping the decision with the team operating the workload.

What the update adds

Depending on the finding, the beta can now group:

• the affected resource and its configuration context;
• the metric, log, trace, or account signal that triggered the finding;
• the condition that made the issue relevant;
• a suggested next action and the expected trade-off.

Hero continues to use read-only AWS access. It can surface and organize evidence, but it does not modify a workload or apply a recommendation automatically.

Next focus

The next beta work will deepen coverage for event-driven workloads where queue backlog, retry behavior, throttling, and downstream latency need to be reviewed together. Teams using Hero can share which findings required the most manual follow-up so the evidence paths improve around real operating questions.