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.
Hello,
We are currently trying to implement the AWS S3 Connected System. When setting up the connected system, we plug in the Access Key ID, Region and Secret Access Key, but when we go to test the connection we are getting "No Owner Associated with this Account. I see below it was mentioned that the getS3AccountOwner method was used to verify the connected system. Is there a way around this? Current we are working with a no owner on the bucket we are leveraging.
Hey Brian, I have removed this restriction, and the updated Connected System should be available soon on app market. In the meantime, you can still create the connected system and use it in integrations without successfully connecting with "Test Connection"