Issues Configuring AWS IAM Principles with Dynamic AWS Accounts for aiven-private link
As Aiven customer,
We are experiencing difficulties configuring the IAM principles while setting up Aiven private link services due to the dynamic nature of our AWS accounts. Specifically, we would like to know if it's possible to use a wildcard (*) in place of specifying individual AWS account IDs, as managing the access control for multiple dynamic accounts is becoming complex.
3
votes
Hellofresh
shared this idea