set default endpoint in aws to empty string

[aspacca]

Bug

What does this PR do?

Apply an hotfix for elastic/beats#32888 directly in the aws integration package.
Proper fix downstream will be addressed in elastic/beats#32921

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-08-31T08:37:30.705+0000

• Duration: 37 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	185
Skipped	2
Total	187

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (16/16)	💚
Files	95.833% (23/24)	👎 -1.512
Classes	95.833% (23/24)	👎 -1.512
Methods	87.302% (275/315)	👎 -2.573
Lines	95.387% (8167/8562)	👍 4.653
Conditionals	100.0% (0/0)	💚

[tommyers-elastic]

thanks for doing this @aspacca !

small nit: the changelog description could be more informative.. we're not really 'fixing' the default endpoint

[tommyers-elastic]

LGTM - could this have any impact on existing installations at all?

[aspacca]

could this have any impact on existing installations at all?

fips will be disabled with this workaround, until we will merge elastic/beats#32921