Tuning cipher settings
IBM COS supports a variety of cipher settings to encrypt data in transit. Not all cipher settings yield the same level performance. Negotiating one of
TLS_RSA_WITH_AES_128_CBC_SHA has shown to yield the same levels of performance as no TLS between the client and the IBM COS System.
Using multipart uploads
When working with larger objects, multipart upload operations are recommended to write objects into IBM COS. An upload of a single object can be performed as a set of parts and these parts can be uploaded independently in any order and in parallel. Upon upload completion, IBM COS then presents all parts as a single object. This provides many benefits: network interruptions do not cause large uploads to fail, uploads can be paused and restarted over time, and objects can be uploaded as they are being created.
Multipart uploads are only available for objects larger than 5MB. For objects smaller than 50GB, a part size of 20MB to 100MB is recommended for optimum performance. For larger objects, part size can be increased without significant performance impact.
Due to the additional complexity involved, it is recommended that developers make use of S3 API libraries that provide multipart upload support.
AbortIncompleteMultipartUpload. If an incomplete multipart upload is not aborted, the partial upload continues to use resources. Interfaces should be designed with this point in mind, and clean up incomplete multipart uploads.
Using software development kits
It is not mandatory to use published S3 API SDKs; custom software can leverage the API to integrate directly with IBM COS. However, using published S3 API libraries provide advantages such as authentication/signature generation, automatic retry logic on
5xx errors, and pre-signed url generation. Care must be taken when writing software that uses the API directly to handle transient errors, such as by providing retries with exponential backoff when receiving