Skip to content

Commit 75a4ff8

Browse files
authored
Update docs/getting-started/agentless-troubleshooting.asciidoc
1 parent 10783f2 commit 75a4ff8

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

docs/getting-started/agentless-troubleshooting.asciidoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ On the **Fleet** page, the agent associated with an agentless integration will h
2424
. Confirm that you entered the correct credentials for the cloud provider you're monitoring. The following is an example of an error log resulting from using incorrect AWS credentials:
2525
+
2626
```
27-
[elastic_agent.cloudbeat][error] Failed to update registry: failed to get AWS accounts: operation error Organizations: ListAccounts, get identity: get credentials: failed to refresh cached credentials, operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: cb01df90-1e78-4ae0-bdad-7e71b1d68f86, api error AccessDenied: User: arn:aws:iam::704479110758:user/lola is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::704479110758:role/cloudbeat-root
2827
```
2928
+
3029
. For information about collecting logs, refer to {fleet-guide}/fleet-troubleshooting.html[Fleet troubleshooting].

0 commit comments

Comments
 (0)