Question 1

How do I migrate from fog to carrierwave-aws in my Rails app?

Accepted Answer

Comment out or remove the storage :fog line in your uploader and replace it with storage :aws. Update configuration keys like changing fog_directory to aws_bucket and adjust URL headers if using custom queries, as explained in the migration section.

Question 2

Is carrierwave-aws better than fog for S3 storage?

Accepted Answer

For S3-specific use, carrierwave-aws is often better due to its smaller footprint, faster performance, and full AWS SDK support. However, fog is more versatile if you need multi-cloud storage or other cloud services.

Question 3

How to set up signed URLs with carrierwave-aws?

Accepted Answer

Configure the aws_signer in your CarrierWave setup to use AWS CloudFront signer or custom logic. Set aws_authenticated_url_expiration, noting that URLs expire after a maximum of 7 days, as shown in the configuration examples.

Question 4

What IAM permissions are needed for carrierwave-aws to avoid AccessDenied errors?

Accepted Answer

The IAM role requires permissions like s3:PutObject, s3:GetObject, s3:DeleteObject, and crucially s3:PutObjectAcl, along with unblocking ACL changes in bucket settings, as detailed in the README's policy guidance.

Question 5

Can I use carrierwave-aws with a custom S3 endpoint like Exoscale?

Accepted Answer

Yes, add an endpoint key in aws_credentials, such as :endpoint => 'my.custom.s3.service.com', to override the standard S3 endpoint, which is useful for non-AWS S3-compatible services.

Question 6

How does carrierwave-aws handle testing without hitting actual S3?

Accepted Answer

Set stub_responses: true in the aws_credentials configuration when in test environment, as shown in the example, to avoid making real S3 calls during tests.

carrierwave-aws

What is carrierwave-aws?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions