This page describes the WEKA implementation of the S3 protocol.
The S3 protocol is widely used and spans many cloud-native or cloud-ready applications.
With WEKA, you can:
- Ingest data with S3, and then you can access the data with either S3 or other protocols.
- Expose existing data to S3, and migrate your application within the same data platform.
- Burst to the cloud and use new applications without migrating your data.
While gaining WEKA's scale, performance, and resiliency advantages, you can gradually move applications to S3 and access the same data through multiple protocols, POSIX, S3, SMB, NFS, and GPUDirect Storage.
The WEKA S3 is a scalable and resilient service that provides multi-protocol access to data.
You implement the S3 service by specifying a set of storage servers that run the S3 protocol and then creating a logical S3 cluster to expose the S3 service. When defining many servers that serve the S3 protocol, the S3 cluster scales to higher performance.
By integrating a round-robin DNS or a load balancer, different S3 clients can access other servers, allowing the WEKA system to scale and service thousands of clients.
The WEKA S3 service works on top of the WEKA filesystem service. Buckets are mapped to top-level directories, and objects are mapped to files. Then, the same data can be exposed with either WEKA-supported protocols.
User access to S3 APIs can be either authenticated or anonymous.
The process of gaining authenticated S3 access requires to:
- 1.Create an internal WEKA user with an S3 user role.
- 2.Add and attach an IAM policy for the S3 user. The IAM policy determines the S3 user's permissions to S3 operations and resources.
As an S3 user, you can create temporary security tokens (STS AssumeRole) or service accounts with restricted permissions.
Anonymous access to buckets/objects can be obtained by one of the following:
- Bucket policy
- Pre-signed URLs
WEKA supports two URL styles for API requests to S3 buckets: path-style and virtual-hosted-style.
The difference between the styles is subtle but significant. When using a URL to reference an object, the DNS resolution maps the subdomain name to an IP address. With the path style, the subdomain is always
s3.domain-name.com. With the virtual-hosted-style, the subdomain is specific to the bucket.
The addressing style used to construct the request is determined by the S3 client sending the request.
Data written through the S3 protocol can be encrypted at rest by setting an encrypted filesystem.
Clients' access to the service through HTTPS is provided using the same certificates that WEKA uses for other API access.
The S3 API calls can be audited using an HTTP webhook service and connecting to an application such as Splunk.
To set an audit target, use the
weka s3 cluster audit-webhook enableCLI command.