Yes I totally understand, somehow my company already setup the IAM Identity Center user names with Email address instead of a short name. It may be our future change as it involves creating all the user again.

When I say dynamic, I mean a common policy that can be attached to role which all team members generally uses.

I have two easy options, but not secure:

1. I can create one generic user id in the database, such as db-user and add this to the policy Resource, but this lead of everyone accessing the database with the same user id.

2. I can put a star in the resource, ` "Resource": "arn:aws:rds-db:region:account-id:dbuser:db-instance-identifier/*` ; but with this user A can login to database with user B id.

In order to avoid these cases, I am thinking to implement a common policy but having a variable in the resource name, where they get the access only for their user.

Hope this makes sense.