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. The following operations are included:
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?
sure thing and the plugin has finally been updated ,,, version: 184.108.40.206
great news Sam! we'll wait for the update. thanks!
jraquino thanks for brining this to our attention. We have updated the plugin to allow for content-type setting on object metadata... new version should be available within a day or so.
When using the older S3 Utilities plugin the content type metadata is set correctly.
It seems the content type metadata of the object uploaded is defaulted to application/octet-stream. It is kind of important for us to set the content type correctly, is there a way for us to do so using this plugin?
Hey ricardop I have reached out to you in a separate email. Thanks!
Hi friends, we're getting a 403 Error when testing the connection. We have verified access to the specific bucket via aws cli. Also tried creating the connected system without passing the connection test, but still get the 403 when creating an Integration object based on it.Any idea what policy we need to grant in order to pass the getS3AccountOwner test method succesfully?Many thanks!
Unfortunately the Connected System does not provide ACL permission updates. This should be configured in the AWS console.
Hi there, we are wanting to set the acl on the s3 object to
ACL="bucket-owner-full-control" - is this parameter (or variants of this) able to be passed through the connector
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"
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.
© 2020 Appian. All rights reserved.