Since November of 2015 Smart Mover (9.6.0) has included the S3 Upload and Download Tasks.
At this point I think most everyone reading this knows what S3 is but just in case… quoting from Amazon’s own web site:
Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance. This means customers of all sizes and industries can use it to store and protect any amount of data for a range of use cases, such as websites, mobile applications, backup and restore, archive, enterprise applications, IoT devices, and big data analytics. Amazon S3 provides easy-to-use management features so you can organize your data and configure finely-tuned access controls to meet your specific business, organizational, and compliance requirements. Amazon S3 is designed for 99.999999999% (11 9's) of durability, and stores data for millions of applications for companies all around the world.
So using Smart Mover’s S3 Upload and Download Tasks you can easily automate integrating these services along with your Enterprise and Elvis systems.
One simple example: After publication, we want to backup all the content from that Enterprise Issue.
This just takes 2 Tasks:
1. Enterprise Download: Simply download the content of the desired Issue into a folder in your Base Path…. I created and chose one called “new”. In my case, I crafted a query that only selected Dossiers from the “Current Issue” and I included the Native file along with both Child and Grand Child objects. So all the content files used in the Issue will be downloaded. Since I based this all on the “Current Issue” there was no need to set the Status to ’Next” or any other value as next time I run the Process the "Current Issue" will refer to entirely new files.
I also choose to structure the downloaded files into a Brand-Channel-Issue-Category folder structure… as I thought this makes the most sense for a backup. But you could use any other options available.
2. S3 Upload: Set the Source folder to the same one used in Step 1, Include Subfolders and you will probably want to Delete Original File just to clean things up. Enter your S3 IAM User’s Access key ID and Secret Key then click the Get Buckets button. This will give you a list of all that User’s S3 Buckets from where you can simply chose the desired target for the files. If you do not have an appropriate Bucket already set up you will need to do so using your AWS Console.
This Task will then upload all the files that where downloaded in the first Task into the chosen S3 Bucket… all the while maintaining the original "Enterprise-like" folder structure chosen in Step 1.
You now have a backup of all the content from that Issue organized into a very readable and accessible structure on S3. You can also at some point either manually or automatically move those files and folders into a more cost effective AWS storage service like S3 Glacier. See: https://aws.amazon.com/s3/storage-classes/?p=s3&exp=a
Please sign in to leave a comment.