- Newest
- Most votes
- Most comments
Please try on AWS.config.credentials under Amplify configuration, also check for session expiry
Hey,
Hope you're keeping well.
That error means the app isn’t actually receiving any AWS credentials, regardless of the IAM policy. In Amplify, S3 calls from a Next.js frontend require an authenticated user via Amplify Auth (Cognito) or an explicitly configured IAM role when running server-side. Check that Amplify.configure includes your Auth settings and that AWS.config.credentials is being populated before the S3 call. Also verify your policy’s resource is correct — it should be arn:aws:s3:::your-bucket-name/* instead of arn:aws:s3:::/* — and that the role is assumed by the identity making the request. Without valid, non-expired temporary credentials, the SDK will always throw a CredentialsProviderError.
Thanks and regards,
Taz
answered 10 months ago
Relevant content
asked a year ago
asked a year ago
- AWS OFFICIALUpdated 2 years ago
