How to integrate AWS S3 bucket with CloudFiles

this guide will walk you through the process of connecting your aws s3 bucket to cloudfiles using an aws cloudformation template by the end of this guide, you will have created a new stack in cloudformation and obtained the necessary details to successfully link your s3 bucket to cloudfiles prerequisites you need an active aws account and an s3 bucket for integration ensure that you have already created the required s3 bucket in your account before proceeding with the following steps steps enter your bucket name in cloudfiles open the cloudfiles app in salesforce and navigate to document management > libraries click on aws s3 (if you do not see the aws s3 option, click manage libraries and add it first) click connect, enter your s3 bucket name, and continue download the cloudformation template note down the external id shown on screen, then download the cloudformation template that is generated head over to the aws management console after this step access aws cloudformation in the aws management console, search for and select 'cloudformation' create a new stack click on “create stack” and select “with new resources (standard)” choose “template is ready” under the “prepare template” options upload the cloudformation template select “upload a template file” click on “choose file” and upload the cloudformation template you downloaded in step 2 click “next” specify stack details enter a name for your stack for example, “cloudfiless3integration” fill in any parameters required by the template, if applicable click “next” configure stack options (optional) configure any additional options like tags or permissions if necessary click “next” review and create the stack review all settings and details make sure everything is correct acknowledge that aws cloudformation might create iam resources click “create stack” wait for stack creation the stack creation process might take a few minutes wait until the status changes to “create complete” obtain the outputs once the stack creation is complete, go to the “outputs” tab of your stack note down the ‘role arn’ values this is essential for connecting your s3 bucket to cloudfiles enter details in cloudfiles log into your cloudfiles account navigate to the s3 bucket integration section enter the ‘role arn’ you noted down earlier also enter the following fields prefix (optional) this defines the folder path within your s3 bucket that cloudfiles will use this lets you organise data within a specific section of the bucket rather than the entire bucket when connecting a bucket for the first time, you can use any prefix if you reuse an existing bucket in another org, each connection must use a unique, non overlapping prefix to prevent conflicts — for example, team a/ and team b/ are valid, but team a/ and team a/subfolder/ are not drive label the display name for this storage connection in cloudfiles this is what users will see when accessing or selecting a storage location it is optional for the first bucket connected in your org but required for any additional connections save your settings note a prefix is mandatory every time you connect the same bucket more than once, whether within the same org or across different orgs — this ensures paths do not overlap if you are connecting the same bucket a second time within the same org, both the original and the new connection must have a prefix, so if the first connection was made without one, disconnect it and reconnect with a prefix before adding the second a drive label is mandatory from the second bucket onward within the same org, regardless of whether the buckets are the same or different after entering the details in cloudfiles, your s3 bucket should now be successfully connected to your cloudfiles account you can start managing and accessing your s3 files directly through cloudfiles note if a bucket is already connected, you will see a 'reuse existing connection' option at this stage and can connect the same bucket again using a different, non overlapping prefix enable sync (optional) toggle on enable sync to automatically reflect changes from your s3 bucket in cloudfiles once enabled, any files or folders uploaded, updated, or deleted in s3 will appear in cloudfiles note sync only applies to changes made after the toggle is enabled existing files in your s3 bucket will not appear automatically in cloudfiles to make historical data available, a custom migration is required — contact support\@cloudfiles io for details if your s3 bucket was connected before the automated sync setup was introduced, enabling sync may require updating the iam role permissions first see docid 1qfoi3qab5ka7j6c789fm for steps