File Upload to Amazon s3 errors

[Tbrondolo]

What method are you using to display the pictures?

[mikeallenbrown]

Pictures stored in S3 won't show up in a gallery now under these settings. S3 is awfully complex. For me anyways. Seems I got a lot of reading ahead of me.

[Tbrondolo]

Just send you a PM. Happy to take a look NC

[SteveK3003]

No Joy Here... I get a error code but the description of the error is truncated to the point that I can't derive the details. Tom would you be willing to look at my setup and help for a fee?

[Tbrondolo]

I should add that if you don't lock down the Public ACCESS then anyone with a formatted URL can upload or download from your S3 storage location.

[peteconway]

Thanks for getting back to us. Glad it's sorted.
Pete

[Tbrondolo]

CORS issue solved.

With Selywn’s help we have a configuration that works for secure upload and download on signed URL’s.

S3 Settings
1. PUBLIC ACCESS – On the public access dialog in Block Public Access for all but the first option. So you are allowing access granted through new access control lists.

Block all public access
Off
Block public access to buckets and objects granted through new access control lists (ACLs)

LEAVE ALL OTHERS TURNED ON - GREEN

1. Remove any Bucket specific policies This should be empty. Maybe it's me, but when I try to add a bucket policy I get CORS errors on upload.
2. Use one of the CORS settings.

For testing from localhost I suggest a wildcard configuration on the Allowed Origin, see below. For production you can lock it down with the specific domain https://example.com. In this configuration requests will only be accepted from the specified domain (it won’t work from localhost). There are methods for adding local host that you can find on the Internet. I find it just as easy to go into S3 and update the CORS.

[
{
"AllowedHeaders": [
"Content-Type",
"x-amz-acl",
"origin*"
],
"AllowedMethods": [
"PUT"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]

[Tbrondolo]

So using Firefox I was able to see more detail on the request headers. What I found is the following

Origin

https://brondolo.com

Referer	https://brondolo.com/

I believe the origin and referer have to match exactly. So what I see is an extra slash on the Referer.

This is from the File Upload S3 action javascript method. I don't know if this is the issue but I have passed it on to Selwyn.

[SteveK3003]

Jay,

Thanks, for this. I imported you file and updated the data connection to match my set up and got the same error. I suspect the problem is the security settings in my S3 though I don't know how. As you noted, the CORs policy shouldn't be the problem

Steve

[Jay Talbott]

It appears the function I mentioned is not available in 7295. The documentation says it is available in 4.6.2.7 + versions. 7295 is 4.6.2.6.

I got the action javascript to work in 7704. When I opened the same component in 7295, it also worked. For what it's worth, I attached it below. You need to either rename your connection string to match mine in the Action Javascript, or vice versa.

My CORS policy is the same as yours.

Hope that helps.
Jay

jsFileUpload_06012021.zip

[Tbrondolo]

Hi Jay,

So I've run into a block on using the a5storage_saveFile(). I want the end user to upload the file which means I need the fully qualified path of the file and it seems you can't get that through the browser. Although there must be someway that Alpha gets that for it's own upload functions. Do you know of a method to get the full filename and path or are you just using this to move files from the Alpha server to S3?

Thanks
Tom

[Tbrondolo]

Hi Jay,

So when I try to run that function it tells me it's not available and it dosen't show on the function list in xbasic. (i'm on build 7295) although the function is in the documentation.

On a positive note I did get the a5storage_saveFile() function to work. The function works with or without a bucket policy. Have you tried the action javascript FileUoload function as that is what is not working for me.

For now I'm going to build around the a5storage_saveFile() function.

I wish I knew more why some of these things work and others don't.

Also, just for comparison what do you have for a CORS policy?

Thanks
tom

[Jay Talbott]

Am I missing something here? My bucket policy is empty, my bucket is set to block ALL public access, and I can easily copy files to my bucket using

a5storage_copyfiles("MyStorageStringName","C:\aFolderName\aFileName.doc")

AmazonBucketPolicy.png

[Tbrondolo]

Hi Steve I am having and have been having a similar problem. I have spent about the same amount of time as you and I have been looking and willing to pay for support. Where I'm at, is if I make the bucket public I can upload and download. If I make the bucket private I can only download with the following CORS and Bucket settings. I have tried a hundred variations of these policies with the same result, Access denied on upload.

If you find someone who can figure this out let me know. I'll do the same.





Bucket policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1619377508586",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::9999999999:root"
},
"Action": "s3:PutBucketPolicy",
"Resource": "arn:aws:s3:::bbbbbb"
}
]
}



Cors Policy

[
{
"AllowedHeaders": [
"Content-Type",
"*",
"*"
],
"AllowedMethods": [
"PUT"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]

[SteveK3003]

I believe so. Here is what I have set

[
{
"AllowedHeaders": [
"Content-Type",
"x-amx-acl",
"origin"
],
"AllowedMethods": [
"PUT"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]