AWS devopsagent documentation change
Summary
Added new log events for third-party provider failures and credential access issues, with updated error type examples.
Security assessment
The change documents new security-relevant log events (e.g., credential access denials) which aid monitoring, but doesn't indicate resolution of a specific security vulnerability.
Diff
diff --git a/devopsagent/latest/userguide/configuring-integrations-and-knowledge-vended-logs-and-metrics.md b/devopsagent/latest/userguide/configuring-integrations-and-knowledge-vended-logs-and-metrics.md index 23a36ca68..5fb9c5976 100644 --- a//devopsagent/latest/userguide/configuring-integrations-and-knowledge-vended-logs-and-metrics.md +++ b//devopsagent/latest/userguide/configuring-integrations-and-knowledge-vended-logs-and-metrics.md @@ -117,0 +118,2 @@ Agent outbound communication failure | An outbound communication to a third-part +Third-party provider call failed | An outbound call to a connected third-party provider failed because the provider returned an error or a network error occurred. The log includes the HTTP status code and the service type. | ERROR +Association credential access denied | Access was denied or authorization failed while retrieving the stored credentials for an association — for example, insufficient permissions, or an encryption key that is disabled or unavailable. The log records the public AWS error code in `optional_details`. | ERROR @@ -370 +372 @@ optional_reference | String | Reference from an agent task (for example, a Jira -optional_error_type | String | Error type +optional_error_type | String | Error type. For example, `PROVIDER_ERROR` when a third-party provider call fails, or `TOKEN_ACCESS_DENIED` when access is denied while retrieving an association's credentials.