Carrierwave / AWS S3 Upload Endpoints about carrierwave-aws HOT 9 CLOSED

I am going crazy. My old deploy was using the 1.0.0 version of carrierwave. Tried rolling that back - no luck.

I even tried using the old server region and bucket. Same error message.

from carrierwave-aws.

I would guess that there is a mismatch between the AWS_REGION and your CLOUDFRONT_HOST, but that is just a guess. Since this was working before it seems like this is purely an AWS / Config issue and not a bug coming from carrierwave-aws.

from carrierwave-aws.

That’s the crazy part. I have tested it with the same region / keys / settings as the existing server that works - I still get the same error. Both are using the same cloud front host etc. I am just hoping someone out there may have seen this issue before.

from carrierwave-aws.

I am going to close this. I went through line by line and manually entered the config values vs vis ENV. It worked. Put the ENV back in and still works. No idea - must have been a typo on my end somewhere.

from carrierwave-aws.

Glad you figured it out 👍

from carrierwave-aws.

Ready to give up at this point and try fog again. The issue persists. It's not related to CloudFront. I can't upload to the non-standard region at all.

from carrierwave-aws.

Same error:

Aws::S3::Errors::PermanentRedirect: The bucket you are attempting to
access must be addressed using the specified endpoint. Please send all
future requests to this endpoint.

I stripped out all CloudFront related code - no signed URLs etc. and using local asset host.

I even added the endpoint config option.

  config.aws_attributes = {
   expires: 10.minutes.from_now.httpdate,
   cache_control: 'max-age=600'
  }

  config.aws_credentials = {
    access_key_id: 'XXXXX',
    secret_access_key: 'YYYYYY',
    region: 'ca-central-1',
    endpoint: 'https://s3.ca-central-1.amazonaws.com'
  }

   config.enable_processing = true
   config.storage = :aws
   config.aws_bucket = 'my-new-ca-central-1-bucket'
   config.aws_acl = :private

from carrierwave-aws.

I switched to FOG and it works with the same configuration.

from carrierwave-aws.

What a mess - I had a bucket setting in another uploaded that was triggering this. I was so focused on the uploaded that was failing that I didn't realize that was the issue. 🤦‍♂️

from carrierwave-aws.