For on-premises customers, AWS S3 is often a more cost effective method to store your content, paying just for what you need and does not require you to budget up front for growth capacity.
The S3 Connector is supported as the default content store for Alfresco Content Services. When installed on-premises, existing content will remain accessible from your existing content store(s), and all new content is written to the S3 content store.
The following diagram shows a simple representation of how an on-premises (on-prem) deployment of Alfresco Content Services using the S3 Connector can interact with AWS S3.
Installation and configuration
You can install and configure Alfresco Content Services and the S3 Connector on-premises using the default configuration. Follow the steps in Installing and configuring the S3 Connector, and the basic configuration steps in Configuring the S3 Connector.
- AES256 encryption for new content
- Content decryption on reads from the existing on-premises files
Difference between running in AWS and running outside AWS
The following table highlights the capabilities that are supported depending on your deployment scenario.
|New deployment (on-prem)||Supported via AWS API keys only||Supported|
|New deployment (in AWS)||Supported via Instance Profile||Supported|
|Existing deployment (on-prem)||Supported via AWS API keys only||Supported|
|Existing deployment (in AWS)||Supported via Instance Profile||Supported|