Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
ASSUME_ROLE_FAILED
HTTP 400 with next_step=contact_support. DataVibe could not assume the IAM role you provided for the S3 sink.
What it means
When you wire an S3 sink with STS AssumeRole, Core attempts the sts:AssumeRole call as part of role verification. If AWS rejects the call we return this error with the original AWS message.
How to fix
- Verify the trust policy on your role allows the DataVibe AWS account id we display in the wizard.
- If you set an
ExternalId, confirm it matches the exact value shown in the wizard. - Make sure the role has
s3:PutObjecton the target bucket prefix. - Re-run role verification from the dashboard once the policy is updated.