NOTE: This connector was set to use the authentication Signature 4. It won’t work if the S3 bucket region is set to any other signature version.

Step 1) Configure your AWS S3 server

Step 2) Get the authentication accesses

Step 3) Create your OS application

Step 4) Drag the actions for managing files according to your application’s needs.

Step 5) Fill the structures in the actions with the necessary data, according to your AWS configurations. The required fields are Access Key, Secret Key, and Bucket Name.
 

Note: If you don’t specify a SubFolder it will manipulate objects in the root of the bucket.

Step 5b) Optionally, you can configure proxy access to your S3 Server. It will only try to connect with the proxy if you set the flag UseProxy as true. Note: Domain is not required, it’s never used in the integration.

Step 6)  Now that you’re all set, it’s possible to start testing your application.

STRUCTURES

AmazonToken -  Contains the authentication fields AccessKey and SecretKey. (Mandatory)

ProxyDetails - Contains the fields for connecting with a proxy. (Optional. Depending on AWS configuration), In the Actions below, a connection by proxy will only be attempted when the flag useProxy is set to true and the proxy connection info is valid, otherwise it will attempt to connect without a proxy.

S3File - Contains the fields needed to perform file management actions in the S3 server.

(Not all of them mandatory, see below)

ACTIONS