Error (412 Precondition Failed) when creating artifact about turborepo-remote-cache HOT 5 CLOSED

Hi. Would you mind providing a reproduction repository?

from turborepo-remote-cache.

@fox1t I just clicked on the Deploy to Vercel button and set up the environment variables. The repository is exactly the same as this.

from turborepo-remote-cache.

I ran into the same issue. I think the problem is, that the vercel deploy link contains S3_ACCESS_KEY and S3_SECRET_KEY instead of AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. But those AWS_ vars can not be set on vercel, because they are protected.

According to the docs the aws-sdk doesn't look for those S3_ vars. I'm not sure if that was different in the past?
One easy fix could be sticking with the S3_ vars and settings those manually.

// src/plugins/remote-cache/storage/s3.ts
// ...
export function createS3({ bucket, endpoint }: S3Options) {
  aws.config.update({
    accessKeyId: process.env.S3_ACCESS_KEY,
    secretAccessKey: process.env.S3_SECRET_KEY,
    region: process.env.S3_REGION,
    signatureVersion: 'v4',
  })

  const client = new aws.S3({
// ...

from turborepo-remote-cache.

This is a good point! We should remap the AWS_ to S3_ ones. Would you mind open a PR?

from turborepo-remote-cache.

#31

from turborepo-remote-cache.