Properties deprecated in S3 Connector 3.1 - Properties deprecated in S3 Connector 3.1 - Alfresco - Alfresco Content Connector for AWS S3 - Alfresco/Alfresco-Content-Connector-for-AWS-S3/6.0/Alfresco-Content-Connector-for-AWS-S3/Alfresco-Content-Connector-for-AWS-S3/Configure/Properties-reference/Properties-deprecated-in-S3-Connector-3.1 - 6.0

The following properties were deprecated in S3 Connector 3.1, and should no longer be used as they'll be removed in a future release.

• s3.useContentRootInPath

  The default is false. When set to true, Alfresco Content Services won't start, and you'll see an error:

  The V1 storage protocol s3:// has been deprecated since version 2.0 of this connector 
  and has been removed. This version no longer supports  s3.useContentRootInPath
  parameter being set to true. If you need to partition the objects in your bucket, we 
  recommend either using tags or the new connector.s3.objectNamePrefix option.
  

  Check Replicating s3.useContentRootInPath behavior for details of how to replicate the old behavior of the s3.useContentRootInPath option through new configuration properties.

• s3.useTenantDomainInPath

  Defines whether the tenant name is used in the S3 path. The default is false. When set to either true or false, you'll see a warning specifying that multi-tenancy is no longer supported:

  Multi-tenancy is no longer supported
  

  In spite of the warning, the behavior of the S3 Connector hasn't changed in relation to this property. However, only content store beans of type org.alfresco.integrations.connector.TenantS3ContentStore actually contain logic that can interpret this property. (In the S3 Connector default Spring configuration, there's currently only one such bean: tenantS3ContentStore).

• s3.autoLowerCaseBucketName

  The default is false. When set to either true or false, you'll see a warning:

  The property s3.autoLowerCaseBucketName is no longer supported
  

  In spite of the warning, the S3 Connector behavior hasn't changed yet.

• s3.flatRoot

  Defines whether all content items should be stored in the same single directory in the bucket, otherwise the standard date-based hierarchy is used. The default is true. When set to false, you'll see a warning:

  The property flatRoot is no longer supported, is highly discouraged, and will be 
  removed with the next release.
  

  In spite of the warning, the configuration is still evaluated and followed (i.e. no behavior changes yet).