Applications for Amazon S3 Storages
Applications for Amazon S3 storages have their own preconfigured templates.

- For Axcelerate Ingestion application
- documentHold.sytemTemplate-Axc5-v1-AWS
- For Axcelerate Ingestion index engines
- singleMindServer.documentHoldSystemTemplate-v2-AWS
- For an Axcelerate Review & Analysis index engine
- singleMindServer.axcelerateStandaloneSystemTemplate-Axc5-v2-AWS
Important: We recommend to not change the template settings for storages, except for Amazon S3 access.
Default storage properties
- In Amazon S3, data is not stored in files, but as binary objects in the cloud.
- The Amazon S3 connection is configured in the CORE master service. All applications managed through the same master service use the same Amazon S3 bucket for storages.
- Scalability: Amazon S3 does not set any limit to storage sizes.
- Axcelerate Ingestion and Axcelerate Review & Analysis use primary storages, that is, deleting an application does not affect other applications using the same stored files. Also, applications do not use an external storage by default.
-
Storages are SQL-managed. SQL-management in combination with Amazon S3 storage offers:
- single instance storage, that is, file sharing within one storage handler
- external cloning, that is, file sharing between different storage handlers.
- case-wide sharing of native files
- compressed storage of native files and redactions
What does this mean for native files and images?
- Native file copies are created for any type of data loading, including CSV data load. A reference to these native file copies is added to the Axcelerate Ingestion storage handler. During publishing, a reference to these native file copies is added to the Axcelerate Review & Analysis storage handler.
- Image copies can be imported with CSV load or CSV merge. A reference to these image copies is added to the respective storage handler. During publishing, a reference is added for the Axcelerate Review & Analysis storage handler for images.