[aws] Add Instance/Pod IAM Role option to Setup Access selector (7.1.x) - #21046
Conversation
Add a default_credentials var_group option (displayed as "Instance or Pod IAM Role") with no required fields, so Elastic Agent can authenticate using the AWS SDK default credential chain (EC2 instance profile, EKS Pod Identity, IRSA) without entering access keys or a Role ARN. This restores the documented capability that was blocked when the credential_type var_group became required with all-var options in 7.0.0 (elastic#19828). Update the credentials documentation to clarify the Setup Access selector, explain each option's purpose, and distinguish "Assume Role" (assumes a specified role) from "Instance/Pod IAM Role" (uses the role attached to the host). Unlike main, this line still has the "Assume Role with External ID" option, so it is documented as well. Backport of elastic#21025 to backport-aws-7.1, the last line installable on Kibana 9.4.x and 9.5.x (7.2.0+ require Kibana ^9.6.0).
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Elastic Docs Style Checker (Vale)Summary: 4 suggestions found 💡 Suggestions (4): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
There was a problem hiding this comment.
🟢 Approval recommended
The manifest, docs, and changelog updates are consistent with the stated goal and appear internally coherent for the 7.1.x backport.
Pull request overview
This PR backports the “Instance or Pod IAM Role” / AWS SDK default credential chain authentication option to the AWS integration’s Setup Access selector on the 7.1.x line, restoring the ability to save policies without entering access keys or a role ARN.
Changes:
- Bump
awspackage version to 7.1.2 and add adefault_credentialsSetup Access option with no fields. - Update AWS credentials documentation to explain the Setup Access selector and clarify the differences between Assume Role and Instance or Pod IAM Role (and document Assume Role with External ID on this branch).
- Add a 7.1.2 changelog entry referencing this PR.
File summaries
| File | Description |
|---|---|
| packages/aws/manifest.yml | Bumps version and adds default_credentials var_group option with vars: [] (no required fields). |
| packages/aws/docs/README.md | Updates credential configuration docs and adds a Setup Access options table and updated role-auth sections. |
| packages/aws/changelog.yml | Adds a 7.1.2 bugfix entry linking to the PR. |
| packages/aws/_dev/build/docs/README.md | Mirrors the docs changes in the build/docs copy. |
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🟢 Approval recommended
The manifest, docs, and changelog updates are consistent with the stated goal and appear internally coherent for the 7.1.x backport.
Review details
- Files reviewed: 5/6 changed files
- Comments generated: 0 new
- Review effort level: Lite
The observability-ci account SCP now denies resource creation without the division/org/team/project tags, breaking the 11 SQS-based data stream system tests and redshift. (cherry picked from commit ecadef5)
…/kcreddy/integrations into aws-default_credentials-backport
There was a problem hiding this comment.
🟢 Approval recommended
The changes are consistent and scoped to enabling/clarifying AWS default-credential-chain auth via the Setup Access selector, with matching versioning and documentation updates.
Review details
- Files reviewed: 17/18 changed files
- Comments generated: 0 new
- Review effort level: Lite
|
✅ All changelog entries have the correct PR link. |
|
✅ Package owners are in sync with |
|
🟢 No issues across the latest commits 55e079f, ea5bfe6.
🤖 AI-Generated Review | Vera Review Bot - v0.3.0 | 📚 Knowledge base: integration-skills
|
💛 Build succeeded, but was flaky
Failed CI StepsHistorycc @kcreddy |
mrodm
left a comment
There was a problem hiding this comment.
LGTM, for the go.mod and go.sum changes
|
Tick the box to add this pull request to the merge queue (same as
|
|
Changelog sync PR created: #21061 |
|
Package aws - 7.1.2 containing this change is available at https://epr.elastic.co/package/aws/7.1.2/ |
Proposed commit message
Checklist
changelog.ymlfile.Related issues