Come posso risolvere l'errore "User/IAM role X is not authorized to perform Y on resource Z" error in AWS Glue (L'utente/ruolo IAM X non è autorizzato a eseguire Y sulla risorsa Z in AWS Glue)?

Come posso risolvere i problemi durante la connessione ai cluster Amazon RDS per PostgreSQL o Aurora PostgreSQL utilizzando l'autenticazione IAM?

Come faccio a connettermi ad Amazon RDS per PostgreSQL o Amazon Aurora PostgreSQL utilizzando l'autenticazione IAM?

Perché la copia dello snapshot della mia istanza di database compatibile con Aurora PostgreSQL impiega così tanto tempo per essere copiata?

# Scenario: RDS Aurora v2 DB snapshot export to S3 bucket

Console gives error _**Principal isn't allowed to assume the IAM role**_ citing 
 * EITHER non-existent IAM role or 
 * OR Principal not allowed to take IAM role.

While this IAM role is being created by Console GUI logic itself.

![IAM Error during RDS Snapshot export to S3](https://repost.aws/media/postImages/original/IM0HNRcGcLT4KWmBiyujEFcQ)

# Additional information
1. Principal name specified by error is _**rds-export.aws.internal**_ => Here internal is never seen in any examples cited in knowledge article.
2. Related article in knowledge center about [IAM role doesn't exists](https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-export-snapshot/) asks to specify correct Principal as *export.rds.amazonaws.com* instead of rds.amazonaws.com

_To resolve this issue, make sure that the trust relationship specifies "export.rds.amazonaws.com”  instead of “rds.amazonaws.com” in your IAM policy.   
While here the Principal is specified as *rds-export.aws.internal* which seems to be an issue_

RDS Snapshot export to S3 fails citing IAM role error where IAM role is created by Console itself

Scenario: RDS Aurora v2 DB snapshot export to S3 bucket

Additional information

Contenuto pertinente