Sync S3

[Carl-Gustaf]

I followed your steps 1 to 4 and it worked great. But still nothing happens after setting up my AWS credentials in .env. I have tested the credentials and they are active. So Should I re init Koel? Should I specify a media path when I use AWS? I feel the answer to this might be a good step 5.

[3lpsy]

Check CloudWatch logs for your lamda. When you upload an mp3, are there logs? There should be around 3 for each request/action.

[Carl-Gustaf]

This should be what you requested:

{
"errorMessage": "Failed to fetch object from S3: AccessDenied: Access Denied"
}

[myultimabot]

How did you solve this issue?

[chawker21]

Im having trouble with this as well, I have .env file named AWS_BUCKET for another aws feature but I dont see anywhere in the koel-aws where it should know what bucket to use... is this feature functioning for anyone else?

[phanan]

The bucket name, along with other song info/data, is posted to Koel everytime a new song is uploaded to your AWS bucket. For example, if you're storing a file bar.mp3 into a bucket foo then you'll expect a new song record in Koel's main database with path being s3://foo/bar.mp3. Upon reading this info, Koel will determine it to be an S3 resource and handle it accordingly.

[bumbummen99]

The bucket name, along with other song info/data, is posted to Koel everytime a new song is uploaded to your AWS bucket. For example, if you're storing a file bar.mp3 into a bucket foo then you'll expect a new song record in Koel's main database with path being s3://foo/bar.mp3. Upon reading this info, Koel will determine it to be an S3 resource and handle it accordingly.

What if the koel instance is currently not reachable or when a LOT of songs are uploaded at once and the lambda does timeout? Is there any way to sync s3 without re-upload?