S3 uploads have stopped working - despite environment variables set up for template | Runpod | Page 1

small wadi Jul 18, 2024, 3:54 PM

#

My worker is not uploading to S3 - despite me setting up the environment variables for S3 in the template. The error in the log is "No bucket endpoint set, saving to disk folder 'simulated_uploaded'" - Interestingly this worked fine previously. I just created a new image and it no longer works. Can you advise on waht to do?

trim storm Jul 18, 2024, 3:58 PM

#

Maybe set the proper env variable for s3 fjrst

#

Edit template

small wadi Jul 18, 2024, 3:59 PM

#

yep - I done that and made sure the variables are all correct in the template. However still the same result

oak shell Jul 18, 2024, 4:04 PM

#

Maybe a regression of the bug fix when the environment variables in serverless got lost.

#

#🚨｜incidents message

small wadi Jul 18, 2024, 4:08 PM

#

Thanks for this context - I'll try the "Please note that you may have to scale down your workers to 0 and back up again to update your workers." step and try again

#

Unfortunately, issue still persists

trim storm Jul 18, 2024, 5:00 PM

#

hmm

#

@glad cave

trim storm Jul 18, 2024, 5:00 PM

#

small wadi Thanks for this context - I'll try the "Please note that you may have to scale d...

try sending your endpoint id here too

fringe moss Jul 18, 2024, 5:15 PM

#

hmm

trim storm Jul 18, 2024, 5:21 PM

#

hmm

#

he's having trouble with the s3 upload function on runpod, madiator

small wadi Jul 18, 2024, 5:41 PM

#

oh thanks @trim storm and @glad cave - it's 3nptpzriu3mt37

glad cave Jul 18, 2024, 6:11 PM

#

@small wadi you have wrong ENV names

#

BUCKET_ENDPOINT_URL
BUCKET_ACCESS_KEY_ID
BUCKET_SECRET_ACCESS_KEY

#

and it your case one env is saved as SECRET_ACCESS_KEY

small wadi Jul 18, 2024, 6:33 PM

#

oh man - that was so dumb of me and thank you so much. I didn't copy and pasted correctly

#

thanks

#S3 uploads have stopped working - despite environment variables set up for template