Storage of binary Content Manager content
By default, Content Manager stores binary large objects (BLOBs) in the Content Manager database you configured. But by modifying the Content Manager configuration file, you can configure storage of BLOBs on the file system, in an Amazon S3 bucket, or in Azure Blob storage.
configSections section contains a section element with its name attribute set to PermanentContentStorage, and with its type attribute value indicating where to store the binary content:
- For storage in a database,
typemust have the valueTridion.ContentManager.Configuration.DatabasePermanentContentStorageSettings, Tridion.ContentManager, Version=VERSION, Culture=neutral, PublicKeyToken=360aac4d3354074b. Additionally, the file needs to contain a database server connection configured in adatabaseelement, which was added and set when you ran the Content Manager installer. - For storage in a (network-accessible) file system location,
typemust have the valueTridion.ContentManager.Configuration.FileSystemPermanentContentStorageSettings, Tridion.ContentManager, Version=VERSION, Culture=neutral, PublicKeyToken=360aac4d3354074b - For storage in an Amazon S3 bucket,
typemust have the valueTridion.ContentManager.Extensibility.AmazonStorage.AwsS3PermanentContentStorageSettings, Tridion.ContentManager.Extensibility.AmazonStorage, Version=VERSION, Culture=neutral, PublicKeyToken=ddfc895746e5ee6b - For Azure Blob storage,
typemust have the valueTridion.ContentManager.Extensibility.AzureStorage.AzurePermanentStorageProviderSettings, Tridion.ContentManager.Extensibility.AzureStorage, Version=VERSION, Culture=neutral, PublicKeyToken=ddfc895746e5ee6b
In all of these values, VERSION is the version, to be verified in the Global Assembly Cache (GAC).
permanentContentStorage element with a number of storage type-specific attributes:
- Database storage
-
No attributes:
<permanentContentStorage /> - File system storage
-
A
folderattribute containing the path to the (network-accessible) file system location, for example:<permanentContentStorage folder="\\filesys03\Transport\PermanentBLOBFolder" /> - Amazon S3 bucket storage
-
Specify the following attributes:
Attribute Description awsAccessKeyIdThe ID of your access key awsSecretAccessKeyThe secret of your access key bucketNameThe name of the bucket, com.sdl.tridion.cloud.dev.tcm.upload aswRegionThe geographical region used for storage, for example, eu-west-1blobFolderThe name of the folder used for storage For example, the following is a validpermanentContentStorageelement:<permanentContentStorage awsAccessKeyId="AKIAIVRGD7LJPHCBUPQA" awsSecretAccessKey="EN68qdVaFeYq7RylM3gSprCQejNto3SkQ2cfUi+Y" bucketName="com.sdl.tridion.cloud.dev.tcm.upload" awsRegion="eu-west-1" blobFolder="myBLOBFolder" /> - Azure Blob storage
-
Specify the following attributes:
Attribute Description defaultEndpointsProtocolThe default protocol to use (for example, HTTPS) when accessing endpoints blobFolderThe name of the folder in which to store BLOBs accountNameThe name of your Azure Blob storage account accountKeyThe key for that account For example, the following is a validpermanentContentStorageelement:<permanentContentStorage defaultEndpointsProtocol="https" blobFolder="test-folder" accountName="myazureaccount1" accountKey="Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRE6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBeBeksoGMGw==" />
After modifying the Content Manager configuration file and saving your change, be sure to restart IIS to apply your changes.