W E K A
3.14
3.14
  • WEKA v3.14 Documentation
  • Weka System Overview
    • About the WEKA System
    • SSD Capacity Management
    • Filesystems, Object Stores & Filesystem Groups
    • Weka Networking
    • Data Lifecycle Management
    • Weka Client & Mount Modes
    • Glossary
  • Getting Started with Weka
    • Quick Install Guide
    • Managing the Weka System
    • CLI Overview
    • GUI Overview
    • Serving IOs with WekaFS
  • Planning & Installation
    • Prerequisites for Installation
    • Bare Metal Installation
      • Planning a Weka System Installation
      • Setting Up the Hosts
        • SR-IOV Enablement
      • Obtaining the Weka Install File
      • Weka System Installation Process Using the CLI
      • Adding Clients
    • AWS Installation
      • Self-Service Portal
      • CloudFormation Template Generator
      • Deployment Types
      • AWS Outposts Deployment
      • Supported EC2 Instance Types
      • Adding Clients
      • Auto Scaling Group
      • Troubleshooting
  • Performance
    • Testing Weka Performance
      • Test Environment Details
  • WekaFS Filesystems
    • Managing Filesystems, Object Stores & Filesystem Groups
      • Managing Object Stores
      • Managing Filesystem Groups
      • Managing Filesystems
      • Attaching/Detaching Object Stores to/from Filesystems
      • KMS Management
    • Advanced Data Lifecycle Management
      • Advanced Time-based Policies for Data Storage Location
      • Data Management in Tiered Filesystems
      • Transition Between Tiered and SSD-Only Filesystems
      • Manual fetch and release of data
    • Mounting Filesystems
    • Snapshots
    • Snap-To-Object
    • Quota Management
  • Additional Protocols
    • NFS
    • SMB
      • SMB Management Using CLIs
      • SMB Management Using the GUI
    • S3
      • S3 Cluster Management
      • S3 Buckets Management
      • S3 Users and Authentication
      • S3 Information Lifecycle Management
      • Audit S3 APIs
      • S3 Limitations
      • S3 Examples using boto3
  • Operation Guide
    • Alerts
      • List of Alerts
    • Events
      • List of Events
    • Statistics
      • List of Statistics
    • System Congestion
    • Security
      • User Management
      • Organizations
    • Expanding & Shrinking Cluster Resources
      • Expand & Shrink Overview
      • Stages in Adding a Backend Host
      • Expansion of Specific Resources
      • Shrinking a Cluster
    • Background Tasks
    • Upgrading Weka Versions
  • Billing & Licensing
    • License Overview
    • Classic License
    • Pay-As-You-Go License
  • Support
    • Prerequisites and Compatibility
    • Getting Support for Your Weka System
    • The Weka Support Cloud
    • Diagnostics CLI Command
  • Appendix
    • Weka CSI Plugin
    • External Monitoring
    • Snapshot Management
  • REST API
Powered by GitBook
On this page
  • Supported S3 APIs
  • General Limits
  • Naming Limitations
  • Buckets
  • Objects
  • Policy Limitations
  • Supported S3 Policy Actions
  • Lifecycle Configuration
  • Quotas
  1. Additional Protocols
  2. S3

S3 Limitations

This page describes limitations concerning the S3 service and protocol implementation.

Supported S3 APIs

The following standard S3 APIs are supported:

  • Bucket (HEAD/GET/PUT/DEL)

    • Including ListObjects and ListObjectsV2

  • Bucket Lifecycle (GET/PUT/DEL)

  • Bucket Policy (GET/PUT/DEL)

  • Bucket Tagging (GET/PUT/DEL)

  • Object (GET/PUT/DEL)

  • Object Tagging (GET/PUT/DEL)

  • Object Multiparts (POST Create/Complete, GET/DEL/PUT, GET Parts)

General Limits

Item

Limits

Maximum number of buckets

10000

Maximum object size

5 TiB

Maximum number of parts per upload

10000

Part numbers

1 to 10000 (inclusive)

Part size

5 MiB to 5 GiB. The last part can be < 5 MiB

Maximum number of parts returned for a list parts request

1000

Maximum number of multipart uploads returned in a list multipart uploads request

1000

User-defined metadata per object

2KB

Naming Limitations

Buckets

  • Bucket names must be between 3 and 63 characters long.

  • Bucket names can consist only of lowercase letters, numbers, dots (.), and hyphens (-).

  • Bucket names must begin and end with a letter or number.

  • Bucket names must not be formatted as IP addresses (for example, 192.168.5.4).

  • Bucket names must be unique across the cluster.

Objects

  • Object key names must be up to 1024 characters long.

  • A / prefix of an object is interpreted as a directory, and such directory segments are limited to 255 characters.

Note: It is advisable to avoid special characters that might be unsupported using protocols other than S3.

Policy Limitations

Supported S3 Policy Actions

The S3 protocol implementation supports the following policy actions:

  • s3:*

    • Note: this wildcard is supported for IAM policies but not for bucket policies

  • s3:AbortMultipartUpload

  • s3:CreateBucket

  • s3:DeleteBucket

  • s3:DeleteBucketPolicy

  • s3:DeleteObject

  • s3:GetBucketLocation

  • s3:GetBucketPolicy

  • s3:GetObject

  • s3:ListAllMyBuckets

  • s3:ListBucket

  • s3:PutBucketPolicy

  • s3:PutObject

  • s3:GetBucketTagging

  • s3:PutBucketTagging

  • s3:GetLifecycleConfiguration

  • s3:PutLifecycleConfiguration

  • s3:ListBucketMultipartUploads

  • s3:ListMultipartUploadParts

Lifecycle Configuration

Quotas

Currently, data ingested by the S3 protocol is not counted against a defined directory quota.

PreviousAudit S3 APIsNextS3 Examples using boto3

Last updated 2 years ago

Refer to . Match them to limitations in other protocols.

Weka supports the elements and definitions, with the limitation of only supporting the lifecycle Expiration action.

AWS S3 object name limitations
AWS S3 Lifecycle Configuration