i answered in some slack threads, but will reitera...
# getting-started
b
i answered in some slack threads, but will reiterate here: the 403 error is coming from the AWS API, so it's related to something there. I suspect there are issues related to how you've authenticated to AWS AWS has an article on 403 errors when dealing with S3 buckets: https://aws.amazon.com/premiumsupport/knowledge-center/s3-troubleshoot-403/ there's also a stack overflow answer here: https://stackoverflow.com/questions/26691286/amazon-s3-bucket-returning-403-forbidden