In the example of the S3 Connector, each content store (i.e. "final" content store, one that provides actual storage, as opposed to a caching content store), should have dedicated configuration options:
| Property | Description |
| connector.s3.directAccessUrl.enabled | Controls whether DAUs are enabled on this specific content store (for example false). |
| connector.s3.directAccessUrl.defaultExpiryTimeInSec | Sets the expiry time in seconds for the DAU in this store, by overriding the global configuration (for example 30). If this value exceeds the content store limit (described below) or the global limit it should fallback to the global configuration. Its value cannot exceed the system-wide maximum expiry time configuration ( system.directAccessUrl.maxExpiryTimeInSec) - it can only be equal or lower (otherwise DAUs for the specific content store will be disabled). If it's not set, the default system-wide setting is used ( system.directAccessUrl.defaultExpiryTimeInSec). |
| connector.s3.directAccessUrl.maxExpiryTimeInSec=300 | The maximum expiry time interval that can be requested by clients - content-store specific setting. Its value cannot exceed the system-wide configuration ( system.directAccessUrl.maxExpiryTimeInSec) - it can only be equal or lower (otherwise DAUs for the specific content store will be disabled). If it's not set, the default system-wide setting is used ( system.directAccessUrl.maxExpiryTimeInSec). |
Note
Callers within the platform (i.e. Java interfaces) can either request a specific expiry time or rely on the default value.
Note
When multiple S3 buckets are used for storage in Alfresco, each S3 Content Store can be configured with either the default (common) S3 Connector-specific properties (i.e. connector.s3.directAccessUrl.enabled etc.), or new separate properties can be defined for each and every store (i.e. connector.s3store1.directAccessUrl.enabled, connector.s3store2.directAccessUrl.enabled, etc.).