Perimattic Managed SeaweedFS - S3 Object Storage on AWS

This AMI runs SeaweedFS, the open-source distributed file and object store, as a single server on Ubuntu 24.04 LTS: the master, a volume server, the filer and the S3 gateway in one container. The container image is pinned to chrislusf/seaweedfs 4.52 and baked into the AMI, so first start does not depend on a registry. SeaweedFS is an independent project and Perimattic is not affiliated with it.

Why SeaweedFS?

SeaweedFS stores objects and files in large volume files, which keeps metadata overhead small and reads fast, and it offers an S3-compatible API so that S3 SDKs and tools such as the AWS CLI can use it with a custom endpoint. The same software can grow into a multi-server cluster.

What Perimattic adds

Pinned, tested version: the image is fixed to 4.52, not 'latest', so a rebuild never changes the application behind your back.

Only the S3 API is exposed: SeaweedFS's master (9333), volume server (8080) and filer (8888) have no authentication of their own. Here they are not published at all; only the S3 gateway is published, on the loopback interface, and only through Apache over HTTPS. S3 access and secret keys are generated per instance (24 random characters each) at first login and written to an S3 identity file that only root can read. Setup then proves that anonymous requests and wrong keys are refused and that a signed request with the generated keys can create a bucket, store an object and read it back, before the endpoint is published. There are no default or shared credentials in the image.

HTTPS: Apache is configured as a reverse proxy in front of the S3 port, with a free Let's Encrypt certificate requested for your domain with certbot.

Patched base: Ubuntu 24.04 LTS built through an automated EC2 Image Builder pipeline, with security updates applied at build time.

Storage and limits

This is one server with one copy of each object and no replication: data lives in /opt/app/data on the instance's root volume, so choose the root EBS volume size for what you will store when you launch, and take EBS snapshots for backup. SeaweedFS marks volumes read-only when less than 10 percent of the disk is free. There is no web console; administer the cluster with weed shell inside the container. Path-style S3 addressing is required.

Licence

SeaweedFS is released under the Apache License 2.0. SeaweedFS Enterprise Edition, sold separately by the project, is not included.

Getting Started Launch the AMI with a root volume sized for your data, and open ports 22, 80 and 443 SSH in and answer the setup prompts (domain and admin email) Note the S3 endpoint, access key and secret key printed at the end of setup Use them with any S3 client, for example: aws --endpoint-url https://your-domain  s3 ls

A domain name with an A record pointing at the instance is required, because the endpoint is served over HTTPS. SeaweedFS uses about 300 MB of memory when idle, so a t3.small (2 GB) is a good starting size; choose a larger instance and root volume as your data and request rate grow.

This AMI is built and supported by Perimattic.

Book a free setup consultation at https://cal.com/gaurav-pareek-perimattic/marketplace-setup-consultations  or email us at aws-support@perimattic.com .

Support Managed and supported by Perimattic, a cloud infrastructure company with 13+ years of experience serving global clients. We offer free setup assistance, custom integrations, infrastructure consulting, and 24/7 support.