- Introduction to contentACCESS
- contentACCESS setup package
- contentACCESS components
- contentACCESS Tools
- Tenants in contentACCESS
- General system configurations
- Connection
- User interface
- Users in contentACCESS
- Invitations
- Roles
- Login providers
- System
- Licensing
- Notifications
- System logs — how to find out possible misconfigurations / reasons of potential system/job failures
- Configuration auditing
- Archive auditing
- Distributed environment in contentACCESS — Clusters
- Statistics
- Legal hold
- Task runner
- Indexing
- SMTP Servers
- SMTP Mappings
- Sharing job
- Sharing settings
- How to create/configure databases — All databases
- Common features
- Creating new jobs in contentACCESS
- Jobs’ page, jobs’ context menu
- Filtering in jobs
- File Archive
- Introduction to File system archive
- File archive settings
- File archive Databases
- File archive System settings
- File archive Retentions
- File archive Storages
- Root folders
- Aliases
- File archive Schedules
- Provisioning settings and managing access to contentACCESS Portal
- Remote agents (file archive)
- Global rules (remote file archive)
- Configuring aliases
- Configuration of jobs available in contentACCESS File Archive
- Configuration of File archive retention changer job
- Configuration of File system archive job
- Configuration of a File system restore job
- Configuration of File system recovery job
- Configuration of Delete job in File archive
- Configuration of File system shortcut synchronization job
- Configuration of Remote shortcutting job
- Active/inactive documents in File system archive
- Email Archive
- Important settings before creating an Email Archive job
- Database settings
- Email archive System settings
- Email archive Provisioning settings
- Retention settings
- Shortcuts in email archiving
- Storing of archived emails
- Creating email archive schedulers
- User experience
- Address book objects
- Granting access rights for mailbox users and explicit users to view the mailbox archive
- Database and store assignment in email archiving
- Mail app access
- Remote agents (email archive)
- PST import
- Creating Email archive jobs: archive, restore, recovery, delete, mailbox move, shortcut synchronizaion, shortcut repair
- Email archive job
- Email archive retention changer job
- Email restore job
- Email recovery job
- Configuration of Delete job in Email archive
- Journal post processing job
- Mailbox move job
- Shortcut synchronization job
- Shortcut repair job
- Public folder archiving
- Access to private emails and archiving them
- SMTP archiving
- SharePoint archive plugin
- SharePoint Archive settings
- SharePoint archive System settings
- Site connections in the SharePoint archive
- SharePoint archive Provisioning settings
- Shortcut configuration in SharePoint
- SharePoint archive Address book
- SharePoint Archive job configuration
- SharePoint archive retention changer job configuration
- SharePoint recovery job configuration
- Configuration of Delete job in SharePoint archive
- SharePoint Publishing job
- SharePoint in the contentACCESS Portal archive
- OneDrive archive
- GDPR plugin
- Teams archive
- Teams archive databases
- Teams archive System settings
- Teams archive Provisioning settings
- Shortcut configuration in Teams archive
- Teams archive Address book
- Teams archive Licensing
- Teams archive Jobs
- Custom plugins
- ThreatTest
- officeGATE
- contentACCESS Mobile
- Virtual drive configurations
- Teams application
- Application settings
- Terms of use
- FAQ
- Download sample for the file to be imported does not work
- Archiving is not working if MAPI is set to communicate with the Exchange server
- Virtual drive is still appearing after the uninstall
- Outlook forms problems
- Unable to open shortcuts of archived files on the server side
- Samples are not shown using 'Show sample" option in the Import dialog
- Do I need to create separate tenants for file archiving and email archiving
- What is the recommended database size for email, file and Sharepoint archiving
- The TEMP folder is running out of space when archiving big files
- The attachment could not be opened
- After updating Exchange 2013, the EWS connection might not work in contentACCESS
- If Windows authentication is not working in contentACCESS and an alias was created for contentACCESS
- contentACCESS Outlook add-in certificate issue
- Prerequisites for O365 archiving
- PowerShell scripts for setting up Email archive
- How to reconfigure your email archive to use modern authentication for PowerShell
- Solution for Outlook security patches
- Solution for Outlook security patches through GPO
- Solution for indexing PDF files
- O365 SuperUser mailbox configuration
- Microsoft 365 journaling
- Organizational forms
- Multifactor authentication
- Region setting
- contentACCESS Mail app installation issue
- Azure app registration for O365 archiving
- Troubleshooting
7.4.1.Amazon S3 ↑ Back to Top
The Amazon S3 store supports any type of cloud storage if it’s using the Amazon S3 interface.
The store connects to the endpoint that you select for a specific service. In contentACCESS, the service endpoints for Amazon Simple Storage Service and Alibaba Cloud Object Storage, which also uses Amazon S3 interface, are preconfigured. If you want to use a different cloud service, which supports Amazon S3 interface, it is possible to select Custom service URL for the service and then enter a custom URL for that service endpoint.
The service authentication identifier is fixed for Amazon S3 and Alibaba, it’s not possible to change it. However if you are using custom endpoint URL, you can enter the identifier here. This identifier is used in the authentication request.
The version specifies which communication version to use for the service enpoint (the service version is specified by the enpoint service). If you are using Amazon S3, you can use Service Version 2 or 4, but Alibaba supports only Version 2 at this moment. The Access Key and Secret Access Key are used to authenticate the caller by the cloud service. These keys are provided by the cloud storage service.
This store type also supports compression and single instancing, which can save you a lot of space.