[AWS] Update README - EC2 Instance IAM Role for AWS Authentication

[ecs-chrisg]

Proposed commit message

Update AWS readme - Add a subsection to the AWS Credentials section explaining how to use an EC2 instance's IAM role for AWS authentication.

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [aws] Improve documentation on using EC2 IAM Role directly #8359

Screenshots

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[bturquet]

LGTM

[ecs-chrisg]

@bturquet Thanks! Should I update changelog.yml and manifest.yml to make this PR version 3.3.1?

[zmoog]

@bturquet Thanks! Should I update changelog.yml and manifest.yml to make this PR version 3.3.1?

Hey @ecs-chrisg, yes, we should always add new changes on top of the latest ones first.

If we need to support previous stack versions (e.g., 8.15.x), we can backport the change. However, adding it as the latest is fine since this is a pure-docs change.

Once merged, these changes will be available at https://www.elastic.co/docs/reference/integrations/aws/ and Kibana versions matching:

conditions:
  kibana:
    version: "~8.16.6 || ~8.17.4 || ^8.18.0 || ^9.0.0"

So a user on 8.15 or earlier stack versions will not see the updated docs in Kibana.

[ecs-chrisg]

@zmoog Makes sense! Newer versions of the integration keep getting merged to main in the time since this PR was opened, so I have to keep updating this integration's version # to stay up to date. I just updated manifest.yml and changelog.yml to 3.3.2.

[zmoog]

In the packages/aws/manifest.yml file:

• version is the actual integration version.
• format_version is the package-spec version this integration uses.

The two accidentally had almost the same values, creating an ambiguity.

For example, if we bump the integration version to 3.3.2, there must be an entry for 3.3.2 at the top of the changelog.yml file

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b7fd5c4

History

• 💔 Build #25666 failed 14d8790
• 💔 Build #25665 failed f9e3fb8
• 💚 Build #25635 succeeded 4bbe8f3
• 💚 Build #24372 succeeded c06c433

[elastic-vault-github-plugin-prod]

Package aws - 3.3.2 containing this change is available at https://epr.elastic.co/package/aws/3.3.2/