Skip to content

Provide additional flexibility for assume_role_policy #196

@pjungels-paraport

Description

@pjungels-paraport

I was frustrated to find that there's not a way to achieve this type of trust policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "lambda.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    },
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::ACCOUNT_NUM:root"
      },
      "Action": "sts:AssumeRole",
      "Condition": {
        "StringEquals": {
          "sts:ExternalId": "SomeExternalId"
        }
      }
    }
  ]
}

We can already add additional principals as trusted entities to the assume_role policy document. It would be great if we could also add additional statement blocks to the assume_role policy doc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions