Even after attaching the necessary AWS-managed policy, why is my IAM user still not allowed access?

I’m having a perplexing problem: even after attaching an AWS-managed policy (such AmazonS3FullAccess) to an IAM user, the user continues to receive AccessDenied when attempting to use the CLI or terminal.

I looked for explicit denials, session policies, permission restrictions, and SCPs, but nothing caught my attention.

Has anyone ever encountered a scenario where access is denied by AWS even if permissions appear to be correct?

What more should I look for?

@Carol_123 Welcome to the forum!

Did you already contact Bitwarden support?