Frequently Asked Questions (FAQs)
What are the usage limitations of EOS?
EOS is highly optimized for the most common scenarios. Below are the limits that you may need to account for while designing your solution with EOS.
Browser Access
| Item | Specification |
|---|
| Web browser (My Account) upload size limit | 30 MB |
API Limits
| Item | Specification |
|---|
| Max number of buckets | no-limit |
| Max number of objects per bucket | no-limit |
| Max object size | 5 TiB |
| Minimum object size | 0 B |
| Max object size per PUT operation | 5 TiB |
| Max number of parts per upload | 10,000 |
| Part size | 5 MiB to 5 GiB (Last part can be 0 B to 5 GiB) |
| Maximum number of parts returned per list parts request | 1000 |
| Maximum number of objects returned per list objects request | 1000 |
| Maximum number of multipart uploads returned per list multipart uploads request | 1000 |
API Restrictions
| Item | Specification |
|---|
| Bucket Creation | Not permitted |
CLI Restrictions
| Item | Specification |
|---|
| Bucket Creation | Not permitted |
Object Storage Data Transfer Charges
The data transfer charge of ₹3.0/GB applies only for external networks (i.e., from e2e to the public).
What's the maximum transfer speed between E2E Compute Node and E2E Object Storage?
Traffic between E2E Compute Node and E2E Object Storage can leverage up to 40 Gbps of bandwidth. However, the actual transfer rate and network performance depend on several factors, including:
- The data transfer medium, such as whether it’s between E2E nodes and E2E Object Storage or from an external point to Object Storage via the internet.
- The size of objects involved in the transfer.
- The E2E nodes' resources and utilization, including CPU, RAM, Disk I/O, and bandwidth limits.