This package allows Python developers to write software that interacts with IBM Cloud Object Storage. It is a fork of the boto3 library and can stand as a drop-in replacement if the application needs to connect to object storage using an S3-like API and does not make use of other AWS services.
IBM has added a Language Support Policy. Language versions will be deprecated on the published schedule without additional notice.
For release notes, see the CHANGELOG.
You'll need:
- An instance of COS.
- An API key from IBM Cloud Identity and Access Management with at least
Writerpermissions. - The ID of the instance of COS that you are working with.
- Token acquisition endpoint.
- Service endpoint.
These values can be found in the IBM Cloud Console by generating a 'service credential'.
Use of the Python SDK and example code can be found here.
After generating a Service Credential, the resulting JSON document can be saved to ~/.bluemix/cos_credentials. The SDK will automatically source credentials from this file unless other credentials are explicitly set during client creation. If the cos_credentials file contains HMAC keys the client authenticates with a signature, otherwise the client uses the provided API key to authenticate by using a bearer token (using an API key still requires the config=Config(signature_version="oauth") to be included during client creation).
You can automatically archive objects after a specified length of time or after a specified date. Once archived, a temporary copy of an object can be restored for access as needed. Restore time may take up to 15 hours.
An archive policy is set at the bucket level by calling the put_bucket_lifecycle_configuration method on a client instance. A newly added or modified archive policy applies to new objects uploaded and does not affect existing objects. For more detail, see the documentation.
Users can configure buckets with an Immutable Object Storage policy to prevent objects from being modified or deleted for a defined period of time. The retention period can be specified on a per-object basis, or objects can inherit a default retention period set on the bucket. It is also possible to set open-ended and permanent retention periods. Immutable Object Storage meets the rules set forth by the SEC governing record retention, and IBM Cloud administrators are unable to bypass these restrictions. For more detail, see the IBM Cloud documentation.
Note: Immutable Object Storage does not support Aspera transfers via the SDK to upload objects or directories at this stage.
Users can set an archive rule that would allow data restore from an archive in 2 hours or 12 hours.
Aspera high-speed transfer through the COS SDK using the cos-aspera library is now legacy. New users and applications should use the Aspera Transfer SDK instead. Existing users should begin new projects with the Aspera Transfer SDK and make plans to migrate existing applications. Users who use S3 for transfers and do not install cos-aspera are unaffected.
Assuming that you have Python and virtualenv installed, set up your environment and install the required dependencies like this instead of the pip install ibm-cos-sdk defined above:
git clone https://github.com/ibm/ibm-cos-sdk-python.git
cd ibm-cos-sdk-python
$ virtualenv venv
...
. venv/bin/activate
pip install -r requirements.txt
pip install -e .Feel free to use GitHub issues for tracking bugs and feature requests, but for help please use one of the following resources:
- Read a quick start guide in IBM Cloud Docs.
- Ask a question on Stack Overflow and tag it with
ibmandobject-storage. - Open a support ticket with IBM Cloud Support
- If it turns out that you may have found a bug, please open an issue.
IBM supports current public releases. IBM will deprecate language versions 90 days after a version reaches end-of-life. All clients will need to upgrade to a supported version before the end of the grace period.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE.txt and NOTICE.txt for more information.
