Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
s3compatibleapi [2019_05_07 14:20] – [Amazon S3 compatible API] jim | s3compatibleapi [2023_08_15 20:56] – steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
# Amazon S3 compatible API | # Amazon S3 compatible API | ||
- | The Enterprise File Fabric provides support for an Amazon S3 compatible API. This means you can use the S3 compatible object storage API to access files that have been mapped to the File Fabric, such as files available on Google Drive, RackSpace Cloud Files, or Microsoft OneDrive, or any of the many other clouds that the solution supports. | + | The Enterprise File Fabric provides support for an Amazon S3 compatible API. This means the S3 compatible object storage API can be used to access files that have been mapped to the File Fabric, such as files available on Google Drive, RackSpace Cloud Files, or Microsoft OneDrive, or any of the many other clouds that the solution supports. |
The S3 API is available on the SaaS hosted service and also on the enterprise on-premises edition of the product. | The S3 API is available on the SaaS hosted service and also on the enterprise on-premises edition of the product. | ||
Line 7: | Line 7: | ||
## Client Configuration | ## Client Configuration | ||
- | To use the S3 API you will need the: | + | To use the S3 API the: |
1. Cloud S3 Endpoint | 1. Cloud S3 Endpoint | ||
- | 1. Access Key ID | + | 2. Access Key ID |
- | 1. Secret Access Key | + | 3. Secret Access Key |
+ | |||
+ | are required. | ||
### 1. Cloud S3 Endpoint | ### 1. Cloud S3 Endpoint | ||
- | For our SaaS services | + | For the SaaS hosted service it is required to use one of the following S3 API endpoints: |
* http:// | * http:// | ||
Line 24: | Line 26: | ||
Naturally http endpoints are not secure and should not be used for production data. | Naturally http endpoints are not secure and should not be used for production data. | ||
- | For appliances contact your administrator for the " | + | For the enterprise on-premises version of the product the S3 access nomenclature is set through the ConfigServer. |
### 2. Access Key ID | ### 2. Access Key ID | ||
- | The Access Key ID is your SME or File Fabric username. | + | The Access Key ID is the SME or File Fabric username. |
### 3. Secret Access Key | ### 3. Secret Access Key | ||
Line 36: | Line 38: | ||
## Use With a Variety of S3 Clients | ## Use With a Variety of S3 Clients | ||
- | The File Fabric' | + | The File Fabric' |
- | * [[standalone/ | + | |
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
Line 45: | Line 46: | ||
## API Implementation | ## API Implementation | ||
- | SME supports | + | The File Fabric implements |
* **[[http:// | * **[[http:// | ||
Line 57: | Line 58: | ||
* **[[http:// | * **[[http:// | ||
+ | ## S3 Signatures Supported | ||
+ | The S3 API supports V2 and V4 signatures. Which one is used is dependent on the client request. |