Upgrade AWS SDK to support EKS Pod Identity

[bartoszcisek]

Describe the enhancement

EKS pod identity is an improved way to grant selected access for pods to AWS resources. Support for pod identity starts at 1.47.11 ASW SDK version.

Describe a specific use case for the enhancement or feature

Granting elastic agent access to RDS DB for elastic agent AWS integration.

What is the definition of done?

Elastic agent uses AWS SDK in version higher that 1.47.11.

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[mholttech]

I was literally just looking for this. Hope to see the sdk version bumped soon.

[cucxabong]

Hi guys,

Do you have any update on this?

[mholttech]

Any update on this?

CC: @bvader

[zmoog]

Quick update on this issue.

Since we bumped the AWS SDK during standard update cycle, we are testing a recent version of Elastic Agent (8.15.3) to double-check it support EKS Pod Identity.

So far we tested the following inputs.

Logs:

• cloudwatch-logs: OK

Metrics:

• cloudwatch: OK

We still need to fully test the following:

Logs:

• aws-s3 (SQS mode)
• aws-s3 (S3 polling mode)

[yavor-martian]

This one seems to be resolved in the latest version of the agent 8.15.3

[zmoog]

EKS Pod Identity is available starting at least from 8.15.3.

I created a public issue #41775 to track the need to update the official docs for Beats and the Elastic Agent integrations.

Feel free to reopen if you run into issues or comment if you have questions.