The content S3 bucket associated with your application identifier can contain drawing files you can access by passing its S3 file key to the “file” query parameter. The S3 file key is just the relative path of the file inside the bucket. As it is passed in a query parameter you have to make sure that it is url encoded.
Example url from our https://graebert.atlassian.net/wiki/spaces/KUDOPARTNER/pages/1183154352/Samples#2.-Open-file-for-editing-from-S3-bucket-with-customized-style : https://app.kudo.graebert.com/editor?file=demo3.dwg&auth=demo3&userId=demouser
To open a file from the S3 bucket with Kudo, you need to make sure that Kudo has at least read access to it. This will be sufficient if you use Kudo only as a viewer. If you use Kudo in edit mode, it will also require write access.
To allow s3 bucket access to Kudo, put a bucket policy on the partner s3 bucket allowing the desired actions to Kudo account : 649336859113
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PermissionsforKudoAccount",
"Effect": "Allow",
"Principal": {
"AWS": [
"arn:aws:iam::649336859113:root"
]
},
"Action": [
"s3:PutObject",
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::kudo-demo-content",
"arn:aws:s3:::kudo-demo-content/*"
]
}
]
}
We need to have an IAM policy to xenon EC2 roles to allow operations on the bucket
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PermissionsForCustomerContentBucket",
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject"
],
"Resource": [
"*"
]
}
]
}