File Transfer to Amazon S3 Bucket using SFTP

Have you looked at the Amazon S3 plugin?

forum.appian.com/.../summary

Did u get a chance to work on this smart service? is it same like SFTP or any additional things to be considered?

I've not used it, and don't know the exact methods it uses to transfer. Perhaps you could contact the original developer or decompile the .jar file to find out?

Here

Secure Credential Store Key: I have set up a key in admin console under third party credentials , selected Amazon S3 Utilities and provided my user name and password of Appian and saved.

Amazon S3 Bucket Name: Given my AWS newly created bucket name

Files: I have given a csv file

AWS server side encryption: false

AWS client side encryption: false

when I execute this am receiving an alert "java.lang.IllegalArgumentException: Access key cannot be null."

Where to setup the access key?  Also where can we provide the credentials to authenticate with AWS.any thoughts from your side?

So, I don't think the documentation is very clear for this, but it says the following:

The plugin leverages the Appian Secure Credential Store for the credentials to integrate with Amazon S3. Before executing the plugin, create an new secure credential store with the following 3 attributes:
- accesskeyid: this is the access key id for connecting to AWS S3
- accesskeysecret: this is the access key secret for connecting to AWS S3
- kmscmkid: this attribute is only required if using AWS Client Side Encryption

Looking at the code, it seems the credential field names MUST match the ones above -
so you should have a single Third Party Credential with three fields as above, each containing the appropriate values.

Once you've got that set, up the input on the smart service named Secure Credential Store Key should be the *name* of the third party credential you have set up that contains the three values as above.

I THINK that's right - give it a go and let me know if it works. Apologies if this is what you've already done...!

So, I don't think the documentation is very clear for this, but it says the following:

The plugin leverages the Appian Secure Credential Store for the credentials to integrate with Amazon S3. Before executing the plugin, create an new secure credential store with the following 3 attributes:
- accesskeyid: this is the access key id for connecting to AWS S3
- accesskeysecret: this is the access key secret for connecting to AWS S3
- kmscmkid: this attribute is only required if using AWS Client Side Encryption

Looking at the code, it seems the credential field names MUST match the ones above -
so you should have a single Third Party Credential with three fields as above, each containing the appropriate values.

Once you've got that set, up the input on the smart service named Secure Credential Store Key should be the *name* of the third party credential you have set up that contains the three values as above.

I THINK that's right - give it a go and let me know if it works. Apologies if this is what you've already done...!