[8.19](backport #47712) [libbeat] aws auth method: fix service name and region overwrite

[mergify]

Proposed commit message

Fix the service name and region overwrite when values are set in the input configuration in the aws auth method that was introduced here.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

---

This is an automatic backport of pull request #47712 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 183016c has failed:

On branch mergify/bp/8.19/pr-47712
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit 183016ce9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   x-pack/libbeat/common/aws/signer.go
	modified:   x-pack/libbeat/common/aws/signer_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   x-pack/libbeat/common/aws/credentials_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[botelastic]

This pull request doesn't have a Team:<team> label.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[olegsu]

More context: #49956

[github-actions]

TL;DR

golangci-lint failed on all three runners (ubuntu, windows, macos) due to a testifylint violation in x-pack/libbeat/common/aws/signer_test.go:171. Replace assert.EqualValues(...) with assert.Equal(...) at that assertion and re-run CI.

Remediation

• Update x-pack/libbeat/common/aws/signer_test.go:171 from assert.EqualValues(t, tc.expectedRequestHeaders, gotHeaders) to assert.Equal(t, tc.expectedRequestHeaders, gotHeaders).
• Push the fix and re-run the golangci-lint workflow (or re-run failed checks) to confirm the lint gate passes.

Investigation details

Root Cause

The workflow run fails in step golangci-lint because testifylint flags equal-values and requires assert.Equal instead of assert.EqualValues.

Evidence

• Workflow: https://github.com/elastic/beats/actions/runs/24514607391
• Job/step:
  • lint (ubuntu-latest) → golangci-lint
  • lint (windows-latest) → golangci-lint
  • lint (macos-latest) → golangci-lint
• Key log excerpt:

x-pack/libbeat/common/aws/signer_test.go:171:4: equal-values: use assert.Equal (testifylint)
	assert.EqualValues(t, tc.expectedRequestHeaders, gotHeaders)
	^
issues found

Validation

• Not run locally; diagnosis is directly from the failing golangci-lint job logs for this workflow run.

Follow-up

• After this lint fix is pushed, this workflow should proceed past the current failure point; if anything else fails afterward, it will be a subsequent issue.

---

What is this? | From workflow: PR Actions Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

TL;DR

The x-pack/heartbeat: Packaging Linux Buildkite job did not fail due to this PR’s code changes; Docker packaging completed successfully, then the job was terminated by signal and failed during Buildkite plugin teardown with a Vault auth error (403 permission denied / invalid token). Immediate action is to retry the job and investigate CI credential/timeout handling, not application code.

Remediation

• Re-run the failed Buildkite job (beats-xpack-heartbeat build 26908) to confirm whether this was transient CI infrastructure failure.
• If it reproduces, rotate/fix the Buildkite Vault token/permissions used by vault-docker-login-buildkite-plugin in pre-exit, and check job timeout/cancellation settings for this packaging step.

Investigation details

Root Cause

This failure is infrastructure/CI teardown, not a compile/test/package defect in repository code.

• Log shows Docker image build/export finished:
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:92 #29 DONE 298.7s
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:112 #31 DONE 2.3s
• Then the job receives cancellation and is terminated:
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:122 # Received cancellation signal, interrupting
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:124 signal: terminated
• Teardown hook fails due to Vault auth/permission:
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:135 Code: 403
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:141 permission denied
  • /tmp/gh-aw/buildkite-logs/beats-xpack-heartbeat-ubuntu-x-packheartbeat-packaging-linux.txt:143 invalid token

PR diff check: this PR only modifies AWS signer files (x-pack/libbeat/common/aws/signer.go and x-pack/libbeat/common/aws/signer_test.go), which are unrelated to Buildkite/Vault teardown behavior.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/44232
• Job/step: :ubuntu: x-pack/heartbeat: Packaging Linux (beats-xpack-heartbeat build 26908)
• Key log excerpt:

#31 DONE 2.3s
# Received cancellation signal, interrupting
Error: The command was interrupted by a signal: signal: terminated
...
Code: 403
* permission denied
* invalid token

Verification

• Not run locally; diagnosis is based on the provided Buildkite failure log and PR diff metadata.

Follow-up

If rerun passes, treat as transient CI instability. If rerun fails with same Vault error, this should be escalated to CI/Buildkite secrets ownership rather than fixed in this PR branch.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.