Amazon S3 Connection Problems on RDM for Windows

Amazon S3 Connection Problems on RDM for Windows

avatar

RDM version : 10.1.0.0
- created AWS AMI User just for RDM
- created S3 bucket
- give RDM user full admin access to S3
- tested access to S3 bucket by logging in as RDM user and creating/deleteing files in this bucket
- uploaded empty file sessions.xml to RDM bucket (as per one of older posts RDM does not create new sesssions.xml in S3- bug to be fixed ?)

Amazon S3 data source stays "Not connected"
Errors from Application Log :
- An Error, number AccessDenied, occurred when reading an object with the message 'Access Denied

- Amazon.S3.AmazonS3Exception: Access Denied ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at Amazon.Runtime.AmazonWebServiceClient.getResponseCallback(IAsyncResult result)
--- End of inner exception stack trace ---
at Amazon.Runtime.AmazonWebServiceClient.HandleHttpWebErrorResponse(AsyncResult asyncResult, WebException we)
at Amazon.Runtime.AmazonWebServiceClient.getResponseCallback(IAsyncResult result)
at Amazon.Runtime.AmazonWebServiceClient.endOperation[T](IAsyncResult result)
at Amazon.S3.AmazonS3Client.GetObject(GetObjectRequest getObjectRequest)
at Devolutions.RemoteDesktopManager.Business.DataSources.S3ConnectionDataSource.cdee935ce1813488c0c594a5aa9fb9b12()
at Devolutions.RemoteDesktopManager.Business.DataSources.S3ConnectionDataSource.GetConnections()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.ca4799bebd8b706f34eea94a778843b55(BaseConnectionDataSource c01af917dca3518ff73ed69848f95f91a)

Error looks pretty obvious i.e. Access Denied, but as per my list above. I did managed to login to S3 as freshly created RDM user with
key/secret key and upload download sessions.xml file.

What is even more interesting, Mac version or RDM is able to access and use those S3 credentials and connection session works there ok.

I hope I am just missing something obvious ... :), any help appreaciated.
edited by dhervieux on 12/12/2014

All Comments (7)

avatar

Hello,

Have you left the bucket name to blank or specified it in the settings? Could you try both ways just to see if it reacts differently?

Thank you,

Maurice

avatar

Hi Maurice

I am unable to leave bucket name empty it gives message "The bucket name is required!"
I have attached screenshot.

Never the less I am not sure how it could work without bucket name, you have to specify some containter in which
your .xml file needs to be placed ?

Regards

bucket.png

avatar

Hello,

You are correct about the bucket name, I was thinking of our S3 Explorer

Let me test it out,

Maurice

avatar

Hello,

It works on my end.

As you said, Access Denied should be obvious to find, but you say that it does work.

Do you have access to a Diff tool to compare your data source definitions?

Best regards

Maurice

avatar

I am getting the same error when setting up a new datasource with RDM.

avatar

Hello,

What version of RDM are you running?

Older versions had a bug that you had to create the xml file manually in your bucket before being able to use it.

Maurice

avatar

10.1.9.0.

I did try creating it as well.
edited by mrjester on 2/28/2015