Skip to content

YACE using excessive iam:ListAccountAliases calls #1853

@caitlin-green-sp

Description

@caitlin-green-sp

YACE very frequently uses iam:ListAccountAliases calls, to the point where it's eating up our rate-limits within AWS. Is there any way to reduce or not require this permission for YACE to function? It says this permission is optional, but when we didn't include it yace still "works" without "iam:ListAccountAliases" it just calls IAM at least twice as many times if you remove the permission from the policy.

Additionally, I have seen this issue:
#1541

We would like to know if there is any ways whatsoever to reduce the number of IAM calls or make this permission truly optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions