- Notes, cautions, and warnings
- S3
- Amazon S3 API support in ECS
- S3 API supported and unsupported features
- Bucket policy support
- Object Tagging
- S3 Object Lock
- Object lifecycle management
- S3 Extensions
- Metadata Search
- S3 and Swift Interoperability
- Create and manage secret keys
- Authenticating with the S3 service
- Using s3curl with ECS
- Use SDKs to access the S3 service
- ECS S3 error codes
- Hadoop S3A for ECS
- Enabling data2 IP in ECS S3
- Cloud DVR
- ECS IAM for S3
- OpenStack Swift
- EMC Atmos
- CAS
- Setting up CAS support in ECS
- Cold Storage
- Compliance
- CAS retention in ECS
- Advanced retention for CAS applications: event-based retention, litigation hold, and the min/max governor
- Set up namespace retention policies
- Create and set up a bucket for a CAS user
- Set up a CAS object user
- Set up bucket ACLs for CAS
- ECS Management APIs that support CAS users
- Content Addressable Storage (CAS) SDK API support
- ECS CAS error codes
- Enabling data2 IP in CAS
- ECS Management REST API
- ECS HDFS
- ECS HDFS Introduction
- Configuring Hadoop to use ECS HDFS
- Hadoop authentication modes
- Migration from a simple to a Kerberos Hadoop cluster
- File system interaction
- Supported Hadoop applications
- Integrate a simple Hadoop cluster with ECS HDFS
- Install Hortonworks HDP using Ambari
- Create a bucket for HDFS using the ECS Portal
- Plan the ECS HDFS and Hadoop integration
- Obtain the ECS HDFS installation and support package
- Deploy the ECS HDFS Client Library
- Configure ECS client properties
- Set up Hive
- Verify Hadoop access to ECS
- Secure the bucket
- Relocate the default file system from HDFS to an ECS bucket
- Integrate a secure Hadoop cluster with ECS HDFS
- Verify that AD/LDAP is correctly configured with a secure Hadoop cluster
- Pig test fails: unable to obtain Kerberos principal
- Permission denied for AD user
- Permissions errors
- Failed to process request
- Enable Kerberos client-side logging and debugging
- Debug Kerberos on the KDC
- Eliminate clock skew
- Configure one or more new ECS nodes with the ECS service principal
- Workaround for Yarn directory does not exist error
- Set up the Kerberos KDC
- Configure AD user authentication for Kerberos
- Secure bucket metadata
- Hadoop core-site.xml properties for ECS HDFS
- Hadoop core-site.xml properties for ECS S3
- External key management
- Document feedback
ECS 3.6.2 Data Access Guide
OpenStack Swift supported operations
The following sections list the OpenStack REST API requests that are supported, and unsupported by ECS.
This information is taken from the Object Storage API V1 section of the OpenStack API Reference documentation.
Supported OpenStack Swift calls
| Method | Path | Description |
|---|---|---|
| GET | v1/{account} | Retrieve a list of existing storage containers ordered by names. |
| POST | v1/{account} | Create or update an account metadata by associating custom metadata headers with the account level URI. These headers must take the format X-Account-Meta-*. |
| GET | v1/{account}/{container} | Retrieve a list of objects stored in the container. |
| PUT | v1/{account}/{container} | Create a container. |
| DELETE | v1/{account}/{container} | Delete an empty container. |
| POST | v1/{account}/{container} | Create or update the arbitrary container metadata by associating custom metadata headers with the container level URI. These headers must take the format X-Container-Meta-*. |
| HEAD | v1/{account}/{container} | Retrieve the container metadata. Currently does not include object count and bytes used. User requires administrator privileges. |
| GET | v1/{account}/{container}/{object} | Retrieve the object's data.
NOTE: GET range on a Static Large Object (SLO) will not work if the segments were created prior to ECS 3.0.
|
| PUT | v1/{account}/{container}/{object} | Write, or overwrite, an object's content and metadata. Used to copy existing object to another object using X-Copy-From header to designate source. For a Dynamic Large Object (DLO) or a SLO the object can be a manifest. Refer to Swift's documentation for details. |
| DELETE | v1/{account}/{container}/{object} | Remove an object from the storage system permanently. In combination with the COPY command you can use COPY then DELETE to effectively move an object. |
| HEAD | v1/{account}/{container}/{object} | Retrieve object metadata and other standard HTTP headers. |
| POST | v1/{account}/{container}/{object} | Set and overwrite arbitrary object metadata. These metadata must take the format X-Object-Meta-*. X-Delete-At or X-Delete-After for expiring objects can also be assigned by this operation. But other headers such as Content-Type cannot be changed by this operation. |
| Feature | Notes |
|---|---|
| Temporary URLs | ECS supports the use of temporary URLs to enable users to be given access to objects without needing credentials. More information can be found Swift's documentation. |
Unsupported OpenStack Swift calls
| Method | Path | Description |
|---|---|---|
| COPY | v1/{account}/{container}/{object} | Copy operation can be achieved using PUT v1/{account}/{container}/{object} with X-Copy-From header. |
| HEAD | v1/{account} | Retrieve the account metadata. Not fully supported as returns zero for the bytes stored (X-Account-Bytes-Used). |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\