Am unable to get the SaveFile working; always get the same error "Access Denied".
Am sure about my Token and have used it in different applications and the aws-cli. I see a lot of attributes for the S3File and the ProxyDetails which are all mandatory and am unsure of what goes where
Paolo, do you need to use the proxy? If not, then set UseProxy to False and you can pass blank string values for the proxy parameters.
Also just make sure you have the access key and secret key the right way round.
Hanno
I have uploaded a new version (still under development) of the component where the proxy details are not mandatory.
Paolo, can you perhaps send a more detailed error log from Service Center? It might help us out in identifying where the issue is.
Thanks for the quick reply.
Down below is what I am setting for the S3File values and the stack trace of the error
Your settings look fine from what I can see.
Here is how I have used it in the past:
As mentioned before, please check your Access Key and Secret Key values that you have them mapped to the correct property of the Amazon Token.
If that doesn't work, all I can think is that your Access/Secret key pair does not have access to the bucket on S3.
Hanno wrote:
Thanks for the reply; the token is mapped properly, so still not sure what is wrong.
Could you give an example for the raw value for the Bucket? maybe it is formatting or something else.
Does it make a difference whether there is a SubFolder or NewSubFolder? Maybe certain items can't be the same value?
Also just realized, how does the region get set? it is possible that I am pointing to a different region.
No, you don't need to be concerned about the region as that is linked to the bucket on AWS's side.
The SubFolder is a folder under the "root" path, which is your bucket name.
NewSubFolder is used when you attempt to create a duplicate file in SubFolder.
I cannot divulge an actual bucket name, but it looks something like this: application-env