near crescent
I have set up a staging server with a separate bucket, created IAM user which has full S3 permissions and generated keys for it.
When I try to list bucket contents using those keys with AWS CLI, all is good. When I do the same using Laravel by populating following env variables:
FILESYSTEM_DISK=s3
AWS_DEFAULT_REGION=us-west-2
AWS_BUCKET=staging-bucket
AWS_ACCESS_KEY_ID=...
AWS_SECRET_ACCESS_KEY=...
After executing Storage::allDirectories() I get an empty array after like 20s. Any ideas?
worn lance
I have set up a staging server with a separate bucket, created IAM user which ha...
Does your IAM user have the s3:ListAllBuckets permission or whatever it’s called?
I think the IAM user needs to be able to list buckets, but then you set an additional condition to restrict which bucket(s) it can work with objects from.
near crescent
Yes, I gave it full permissions. It works with CLI
That's why I find it confusing
By full permissions I mean actual AWS managed S3 admin permissions
pastel grove
@near crescent why are you using access keys and not an instance profile ?
near crescent
<@747469942999351416> why are you using access keys and not an instance profile ...
I have been looking into switching, and also did modifications for SSO variant but haven't made the transition yet.