Overview
The Amazon S3 Utilities Plug-in leverages the Amazon AWS Java API to connect with Amazon S3 to store and retrieve files.
Key Features & Functionality
The following smart services are included:
The plug-in also includes a function:
Amazon S3 Utilities supports the following Amazon S3 features:
Note: The plug-in requires Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files when using client side encryption.
(https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html)
The Appian Secure Credential Store is leveraged for the credentials to integrate with Amazon S3. Before executing the plug-in, create an new secure credential store with the following 3 attributes. These values are obtained from Amazon AWS IAM console.
You will need to develop a component plugin that is used to directly upload files from SAIL into S3
Thanks Mike for your answer. In our use case there is no predefined URL. It is required to upload files larger than 1 Gb from an application developed with Appian to the final repository.
That depends on the nature of the transfer - if it is a direct download from S3 using a presigned url, there is technically no limit. Otherwise, limits will apply. What's your use case?
Hi, I would like to know if this plug-in is used to address the transfer of files larger than 1 GB, and with which repository it should integrate in AWS.
Thank You Mike! It worked.
Do you mean upload file works well? Why would you need the url after you downloaded the file?
Are you referring to the S3 Connected System and not this plugin?
For downloads, I do recommend using the getPreSignedURLForS3() function from this plugin - that way you don't have to download the document into Appian and the operation happens client side only.
Hi, When using Download File Operation, able to download the file successfully, but no response in the response body. Is it possible to add in the response as we are trying to show the download link to the User at UI
The integration object is not needed. On your interface you render links to the web api. The web api object NEEDS TO check security first, then redirect the user.