How to Connect IDrive e2 to WordPress with Arewa S3 Media Library

Are you looking for a way to connect IDrive e2 cloud storage to WordPress, reduce hosting disk usage, and manage your media files more efficiently?

Arewa S3 Media Library allows you to integrate IDrive e2 with WordPress using its S3-compatible API. You can upload new media to the cloud, copy existing WordPress files, manage multiple buckets, configure public or private delivery, and browse cloud files directly from your WordPress dashboard.

In this tutorial, you’ll learn how to create an IDrive e2 bucket, generate S3 API credentials, find your storage endpoint and region, connect IDrive e2 to Arewa S3 Media Library, configure media offloading, and set up a custom domain using IDrive e2 CNAME settings.

1. What You’ll Need

Before starting, make sure you have:

• A WordPress website.
• The Arewa S3 Media Library plugin installed and activated.
• An active IDrive e2 account.
• Permission to create storage buckets and S3 access keys.
• An optional custom domain for media delivery.
• Access to your domain’s DNS settings if you plan to configure a custom domain.

IDrive e2 is an S3-compatible object storage service that can store images, videos, documents, and other WordPress media files.

2. Create an IDrive e2 Account

Visit the official IDrive e2 website and create an account.

After signing in, open the IDrive e2 management dashboard.

From here, you can manage storage regions, create buckets, generate API credentials, and configure custom domains.

Choose Your Storage Region

• IDrive e2 offers storage locations in different geographical regions.
• Choose a location appropriate for your website’s audience, storage requirements, and expected access patterns.
• For example, if your website serves European visitors, you may prefer an available European storage location.
• Important: Your bucket’s region and S3 endpoint are essential when connecting IDrive e2 to Arewa S3 Media Library.
• Unlike the Backblaze B2 connection workflow, the IDrive e2 provider requires you to enter both values manually.

3. Create an IDrive e2 Bucket

From the IDrive e2 dashboard:

1. Open the Buckets section.
2. Click the option to create a new bucket.
3. Enter a unique bucket name.
4. Select the storage region or location.
5. Choose the bucket’s access settings.
6. Complete the bucket creation process.

Example bucket name:

wordpress-media

Public and Private Buckets

• You can configure storage according to the intended use of your files.
• Public media: Suitable for website images, thumbnails, and other files intended for unrestricted access.
• Private media: Suitable for protected downloads, private documents, and files that require temporary signed URLs.
• For websites with protected content, a private bucket is generally the better starting point.
• If you need both public and private files, consider using separate buckets.

4. Find Your IDrive e2 S3 Endpoint and Region

• This is one of the most important steps.
• Arewa S3 Media Library requires two manually entered values for IDrive e2:

• IDrive e2 S3 endpoint
• Region

• Open your IDrive e2 dashboard and locate the S3 connection details for your bucket or storage location.
• Copy the endpoint exactly as displayed.
• The endpoint will generally be an HTTPS address associated with your IDrive e2 storage location.
• For the region, use the region identifier shown in your dashboard.
• Example:
• eu-west-3
• This is only an example. Your actual region may be different.
• Do not assume that the region name and endpoint can be inferred from each other.
• Important: Unlike Backblaze B2, Arewa S3 Media Library does not automatically detect the IDrive e2 endpoint and region during the initial connection. You must supply both values.

5. Generate IDrive e2 S3 API Credentials

To connect IDrive e2 to WordPress, you need:

• Access Key ID
• Secret Access Key

In your IDrive e2 dashboard, open the section for managing S3 access keys or API credentials.

Create a new key with access to the bucket you want to use.

For full media-management functionality, the credentials need permissions appropriate for listing, reading, uploading, and deleting objects.

Use restricted credentials where supported rather than giving the plugin unnecessary access to unrelated buckets.

Save Your API Credentials

After generating the credentials, securely copy the Access Key ID and Secret Access Key.

You will enter them in Arewa S3 Media Library.

Do not publish these credentials, include them in screenshots, or expose them in frontend JavaScript.

6. Open Arewa S3 Media Library in WordPress

Sign in to your WordPress dashboard.

Navigate to:

Media → Arewa S3 Media → Connections

Click:

Add Connection

The plugin displays the Add Storage Connection form.

Enter a Connection Name

In Connection name, enter:

IDrive e2

You can use another descriptive name if you manage multiple IDrive e2 storage accounts.

Select the Storage Provider

Open the Provider dropdown and choose:

IDrive e2

The plugin displays the fields required for this provider.

7. Connect IDrive e2 Using the S3 API

Complete the connection form using your IDrive e2 credentials.

Make sure your endpoint and region match the bucket you intend to use.

Connect Your Account

After entering all the required information, click:

Connect

Arewa S3 Media Library attempts to authenticate with your IDrive e2 account using the S3-compatible API.

If the connection succeeds, the plugin loads the accessible buckets.

For security, the plugin may clear the visible credential fields after accepting the connection details.

This does not mean your saved credentials have been lost.

8. Select and Verify Your IDrive e2 Bucket

After connecting, select the bucket you want to use for WordPress media.

The plugin provides bucket-selection and verification controls.

1. Open the Bucket dropdown.
2. Select your IDrive e2 bucket.
3. Click Verify selected bucket.
4. Wait for the verification result.

You can also use Refresh Buckets or Verify checked buckets when multiple accessible buckets are available.

Why Is Bucket Verification Important?

Bucket verification helps confirm that the credentials, endpoint, region, and bucket settings are compatible with the requested storage operations.

If verification fails, check:

• The S3 endpoint.
• The region identifier.
• Your Access Key ID.
• Your Secret Access Key.
• Bucket permissions.
• Network connectivity.

Do not continue with media migration until the connection is working correctly.

9. Configure the Storage Mode

After selecting and verifying your bucket, configure how WordPress media should be stored.

Arewa S3 Media Library provides three options.

Local

Media remains stored locally on your WordPress hosting server.

New uploads are not automatically copied to IDrive e2.

Choose this option when you want to retain traditional WordPress storage behavior.

Copy to Cloud

New WordPress media is copied to IDrive e2 while the original local files remain available.

This mode is useful when you want to:

• Maintain local originals.
• Keep additional copies in cloud storage.
• Test IDrive e2 before switching to cloud-focused storage.
• Preserve an additional layer of media availability.

Cloud Only

• This mode is intended for websites that want to use IDrive e2 as their primary media storage destination.
• The plugin copies media to cloud storage while retaining local files initially for verification.
• Once the cloud copies have been verified, you can use the plugin’s cleanup tools to remove eligible local files.
• Important: Cloud Only does not require you to delete local files manually immediately after upload.
• Always verify your cloud copies before performing cleanup.

10. Configure Public or Private Media Delivery

Arewa S3 Media Library provides three delivery options.

Public URL

• Select Public URL when your media should be accessible without authentication.
• This option is suitable for public images, website thumbnails, and unrestricted downloads.
• The bucket and delivery endpoint must allow public access to the relevant files.

Signed URL for Anyone With the Link

• This option generates temporary signed URLs for private files.
• Anyone with a valid, unexpired signed link may access the corresponding object.
• It is useful for temporary sharing, but the link itself acts as a bearer credential.

Signed URL for Authorized Users

• This mode is intended for protected WordPress media.
• The plugin checks authorization before generating or delivering access to the private object.
• It is suitable for membership websites and other applications where access depends on WordPress user permissions.
• For protected content, use a private bucket and test the authorization behavior before deploying it to production.

11. Configure the Public / CDN Domain

• Arewa S3 Media Library includes a Public / CDN domain field.
• This allows you to configure a custom media delivery address when your storage provider and domain setup support it.
• For example:

• You can leave this field empty to use the storage endpoint.
• A custom domain must be correctly configured before using it for public media delivery.
• Later in this tutorial, we’ll explain how IDrive e2’s CNAME configuration differs from Backblaze B2.

12. Select the Default Offload Bucket

• Under Default Offload Bucket, choose the IDrive e2 bucket that should receive new WordPress media uploads.
• For example:
• wordpress-media
• The default storage connection determines where new offloaded media is sent.
• Changing the default connection does not automatically migrate previously uploaded files.
• After completing the settings, click:
• Save Connection
• Your IDrive e2 connection is now ready for use.

13. Copy Existing WordPress Media to IDrive e2

• If your WordPress website already contains images, videos, or documents, you can copy eligible existing media to IDrive e2.
• Navigate to:
• Media → Arewa S3 Media → Offload
• Locate the section:
• Copy existing WordPress media
• Click:
• Start existing-media batch
• The plugin scans WordPress attachments and submits eligible media for background copying.

What Happens During the Transfer?

Arewa S3 Media Library processes eligible media files and their generated image sizes according to the selected destination.

The dashboard displays transfer progress and status information.

You may see:

• Scanned attachments.
• Queued files.
• Verified copies.
• Skipped items.
• Missing originals.
• Scan errors.

Allow the transfer to finish before performing local cleanup.

Note: The existing-media batch uses the current default storage destination.

14. Copy WordPress Media to an Additional Cloud

Arewa S3 Media Library also supports additional cloud storage destinations.

For example, you could use IDrive e2 as your primary storage and Backblaze B2 as an additional copy destination.

In the Offload page, find:

Copy WordPress media to another cloud

Then:

1. Open Copy destination.
2. Select the additional cloud connection.
3. Click Start additional cloud copy.
4. Wait for the operation to finish.
5. Verify the copied files.

This allows you to maintain media copies across multiple cloud providers without automatically replacing your default storage connection.

15. Synchronize and Verify IDrive e2 Media

After copying your files, open the Synchronization section of the Offload page.

Click:

Sync / Verify Cloud

The plugin checks the media associated with the current default cloud connection.

It reports information such as:

• Verified in cloud
• Missing from cloud
• Waiting to copy

Repair Missing Files

If the verification report identifies missing cloud objects, you can use:

Repair Missing Objects

This feature checks eligible missing files and attempts to upload them when suitable local copies are available.

Review Media Status

Scroll down to the Media status section.

Each attachment displays its current cloud-copy status.

For example:

Synced: The expected cloud copy has been verified.

Missing everywhere: The expected file is not available in the checked locations.

Resolve missing-file problems before removing local originals.

16. Remove Verified Local Files to Save Hosting Space

If you selected Cloud Only, you can reduce hosting disk usage after successful cloud verification.

In the Offload page, find:

Remove verified media

Before using it:

1. Finish the media transfer.
2. Run Sync / Verify Cloud.
3. Confirm that the required files are verified.
4. Test your website images and downloads.
5. Keep a separate backup of important media.
6. Click Remove verified media.

The plugin checks eligible local files before cleanup and preserves the WordPress media records and references according to its cloud-retention workflow.

Warning: Do not use this cleanup feature with the expectation that cloud storage is automatically a complete backup solution. Maintain an independent recovery strategy.

17. Browse IDrive e2 Files from WordPress

• Arewa S3 Media Library includes a cloud file browser.
• Navigate to:
• Media → Arewa S3 Media → Library → Cloud Files
• Choose your IDrive e2 connection and select the desired bucket.

All Files

The All Files view allows you to browse cloud objects using a media-library-style interface.

Available features include:

• File thumbnails.
• Search.
• File types and sizes.
• Sorting.
• Grid and list views.
• Pagination.

By Folders

Choose By Folders to explore objects according to their folder-style paths.

This is useful for large cloud media collections.

The Cloud Files interface helps you manage and explore remote storage directly from WordPress.

18. Configure a Custom Domain with IDrive e2

IDrive e2 provides a CNAME configuration feature for connecting a custom domain to a storage region.

This is one of the main differences between IDrive e2 and the Backblaze B2 CDN workflow.

With Backblaze B2, a common Cloudflare setup uses a DNS CNAME and URL rewriting for the provider’s public download path.

With IDrive e2, the dashboard also provides a region-level CNAME configuration that includes certificate and private-key fields.

18.1 Open IDrive e2 Region Settings

• Sign in to your IDrive e2 dashboard.
• Locate the region where your bucket is stored.
• Open its region settings.
• For example:

Region settings (London-2)

The region settings panel contains a CNAME section.

You may see information such as:

• Number of buckets.
• Storage usage.
• Total objects.
• Existing CNAME records.

18.2 Add a CNAME Record

In the region settings panel, click:

Add CNAME

The configuration form includes:

CNAME

Enter the fully qualified hostname you want to use.

Example:

media.example.com

Index File (optional)

You may leave this empty for ordinary media delivery.

The index-file setting is more relevant when serving website-style content.

18.3 Configure SSL/TLS

The IDrive e2 CNAME form shown in the dashboard includes:

• Certificate (preferably fullchain)
• Private Key
• Passphrase (optional)

These fields are used for the TLS certificate configuration associated with the custom domain.

Use a valid certificate issued for your hostname and its corresponding private key.

If the certificate uses a passphrase, provide it where required.

Security warning: Your TLS private key is sensitive. Do not share it in support tickets, screenshots, public repositories, or documentation.

If you prefer not to upload your TLS private key to the storage provider, consider using a compatible Cloudflare proxy or another HTTPS delivery architecture instead.

18.4 Configure DNS in Cloudflare

Open the Cloudflare dashboard and select your domain.

Navigate to:

DNS → Records → Add record

Create the DNS record required by your IDrive e2 custom-domain configuration.

Example:

Use the exact CNAME target specified by IDrive e2 for your region and custom-domain configuration.

Do not invent a target or assume that the S3 API endpoint is necessarily the correct CNAME destination.

For initial validation, DNS-only mode can make it easier to confirm that the IDrive e2 custom-domain configuration works independently.

If you later enable Cloudflare proxying, verify HTTPS, cache behavior, and file access again.

18.5 Verify the Custom Domain

After completing the provider-side CNAME setup and DNS configuration, test a public object through your custom hostname.

Example:

https://media.example.com/wordpress-media/example.webp

The exact path depends on how IDrive e2 maps buckets and object keys through the configured hostname.

Test the real object path before entering the delivery domain in WordPress.

18.6 Add the Custom Domain to Arewa S3 Media Library

Return to WordPress:

Media → Arewa S3 Media → Connections

Edit your IDrive e2 connection.

Locate:

Public / CDN domain

Enter the working custom-domain base URL.

For example:

Use the actual base path required by your IDrive e2 configuration.

Save the connection.

Upload a test image and verify that its generated public URL resolves correctly.

19. Optional: Use Cloudflare as a CDN

A custom domain alone does not necessarily mean Cloudflare is caching your media.

To use Cloudflare’s reverse-proxy CDN features, the hostname must be proxied through Cloudflare and the origin configuration must be compatible.

Enable Cloudflare Proxying

Once the IDrive e2 custom domain is working, you can evaluate enabling the orange-cloud proxy for the corresponding DNS record.

Before doing so, confirm that:

• IDrive e2 accepts requests for the custom hostname.
• The origin supports the required HTTPS configuration.
• The certificate is valid for the hostname.
• The bucket and object paths resolve correctly.
• Public files can be downloaded without authentication.

Use Full (Strict) SSL/TLS mode when the origin presents a valid trusted certificate.

Configure Caching

Open:

Cloudflare → Caching → Cache Rules

Create an appropriate rule for your public media hostname if you need custom caching behavior.

For example, you can configure caching for public images that do not change frequently.

Do not apply public CDN caching to protected files or responses containing user-specific information.

Cloudflare caching depends on the response headers, file type, and applicable rules.

Important: Private Signed URLs

Private S3 signed URLs are not interchangeable with ordinary public CDN URLs.

The signature is calculated using specific request details, including the hostname.

Changing the hostname of an already-signed URL may invalidate its signature.

For private media, use the plugin’s supported signed-delivery endpoint unless you have implemented and verified a compatible authenticated CDN or proxy.

Do not expose S3 access keys or secret keys in Cloudflare page rules or public JavaScript.

20. Troubleshooting Common IDrive e2 Problems

Connection Failed

Check the following values:

• S3 endpoint.
• Region.
• Access Key ID.
• Secret Access Key.

Make sure the endpoint and region correspond to the storage location you are using.

No Buckets Found

Verify that your credentials can list the required buckets.

If your credentials are restricted, check their scope and use the plugin’s manual bucket configuration where appropriate.

Access Denied

Confirm that your API credentials have the necessary object and bucket permissions.

Also verify that you are accessing the correct bucket.

Images Return 403 Forbidden

Check whether your bucket is public or private.

Public URL delivery requires public access to the relevant objects.

Private delivery requires a valid authorized or signed request.

Custom Domain Does Not Work

Verify the CNAME configuration in IDrive e2 and the corresponding DNS record.

Check that the certificate matches your hostname and that the expected bucket/object path is correct.

Cloudflare Returns an SSL Error

Check the origin certificate, the Cloudflare SSL/TLS mode, and whether IDrive e2 supports the configured hostname.

Signed URLs Fail Through Cloudflare

Avoid changing the hostname of already-signed S3 URLs.

Use the original signed endpoint or a properly designed authenticated proxy.

Missing Cloud Files

Run:

Sync / Verify Cloud

Review the media status report and use Repair Missing Objects when eligible local files are available.

21. IDrive e2 vs. Backblaze B2 in Arewa S3 Media Library

Both services provide S3-compatible object storage, but their connection workflows differ.

These differences describe the connection workflows supported by Arewa S3 Media Library, not every configuration available from the storage providers themselves.

22. Final Setup Checklist

Before completing your integration, verify:

• IDrive e2 account created.
• Storage bucket created.
• S3 endpoint copied.
• Region copied.
• Access Key ID and Secret Access Key generated.
• IDrive e2 selected in Arewa S3 Media Library.
• Connection authenticated.
• Bucket selected and verified.
• Storage mode configured.
• Delivery method selected.
• Default Offload Bucket configured.
• Connection saved.
• Existing media copied, if needed.
• Cloud synchronization completed.
• Media status reviewed.
• Verified local cleanup performed only when appropriate.
• Cloud Files library tested.
• Custom domain and Cloudflare tested, if enabled.

Conclusion

Connecting IDrive e2 to WordPress with Arewa S3 Media Library provides a flexible way to manage media storage outside your hosting server.

You can copy existing WordPress uploads, automatically offload new media, keep additional cloud copies, configure private signed delivery, and browse your cloud files from a familiar WordPress interface.

IDrive e2 also provides custom-domain capabilities through its region-level CNAME configuration, giving you additional options for public media delivery.

With Arewa S3 Media Library, you can bring your WordPress media library and S3-compatible cloud storage together in one place.

Start using Arewa S3 Media Library to connect WordPress to IDrive e2 and simplify your cloud media management.