In this Ruby on Rails tutorial, we are going to configure Ruby on Rails Active Storage module to work with Google Cloud Platform, Amazon AWS S3 Buckets, and Microsoft Azure Cloud.

Table of contents

• What is Ruby on Rails Active Storage?
• Ruby on Rails Active Storage configuration overview
• Ruby on Rails Active Storage server disk usage configuration
• Ruby on Rails Active Storage Google Cloud Platform configuration
  • GCP account setup and bucket creation
  • GCP storage credentials
  • GCP Rails configuration
• Ruby on Rails Active Storage AWS S3 configuration
  • AWS account setup
  • AWS storage credentials
  • AWS Rails configuration
• Ruby on Rails Active Storage Microsoft Azure Cloud configuration
  • Azure account setup
  • Azure storage credentials
  • Azure Rails configuration
• Conclusion

Let us learn more about Ruby on Rails Active Storage setup...

...or have it done

Yes, Hix does this - so you don't have to.

Learn More

#What is Ruby on Rails Active Storage?

Ruby on Rails Active Storage is responsible for storing any files in the Ruby on Rails application and exposing them to Ruby on Rails application's Active Record objects.

Ruby on Rails Active Storage out of the box comes equipped with four different file storage options:

• a local disk-based service, useful for development and testing,
• Google Cloud Platform,
• Amazon AWS S3,
• Microsoft Azure Storage,

and on top of that, supports mirroring files between multiple storage destinations for sane migrations and backups.

Furthermore, Ruby on Rails Active Storage equips the application into the ability to perform various file transformations:

• cropping, resizing and doing everything available via ImageMagick library,
• file format conversion, for example changing JPG to PNG,
• generating images from PDF and other file formats,
• extracting metadata from arbitrary files.

Ruby on Rails Active Storage is the module to use whenever in need to do any kind of work on files.

If your Ruby on Rails application needs to store an avatar uploaded by a user in order to easier identify him in your web app, use Ruby on Rails Active Storage module.

If your Ruby on Rails application needs to generate payment invoices in order to later send them via email, use Ruby on Rails Active Storage module.

#Ruby on Rails Active Storage configuration overview

In order to work, Ruby on Rails Active Storage requires two tables in your application's database:

• active_storage_blobs table,
• active_storage_attachments table

In order to acquire Ruby on Rails migrations creating those tables and then create them in your Ruby on Rails application, run

rails active_storage:install
rails db:migrate

Ruby on Rails Active Storage supports declaring multiple services configuration usage, with an ability to keep multiple storage services mirrored.

The Ruby on Rails Active Storage configuration file bases on two special keys in order to synchronize files between multiple storage services:

• primary accepting the predefined service name as a value,
• mirrors accepting an array of predefined service names as a value,

This is especially useful in order to safely migrate between services in the production environment of the Ruby on Rails application with zero downtime.

While configuring Ruby on Rails Active Storage in your application, you are going to be interested in the following files.

• config/storage.yml, the main Ruby on Rails Active Storage configuration file responsible for all services definitions,
• config/environments/development.rb,
• config/environments/test.rb,
• config/environments/production.rb.

On top of the default Ruby on Rails environments, any other environment configuration file that your application defines, such as for example config/environments/staging.rb, is going to configure the Ruby on Rails Active Storage module.

#Ruby on Rails Active Storage server disk usage configuration

Let us take a look at the most basic configuration for the Ruby on Rails Active Storage module - the simple server disk usage.

This is the default configuration that comes with Ruby on Rails project intialization.

config/storage.yml

local:
  service: Disk
  root: <%= Rails.root.join("storage") %>

test:
  service: Disk
  root: <%= Rails.root.join("tmp/storage") %>

The example Ruby on Rails Active Storage file defines two services, local and development.

Both of them save files to defined Ruby on Rails application directories, let's make sure they are created in your project root.

cd /path/to/rails/app
mkdir files
mkdir -p tmp/files

This should be optional unless your Ruby on Rails application was initialized with the --skip-active-storage configuration option.

The test service takes advantage of the temporary directory, that's usually ignored by git version control in the .gitignore file.

The disk service is the one that you'd probably want to use in the development and potentially in the production environment.

It would also go to the .gitignore file, yet you wouldn't want to lose it on production - anyway, make sure its there for the development process.

.gitignore

/storage/*
/tmp/*

Let's now take a look at the Ruby on Rails Active Storage environment configuration file - let it be the test one, as it will most likely look like in most of Ruby on Rails applications.

config/environment/test.rb

config.active_storage.service = :test

This simple configuration option accepts a symbol representing the service name previously defined in the Ruby on Rails Active Storage configuration file.

In our case, it tells Ruby on Rails Active Storage module to write to the temporary files directory while running the app in the test environment.

Configuration of other environments' Ruby on Rails Active Storage module is going to look like that:

config/environment/production.rb, config/environment/development.rb

config.active_storage.service = :local

And that's pretty much it.

Continue reading in order to learn how to use third-party cloud storage services with Ruby on Rails Active Storage module.

#Ruby on Rails Active Storage Google Cloud Platform configuration

Google Cloud Platform Storage service connection is easily configurable with Ruby on Rails Active storage module.

The most difficult part of the process is not Ruby on Rails code-related - yet still worth automating with Hix on Rails - but the whole setup on the Google Cloud Platform part.

Let's get through it.

#GCP account setup and bucket creation

In order to use Google Cloud Storage with Ruby on Rails Active Storage module, we need to create an account first. Follow these steps in order to do that.

1. On the official Google Cloud Storage website page, click "Try it free".

2. You will be asked to log into your Google account. Do that, or create one if you don't have it.
3. In the first step of Google Cloud account creation, confirm that Google guessed your country of origin correctly and accept the terms and conditions.

4. In the second step, sell your soul to Google providing your address and credit card information. You might choose between an "Individual" and "Business" accounts here, too.

5. Click "Start my free trial", and on the next page click the "Got it" button in the welcome popup.

You are now on your Google Cloud Platform dashboard dedicated to Storage management. By default, Google Cloud Platform creates an entity called "My First Project".

For the purposes of this guide, we are going to use it, but in your Ruby on Rails production projects, it's worth creating a project with a more meaningful name than that.

1. Click the "Create bucket", and then close the popup window by clicking the "Got it" button.

2. In the first step of the bucket creation, provide its name - if not sure, go through the bucket naming guidelines - and then click "Continue". Keep your bucket name in mind in order to connect to it via Ruby on Rails Active Storage module.

3. In the next step, select storage location best matching your Ruby on Rails application audience, then click "Continue".

4. Depending on your need, select the storage data class - it defines how often your files are going to be accessed. Then, click "Continue".

5. In the access control step, it is best to leave it as-is if in doubt.

6. The rest of the configuration is optional - click "Continue" in order to review it, and then click the "Create" button.

Now that we've created the Google Cloud Platform account and our first bucket in the Storage service, let's get through the authorization part.

#GCP storage credentials

Follow the credentials generation process in order to authorize Ruby on Rails Active Storage to connect to Google Cloud Storage.

1. Go to the Google Cloud service account management website.
2. Click the "Open the IAM & Admin page" button.

3. Click "Select a project", choose a project, and click "Open".
4. In the left-hand sidebar, navigate to "Service accounts" page.

5. On the service accounts page, click the "Create service account" button.

6. Provide service account name. The ID is autogenerated from the name, and description is optional. Click the "Create" button.

7. Optionally set the service account permissions to Storage Admin. Then, click the "Continue" button.

8. In the next step, click the "Create key" button.

9. In the right-hand sidebar, select JSON option and click "Create".

10. The private key was downloaded. Save it for further usage in the Ruby on Rails Active Storage configuration.

Now that we've successfully obtained the Google Cloud Storage JSON credentials private key, let's connect our Ruby on Rails Active Storage using it.

#GCP Rails configuration

For Ruby on Rails Active Storage to work with Google Cloud Storage there's a dedicated gem required to be installed.

Add the following to your Ruby on Rails application Gemfile file.

Gemfile

gem 'google-cloud-storage'

Next, open the downloaded Google Cloud Storage JSON file with a text editor of your choice.

keyfile.json

{
  "type": "service_account",
  "project_id": "40hallowed-ridge-264013",
  "private_key_id": "32976f16b04ece6a6fb8bc3bb4c52ea48f738bb8",
  "private_key": "-----BEGIN PRIVATE KEY-----\n<.....>\n-----END PRIVATE KEY-----\n",
  "client_email": "hix-on-rails@40hallowed-ridge-264013.iam.gserviceaccount.com",
  "client_id": "102135739378581270686",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/hix-on-rails%40hallowed-ridge-264013.iam.gserviceaccount.com"
}

Ruby on Rails Active Storage supports two types of configuration for the Google Cloud Storage service.

The first way to configure Ruby on Rails Active Storage to connect with your Google Cloud Storage bucket is by using the credentials key, which accepts a path to the JSON credentials file stored in your Ruby on Rails application directory.

config/storage.yml

google:
  service: GCS
  credentials: <%= Rails.root.join("path/to/keyfile.json") %>
  project: "My First Project"
  bucket: "hix-on-rails-active-storage"

The second option is to pass each of the configuration options defined in the Google Cloud Storage JSON file separately.

config/storage.yml

google:
  service: GCS
  credentials:
    type: "service_account"
    project_id: "hallowed-ridge-264013"
    private_key_id: "32976f16b04ece6a6fb8bc3bb4c52ea48f738bb8"
    private_key: "-----BEGIN PRIVATE KEY-----\n<.....>\n-----END PRIVATE KEY-----\n"
    client_email: "hix-on-rails@hallowed-ridge-264013.iam.gserviceaccount.com"
    client_id: "102135709378581270686"
    auth_uri: "https://accounts.google.com/o/oauth2/auth"
    token_uri: "https://accounts.google.com/o/oauth2/token"
    auth_provider_x509_cert_url: "https://www.googleapis.com/oauth2/v1/certs"
    client_x509_cert_url: "https://www.googleapis.com/robot/v1/metadata/x509/hix-on-rails%40hallowed-ridge-264013.iam.gserviceaccount.com"
  project: "My First Project"
  bucket: "hix-on-rails-active-storage"

In both cases, it is not the best idea to keep any secrets in the version control system. Let's install the dotenv-rails gem instead and put all the configuration into the dedicated .env file.

.env

GCS_PROJECT_ID=hallowed-ridge-264013
GCS_PRIVATE_KEY_ID=32976f16b04ece6a6fb8bc3bb4c52ea48f738bb8
GCS_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\n<.....>\n-----END PRIVATE KEY-----\n"
GCS_CLIENT_EMAIL=hix-on-rails@hallowed-ridge-264013.iam.gserviceaccount.com
GCS_CLIENT_ID=102135709378581270686
GCS_AUTH_PROVIDER_X509_CERT_URL=https://www.googleapis.com/robot/v1/metadata/x509/hix-on-rails%40hallowed-ridge-264013.iam.gserviceaccount.com
GCS_PROJECT="My first project"
GCS_BUCKET=hix-on-rails-active-storage

After doing that, simply use all the environment variables in the Ruby on Rails Active Storage configuration file.

config/storage.yml

google:
  service: GCS
  credentials:
    type: "service_account"
    project_id: <%= ENV['GCS_PROJECT_ID'] %>
    private_key_id: <%= ENV['GCS_PRIVATE_KEY_ID'] %>
    private_key: <%= ENV['GCS_PRIVATE_KEY'] %>
    client_email: <%= ENV['GCS_CLIENT_EMAIL'] %>
    client_id: <%= ENV['GCS_CLIENT_ID'] %>
    auth_uri: "https://accounts.google.com/o/oauth2/auth"
    token_uri: "https://accounts.google.com/o/oauth2/token"
    auth_provider_x509_cert_url: "https://www.googleapis.com/oauth2/v1/certs"
    client_x509_cert_url: <%= ENV['GCS_CLIENT_X509_CERT_URL'] %>
  project: <%= ENV['GCS_PROJECT'] %>
  bucket: <%= ENV['GCS_BUCKET'] %>

This way your Google Cloud Storage credentials are not stored in the repository holding your Ruby on Rails application code and are less likely to get stolen.

#Ruby on Rails Active Storage AWS S3 configuration

Amazon Web Services AWS S3 storage service connection is easily configurable with Ruby on Rails Active Storage module.

The most difficult part of the configuration is the whole setup on the Amazon Web Services AWS S3 part - yet it is still worth it to automate Ruby on Rails Active Storage configuration with Hix on Rails.

Let's dive into it.

#AWS account setup

Get through the following steps in order to create your Amazon account for connecting Ruby on Rails Active Storage with the AWS S3 service.

1. Go to AWS Amazon S3 official website and click "Get Started with Amazon S3" button.

2. Click the "Create new account" button. If you have an account already, you can skip the rest of these steps.

3. Provide your account email, password and name. Then click the "Continue" button.

4. Sell your soul to Amazon providing your full name and address data. At this point it is possible to create either "Personal" or "Business" account. Then click the "Create account and continue" button.

5. Provide your Credit Card information and click the "Verify and Add" button.

6. Select the country and provide your phone number in order to get the verification code. Fill up the security check input, then click the "Send SMS" button.

7. Wait for the SMS message and enter your verification code, then click the "Verify code" button.

8. In the successful verification popup, click the "Continue" button.

9. Select your support plan. It's good to start for free and upgrade it as you need.

10. Click the "Sign in to the Console" button.

Now that you've created your AWS account, let's create the Amazon S3 bucket.

Follow the steps below in order to do that.

1. Sign in to the AWS Management Console providing email and password to your account.

2. Click the "Services" dropdown in the navigation bar and navigate to the "Storage / S3" page.

3. In the S3 dashboard, click the "Create bucket" button.

4. Enter your bucket name and select its region - it is important to remember for further Ruby on Rails Active Storage configuration. Then, click the "Next" button.

5. Browse through the S3 bucket configuration options. Then click the "Next" button.

6. Adjust your S3 bucket permissions settings, they can be changed later if needed. When done, click the "Next" button.

7. In the final step, review all the information provided, then click the "Create bucket" button.

The last step for Ruby on Rails Active Storage module towards accessing your Amazon AWS S3 bucket is obtaining your account credentials.

Let's see how to do that.

#AWS storage credentials

With regard to the AWS Best Practices, we are going to create a special user for our Ruby on Rails Active Storage module, with access specifically set to the Amazon AWS S3 service only.

The Amazon access can be modified at any point for given users.

Follow the steps below.

1. In the AWS S3 dashboard, click your account dropdown and "My Security Credentials" link.

2. In the popup, click the "Get Started with IAM Users" button.

3. In the Identity and Access Management dashboard, click the "Add user" button.

4. Enter the user name and password, and allow programmatic and AWS Management Console access. Do not require a password change. Then, click the "Next: Permissions" button.

5. Click the "Attach existing policies directly" tile, then search for "S3" and check the "AmazonS3FullAccess" option.

6. Optionally, add user tags. When done, click the "Next: Review" button.

7. Review the new user, then click the "Create user" button.

8. Copy your "Access key ID" and "Secret access key".

9. At this point, it is also good to backup your access keys CSV file safely, just in case.

Now that we've obtained Amazon AWS S3 credentials, let's finalize connecting the Ruby on Rails Active Storage module to our freshly created AWS S3 bucket.

#AWS Rails configuration

Ruby on Rails Active Storage module is able to connect with your Amazon AWS S3 service thanks to aws-sdk-s3 gem.

Open your project's Gemfile file and add the following.

gem 'aws-sdk-s3'

Now, let's get to the Ruby on Rails Active Storage configuration.

Browse a full list of AWS regions in order to find your S3 bucket region code.

config/storage.yml

s3:
  service: S3
  access_key_id: "AKIAIOSFODNN7EXAMPLE"
  secret_access_key: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
  region: "eu-west-2"
  bucket: "hix-on-rails"

Adjust the Ruby on Rails Active Storage configuration file with your Amazon AWS S3 credentials.

A better way to store Ruby on Rails application credentials is by using the dotenv-rails gem. After installing it, create the .env file and add the following.

.env

AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
AWS_BUCKET=hix-on-rails
AWS_REGION=eu-west-2

The next step is to load those environment variables into the Ruby on Rails Active Storage configuration file.

config/storage.yml

s3:
  service: S3
  access_key_id: <%= ENV['AWS_ACCESS_KEY'] %>
  secret_access_key: <%= ENV['AWS_SECRET_ACCESS_KEY'] %>
  region: <%= ENV['AWS_REGION'] %>
  bucket: <%= ENV['AWS_BUCKET'] %>

This way you don't store any secrets in your Ruby on Rails project's version control system - other supported ways to achieve the same goal are using different configuration methods of the AWS Ruby SDK package.

#Ruby on Rails Active Storage Microsoft Azure Cloud configuration

Microsoft Azure Blob Storage service connection is easily configurable with Ruby on Rails Active Storage module.

Once you get through the Microsoft Azure Blob Storage account creation and setup, it is worth to automate the Ruby on Rails Active Storage configuration with Hix on Rails.

Let's rock.

#Azure account setup

For Ruby on Rails Active Storage to work with Microsoft Azure Storage, the Microsoft account and Microsoft Azure account are needed.

Follow the steps below in order to create a Microsoft account.

1. Visit the Microsoft Azure Storage website and click the "Start free" button.

2. On the next page, click the "Start free" button.

3. Provide your account email, then click the "Next" button.

4. Provide your account password, then click the "Next" button.

5. Provide your country and birth date, then click the "Next" button.

6. Go to your email account, copy and paste the verification code. Then click the "Next" button.

Now that we have created the Microsoft account, we are going to create the Microsoft Azure account related to it.

You should be redirected to the form presented below.

1. Provide your basic credentials - country, first and last name, email, phone number and optionally your company VAT ID. Then click the "Next" button.

2. After entering your phone number, click the "Text me" button.

3. Wait for the SMS message and enter the code received. Wait for the verification to complete and click the "Next button".

4. Sell your soul to Microsoft providing all the necessary billing data. Then click the "Next" button.

5. Check the required agreements and click the "Sign up" button.

That's it, both Microsoft accounts required by Ruby on Rails Active Storage are ready to use.

In the new account, let's create the "Storage account" and an entity that's specific to Azure, called "Container", which is an equivalent to AWS S3 and Google Cloud Storage "Bucket".

1. Click the "Go to portal" button.

2. Skip the Azure usage wizard for now by clicking "Maybe later" button in the popup.

3. In the top-left corner open the hamburger menu and navigate to the "Storage accounts" page.

4. Click the "Create storage account" button.

5. Provide account name, select its location and optionally browse through all the configuration tabs. Then click the "Review + Create" button.

6. Wait for the account validation, then click the "Create" button.

7. Wait for the container to be created - it will take up to 5 minutes. Then click the "Go to resource" button.

8. Click the "Containers" tile.

9. Click the "+ Container" link, provide your container data and click the "OK" button.

With all this in place, let's collect the final piece required for Ruby on Rails Active Storage to work with our Microsoft Azure account.

#Azure storage credentials

The last step toward working Ruby on Rails Active Storage module reading and writing files to our Microsoft Azure Storage service is obtaining its credentials.

In order to do that, in the left-hand sidebar "Settings" section navigate to the first section named "Access keys".

Leave this page open for the Ruby on Rails Active Storage configuration described in the next step.

#Azure Rails configuration

In order to work, Ruby on Rails Active Storage requires the dedicated gem.

Open your Gemfile and add the following.

gem 'azure-storage-blob'

The next step is to edit the Ruby on Rails Active Storage configuration file.

config/storage.yml

azure:
  service: AzureStorage
  storage_account_name: "hixonrails"
  storage_access_key: "12id12dni1ksld1niodnio1dn1opdm1skdm1idmop1wm1pdm1pd1"
  container: "activestorage"

The more secure way to store your Microsoft Azure Storage credentials is to use dotenv-rails gem instead of keeping them in the Ruby on Rails Active Storage configuration file, which is checked into the git version control system.

.env

AZURE_STORAGE_ACCOUNT_NAME=hixonrails
AZURE_STORAGE_ACCESS_KEY=12id12dni1ksld1niodnio1dn1opdm1skdm1idmop1wm1pdm1pd1
AZURE_STORAGE_CONTAINER=activestorage

With this saved, edit the Ruby on Rails Active Storage configuration file.

config/storage.yml

azure:
  service: AzureStorage
  storage_account_name: <%= ENV['AZURE_STORAGE_ACCOUNT_NAME'] %>
  storage_access_key: <%= ENV['AZURE_STORAGE_ACCESS_KEY'] %>
  container: <%= ENV['AZURE_STORAGE_CONTAINER'] %>

This way your Ruby on Rails application is one step closer to respect Twelve-Factor App methodology.

#Conclusion

Ruby on Rails Active Storage configuration is as easy as it gets - all you need to do is filling your access data to the Cloud Storage provider of your choice.

It gets even easier if you decide that your Ruby on Rails Active Storage module is going to store the files on your server's disk.

The difficult, yet in case of most of the organizations one-time part of the Ruby on Rails Active Storage configuration is the account creation and setup with the Cloud Storage provider of your choice - Amazon, Google or Microsoft.

In order to make the Ruby on Rails Active Storage configuration part even easier, consider using Hix on Rails, the Ruby on Rails Application Template that integrates the Active Storage setup in its setup wizard.