[Bug]: aws_lambda_permission source_account creates invalid IAM condition key

[baolsen]

Terraform Core Version

1.2.9

AWS Provider Version

4.39.0

Affected Resource(s)

aws_lambda_permission

Expected Behavior

When specifying the source_account argument, a condition key should be created like so:

{
 "StringEquals": {
  "aws": "112233445566"
 }
}

Condition keys are case-sensitive.

Actual Behavior

The following condition key is created instead:

{
 "StringEquals": {
  "AWS": "112233445566"
 }
}

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

Snippet:

resource "aws_lambda_permission" "this" {
  # statement_id  = "AllowExecutionFromRole"
  action        = "lambda:InvokeFunctionUrl"
  function_name = aws_lambda_function.this.function_name
  principal = "arn:aws:iam::112233445566:role/r-112233445566-role"
  source_account = "112233445566"
  function_url_auth_type = "AWS_IAM"
}

Steps to Reproduce

Create any aws_lambda_permission resource and specify source_account.
View the created permissions in the AWS console.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

Lambda permissions reference:
https://docs.aws.amazon.com/lambda/latest/dg/urls-auth.html

Condition keys reference:
"StringEquals; Exact matching, case sensitive"
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html

Would you like to implement a fix?

Yes

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[baolsen]

Might be an AWS limitation, when both --source-account and --function-url-auth-type are specified to the API.
Awaiting feedback on support case.