Amazon S3 vs Obstor

Amazon S3 is an object storage service for storing, managing, analyzing, and protecting data used by data lakes, cloud-native applications, and mobile apps. Capacity adjusts as objects are added or removed, without requiring storage to be provisioned in advance. Storage classes cover frequent access, infrequent access, and archiving. Versioning preserves object versions, while Replication can copy objects to buckets in the same or different AWS Regions. Amazon Athena and Redshift Spectrum can query S3 data in place with SQL; S3 Vectors adds vector storage and querying, including integration with Amazon Bedrock Knowledge Bases. Security controls include encryption for uploads, Block Public Access, and Object Lock for customer-defined retention periods. AWS documents access through its Management Console, CLI, SDKs, and REST API. S3 is listed for Android, API, iOS, Linux, macOS, web, and Windows. A Free Tier is available. Pricing is usage-based, with charges varying across storage, requests, retrieval, transfer, and other features. Some archived objects have minimum storage durations of 90 or 180 days, and early deletion incurs a prorated charge.

Obstor is an Apache 2.0-licensed, S3-compatible object storage server with built-in SFTP support. It works with S3 SDKs, command-line tools, and applications without code changes. In distributed deployments, objects are sharded and replicated across connected nodes, with each object kept in at least two global locations. Its native SFTP server stores uploaded files as S3 objects. Data features include SSE-C and SSE-S3 server-side encryption with KMS integration, configurable erasure coding for drive and node failures, and object versioning with lifecycle policies. IAM controls use users, groups, policies, and service accounts with S3 and AWS IAM policy syntax. Event notifications can be sent to Kafka, NATS, AMQP, Redis, PostgreSQL, Elasticsearch, and webhooks. Installation options include a single binary, Docker, a Kubernetes Helm chart, or building from source. Standalone instructions cover macOS, GNU/Linux, and 64-bit Windows. Standalone servers are intended for development and evaluation; versioning, object locking, and bucket replication require distributed deployment with erasure coding.