UP20030 No permissions to assumeRole
The error you see is of the kind:
Possible Causes
The error happens when there is an attempt to connect an S3 location managed by another AWS account, other than the one running SQLake.
You created an AWS_ROLE to access your bucket. However, the role running where you run SQLake doesn't have permission to assume your new role and access the location.
Possible Solutions
If you run on a private VPC, contact your system administrator. Follow the above guide but configure the trust policy to allow where the VPC is installed to assume the role created to access your bucket.
PreviousUP20020 No access to databaseNextUP20040 Could not DROP entity used by a job or materialized view
Last updated