-
Bug
-
Resolution: Done
-
Critical
-
Logging 5.5.0
-
False
-
None
-
False
-
NEW
-
OBSDA-59 - CloudWatch log forwarding add-on needs to support STS installations
-
VERIFIED
-
-
Logging (Core) - Sprint 220, Log Collection - Sprint 221
When using sts role secret, the clf/instance raises error below.
{ "conditions": [ { "lastTransitionTime": "2022-06-17T06:03:08Z", "message": "all pipelines invalid: [to-cloudwatch]", "reason": "Invalid", "status": "False", "type": "Ready" } ], "outputs": { "cloudwatch": [ { "lastTransitionTime": "2022-06-17T06:03:08Z", "message": "auth keys: aws_access_key_id and aws_secret_access_key are required", "reason": "MissingResource", "status": "False", "type": "Ready" } ] }, "pipelines": { "to-cloudwatch": [ { "lastTransitionTime": "2022-06-17T06:03:08Z", "message": "invalid: unrecognized outputs: [cloudwatch], no valid outputs", "reason": "Invalid", "status": "False", "type": "Ready" } ] } }
- relates to
-
LOG-2767 sts cloudwatch secret should accept the secret format from credential requests
- Closed