A large uploads directory can make a website’s server look bigger than its application needs. Object storage holds files separately from the web server; a content delivery network, or CDN, can deliver them closer to visitors. That can help, but it does not automatically produce a smaller bill.
First separate three decisions: where the files belong, how the application uses them, and what server capacity remains necessary. Make each one reviewable. Keep local originals until you have demonstrated that the new arrangement works and recovery is possible.
1. Measure the files and their purpose
Inventory original images, generated sizes, video, private documents and temporary files. Record counts and total sizes, then identify which folders the application expects to read locally. A directory called uploads is not evidence that every file in it is public.
Look at growth and working space too. Image processing can need temporary space even after published media moves. Keep room for logs, updates, database work and recovery tasks. Removing today’s media does not mean the remaining used space is a safe disk size.
2. Draw the delivery and access boundaries
| Request or responsibility | Before | Proposed after |
|---|---|---|
| Public image | Browser → application server → local file | Browser → CloudFront → private S3 origin on a cache miss |
| Application page | Browser → application server | Browser → application server; no automatic compute reduction |
| Protected document | Application checks viewer permission | Separate protected path; viewer authorisation still required |
| Recovery | Server data and configuration backups | Application recovery plus media versions and a tested backup route |
This is a fictional architecture, not a measured performance result. CloudFront’s origin access control can let a distribution read a private S3 origin. The bucket policy must match the intended distribution and content scope; see AWS guidance on restricting the S3 origin.
Origin access is separate from permission to view a file. If CloudFront serves an object publicly, a private bucket does not make that object private to visitors. Protected downloads need an appropriate viewer access mechanism, such as the authenticated application issuing signed URLs described in CloudFront’s private-content guidance.
Decide which system uploads, updates and removes media, and how it authenticates. Keep permissions limited to the intended content. Choose the actual integration before writing a migration script; there is no universal WordPress offload behaviour to assume.
3. Prove application compatibility and the copy
Use a staging copy to test the selected plugin or integration against its own documentation. Check original uploads, generated sizes, image editing, attachment metadata, galleries, feeds and any shop or membership features. Include multisite paths if the installation uses them.
Copy first, then verify an inventory of expected files. Compare supported checksums or actual downloaded content where needed. File size alone is not proof that two files are identical, and a generic object identifier should not be assumed to be a content checksum.
Keep track of uploads and edits that happen during the copy. Plan the final catch-up, a controlled cutover and a rollback window. Test old bookmarked URLs and files requested by search engines as well as fresh pages. Avoid blanket database replacement before understanding the application’s stored data and URL handling.
Check authorisation failures deliberately. An unauthenticated visitor should not gain access to protected documents through either the new CDN address or the origin. Test invalidation and versioned URLs so an updated image does not leave visitors seeing an obsolete copy.
4. Price the whole delivery path
Build a worksheet for storage, object requests, delivery, cache misses, logs and recovery copies. The S3 pricing page and CloudFront pricing page are separate inputs. Compare the applicable plan and region, and do not add a bundle allowance to unrelated usage.
Include migration overlap and any integration licence. An existing CDN contract may remain payable after the move. A reduction in server bandwidth is useful evidence, but it is not the same as a cash saving if the original capacity or contract still costs the same.
Keep traffic assumptions consistent. Compare the same media volume, request mix and visitor geography. If growth is uncertain, calculate a small and large usage case. Leave an unknown cost visibly unresolved rather than entering zero to finish the spreadsheet.
5. Reduce capacity only after measurement
Deleting files does not shrink a provisioned EBS volume’s bill. AWS bills storage capacity as described in EBS pricing, and Elastic Volumes cannot reduce an existing volume’s size. A smaller disk requires a separate migration to a suitable replacement.
Likewise, less media traffic does not prove that CPU or memory can be halved. Measure busy customer journeys, background jobs and a cold cache after offload. Choose a replacement size from those results and keep a tested rollback path.
Only count the disk or server saving once that change has been made and verified. If you later buy a commitment, calculate it from the new eligible usage. Do not add the old server’s full discount to savings already attributed to its replacement.
What can go wrong?
A gallery may load while image editing fails because it needs local originals. A private document may become public through the CDN. A copy may miss files written during migration. Keeping a verified inventory, controlled access tests and a clear rollback window addresses different risks; no single green check covers them all.
Proceed, investigate or keep?
- Proceed: files and access are verified, the integration passes representative tests, and the full cost comparison supports the change.
- Investigate: local-file dependencies, protected content or new delivery charges remain unclear.
- Keep: a local copy is still required by the application or the recovery plan.
Before the later server decision, read the EC2 capacity checks. For image-processing risks, see why image regeneration needs a recovery path.
Continue the AWS review
If you are reviewing your website’s hosting, tell AceMedia Host what you need.