Overview
Manage AWS S3 data stores with Appian! Users can access their S3 objects directly from an Appian interface. Appian documents can be uploaded to a S3 bucket with Server-Side Encryption and be configured as Public or Private. The AWS S3 Connected System Plug-in uses the AWS Java SDK to connect to S3.
Key Features & Functionality
Requirements
Access Key Id: the access key id for connecting to S3 can be retrieved from AWS Management Console Navigate to the Users > Summary page and click the “Security credentials” tabSecret Access Key: the secret access key can only be viewed once upon the creation of an access key, see AWS Access Keys documentation for more information: https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys
Notes
Users that want to upload objects as 'Public' must have the correct IAM privileges or an "Access Denied" error will return.
S3 endpoints which restrict traffic based on source will need to allow the IP and VPC endpoints outlined in KB-1582 based on site region.
Hi theresaa0002 - yes it is compatible with all versions above 19.3. Check out the AppMarket FAQ for information on compatibility.
Is this plugin compatible with Appian 20.1? I see it says 20.4 but just verifying
Has anyone successfully used the operation "Upload Multiple Files" with encryption into a bucket that explicitly denies objects that are not server-side encrypted? Based on my review of the source code, AWSS3UploadMultiFileIntegrationTemplate.java is calling uploadFileList but not sending ObjectMetadata along with the files and therefore the files are not actually encrypted, even if the "Encrypted" checkbox is checked.
Our testing has confirmed this as well.
Got it.
How do you install this plug-in?
Yes, its giving Access Denied error
Hi, are you currently getting errors when trying to "Test Connection" with the access key/secret key from cross accounts?
Does it works with AWS cross account access?
we have AWS Organizational Unit, user accounts (access key/secret key) are created in one account and S3 bucket in another account, Users are given cross account access using assume role to access the cross account S3 bucket.
How do we set up the S3 connected system for this scenario?