Close

Upgrade Content Connector for AWS S3

Use this information to upgrade the S3 Connector from a previous version for Tomcat-based deployments only.

  1. Stop the Alfresco Content Services server.

  2. Navigate to the root directory of your installation.

  3. Use the following command to check for the module you wish to delete:

    java -jar bin/alfresco-mmt.jar list tomcat/webapps/alfresco.war
    

    This displays a list of the installed modules. Make a note of the module ID of the module you wish to uninstall, for example, org_alfresco_integrations_S3Connector.

  4. Use the Module Management Tool (MMT) to uninstall the AMP from the repository WAR (alfresco.war). For example:

    java -jar bin/alfresco-mmt.jar uninstall org_alfresco_integrations_S3Connector 
     tomcat/webapps/alfresco.war
    

    For more information, see Using the Module Management Tool (MMT) and Uninstalling an Alfresco Module Package.

  5. Navigate to the amps directory.

  6. Delete any previously installed S3 Connector AMP.

  7. Copy the AMP file you downloaded during installation to the amps directory.

  8. Use the Module Management Tool (MMT) to install the AMP into the repository WAR (alfresco.war).

    For more information, see Using the Module Management Tool (MMT) and Installing an Alfresco Module Package.

  9. Check that the configuration is set up correctly for your environment.

    Note: To upgrade a system that never used the file system (i.e. on-premises installation without locally saved binaries), we recommend that you choose a pure S3 content store. See S3 Connector content store subsystems and Properties reference for more details.

  10. Starting from version 3.1, the S3 Connector has custom soft deletion disabled by default, since this feature is already present in Amazon’s S3 service. For details on how to re-enable it, see S3 Connector deleted content store.

  11. Start the server.

Edit this page

Suggest an edit on GitHub
This website uses cookies in order to offer you the most relevant information. Please accept cookies for optimal performance. This documentation is subject to the Documentation Notice.