Andrew Huynh
Andrew Huynh
**Describe the bug** Taken from https://github.com/aws/amazon-cloudwatch-agent/runs/7796034979?check_suite_focus=true ``` 2022/08/11 21:32:50 D! Successfully created credential sessions 2022/08/11 21:36:51 E! Failed to get credential from session: NoCredentialProviders: no valid providers in chain caused...
**Describe the bug** ``` null_resource.integration_test (remote-exec): cwl_util.go:62: Error occurred while getting log events: operation error CloudWatch Logs: GetLogEvents, https response error StatusCode: 400, RequestID: 9068b214-19ed-4ee9-beea-951cc1cdf4b7, ResourceNotFoundException: The specified log group...
https://github.com/aws/amazon-cloudwatch-agent/pull/293 was introduced, allowing people to set the log level of the agent without restarting. This functionality was not ported over to the `packaging/darwin/amazon-cloudwatch-agent-ctl` script, though: ``` usage: amazon-cloudwatch-agent-ctl -a...
We should make sure that we don't introduce changes that break [Container Insights](https://github.com/aws-samples/amazon-cloudwatch-container-insights). This would be pretty substantial in comparison to existing integration tests on this repo.
This was attempted to be addressed in #334, and is tidied up, but the test is still flaky
Currently, the agent only supports a subset of available forms of authentication provided by the AWS SDK for Go. One that's missing is [process credentials](https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html). The agent supports static credentials...
CloudWatch Logs announced today that customers no longer need to use the special header to designate a log as EMF: https://aws.amazon.com/about-aws/whats-new/2023/01/amazon-cloudwatch-metric-extraction-structured-logs/ There is special logic in the CloudWatch agent to...