---
title: Object Storage
description: "Store files as objects in buckets through an HTTP API. Good for media, backups, and CDN origins."
canonical: https://penasihathosting.com/en/hosting-wiki/object-storage
type: wiki
locale: en
updated: 2026-10-29
author: Willya Randika
---

# Object Storage

## Overview

- **Summary:** Store files as objects in buckets through an HTTP API. Good for media, backups, and CDN origins.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**Object storage** stores files as **objects** inside **buckets**, accessed through an HTTP API (usually S3-compatible). There is no hierarchical filesystem like regular folders; each object has a key, metadata, and URL.

## Hosting use cases

| Need | Suitable? |
| --- | --- |
| WordPress media library | Yes, often paired with a CDN |
| Database/file backups | Yes, as an offsite target |
| Static assets (images, video) | Yes |
| A live database | No |
| Files edited in place frequently | Not ideal |

## How it differs from block storage

Block storage is a disk attached to one server and formatted with a filesystem. Object storage is accessed over HTTP and designed for large scale. For applications that need ordinary `read/write` file access, block storage is the better fit.

## What to watch for

- **Egress cost.** Downloading data can cost more than storing it.
- **Consistency.** Some services have specific consistency behavior; read the documentation.
- **Access policy.** Public buckets can leak; use private buckets and signed URLs.
- **Versioning.** Enable it when you need protection from overwrites or accidental deletes.
- **Never put credentials in the client.** Access through the backend or temporary tokens.
- **Put a CDN in front.** For public assets, a CDN reduces latency and direct egress load.

To move WordPress media to object storage, use an S3-compatible plugin and configure public URLs or a CDN. Test uploads, deletes, and thumbnail regeneration before production. Do not move theme or plugin files to object storage; they stay in the document root. Use versioning for backup buckets and signed URLs for private files.

An upload example with the AWS CLI:

```bash
aws s3 cp ./image.jpg s3://my-bucket/media/image.jpg --acl private
```

Use `--acl private` and signed URLs for files that must not be public. For public assets, put a CDN in front of the bucket and set cache headers on the object.

## FAQ

<Accordion>
  <AccordionItem title="Can object storage be mounted as a disk?">
    Usually not like block storage. Some services offer FUSE mounts, but performance is not the same as a local disk.
  </AccordionItem>
  <AccordionItem title="Is object storage good for backups?">
    Yes, provided the bucket is private, versioning/retention is configured, and restores are tested.
  </AccordionItem>
  <AccordionItem title="What does S3-compatible mean?">
    A service that follows the Amazon S3 API, so S3 tools and libraries work with another provider's endpoint.
  </AccordionItem>
</Accordion>