AWS resilience-hub: Note auto-investigations after DevOps Agent connection
Summary
Adds a sentence explaining that existing failure mode assessment findings trigger Resilience Hub investigations once a service is first connected to an Agent Space.
Security assessment
The added text only describes automatic investigation behavior after a DevOps Agent connection; it mentions the invoker role but introduces no new permission, credential, or exposure guidance.
Evidence
+After your invoker role has the required DevOps Agent permissions, you can connect a service to your Agent Space. Connect a service by providing the Agent Space ARN in the service's DevOps Agent configuration. You can do this when you create a service or when you update an existing one. If there are existing failure mode assessment findings, Resilience Hub runs investigations for each finding after a connection is first established.
Diff
diff --git a/resilience-hub/latest/userguide/next-gen-devops-agent-connect.md b/resilience-hub/latest/userguide/next-gen-devops-agent-connect.md index 865a076..5be0e85 100644 --- a//resilience-hub/latest/userguide/next-gen-devops-agent-connect.md +++ b//resilience-hub/latest/userguide/next-gen-devops-agent-connect.md @@ -9 +9 @@ -After your invoker role has the required DevOps Agent permissions, you can connect a service to your Agent Space. Connect a service by providing the Agent Space ARN in the service's DevOps Agent configuration. You can do this when you create a service or when you update an existing one. +After your invoker role has the required DevOps Agent permissions, you can connect a service to your Agent Space. Connect a service by providing the Agent Space ARN in the service's DevOps Agent configuration. You can do this when you create a service or when you update an existing one. If there are existing failure mode assessment findings, Resilience Hub runs investigations for each finding after a connection is first established.