Allow to set SourceIdentity in assume_role configuration

[chgerkens]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Please provide a way to specify the SourceIdentity argument as part of an assume_role configuration.

New or Affected Resource(s)

• provider aws, assume_role block: https://registry.terraform.io/providers/hashicorp/aws/latest/docs#assume_role-configuration-block

Potential Terraform Configuration

I suggest to add a new argument "source_identity" to the assume_role configuration block:

provider "aws" {
  assume_role {
    role_arn     = "arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME"
    session_name = "SESSION_NAME"
    external_id  = "EXTERNAL_ID"
    source_identity = "SOURCE_IDENTITY" // suggested new attribute
  }
}

References

• https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html

[ewbankkit]

@chgerkens Thanks for raising this issue.
AWS credentials are handled by the https://github.com/hashicorp/aws-sdk-go-base library.
I have opened an issue - hashicorp/aws-sdk-go-base#87.

[gdavison]

This is also affected by aws/aws-sdk-go-v2#1575

[gdavison]

Implemented in aws/aws-sdk-go-v2#1588

[wlami]

This is blocked by hashicorp/aws-sdk-go-base#87. I already have a local test build implementing this feature - I'll create a PR once the upstream PR on aws-sdk-go-base is merged.

[wlami]

This has been implemented in #25368 and released in v4.29.0 of the Terraform AWS Provider.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.