- 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
ECS IAM error codes
The below table lists the ECS IAM error codes.
| Error type | HTTP status code | Description |
|---|---|---|
| AccessDeniedException | 400 | Indicates that you do not have the required access to perform the action. |
| ConcurrentModification | 409 | Indicates that multiple requests are submitted simultaneously to modify the object. You need to wait for a few minutes and submit the request again. |
| DeleteConflict | 409 | Indicates that the request is raised to delete a resource that is attached with another entity. |
| EntityAlreadyExists | 409 | Indicates that the request is raised to create a resource that already exists. |
| ExpiredToken | 400 | Indicates that the Web identity token that is used to perform the action is expired or not valid. |
| IDPRejectedClaim | 403 | Indicates that the identity provider (IdP) reported that authentication failed. |
| InternalFailure | 500 | Indicates that the request failed due to an unknown error, exception, or failure. |
| InvalidAction | 400 | Indicates that the requested action is not valid. |
| InvalidInput | 400 | Indicates that an invalid or an out-of-range value is provided for an input. |
| InvalidParameterValue | 400 | Indicates that an invalid or an out-of-range value is provided for an input parameter. |
| LimitExceeded | 409 | Indicates that the request is rejected because an attempt is made to create resources beyond the current account limits. |
| MalformedPolicyDocument | 400 | Indicates that the provided policy document is malformed. |
| MissingAction | 400 | Indicates that the action or a required parameter is missed in the request. |
| MissingParameter | 400 | Indicates that the required parameter is missed in the request. |
| NoSuchEntity | 404 | Indicates that the referenced entity does not exist. |
| NotImplemented | 501 | Indicates that the mentioned functionality is not implemented yet. |
| PackedPolicyTooLarge | 400 | Indicates that the total packed size of the session policies and session tags combined is too large. See ECS IAM limitations on entities and objects. |
| PermissionDenied | 403 | Indicates that the principal does not have the required permission to perform the action. |
| ServiceFailure | 500 | Indicates that the request is failed because of an unknown error, exception, or failure. |
| ServiceUnavailable | 503 | Indicates that the request is failed due to a temporary failure of the server. |
| ValidationError | 400 | Indicates that the input fails to satisfy the constraints specified by the specific API. |
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: <>()\