S3 Data Copy to Bucket with Object Lock

Hello Steven,

Thank you for contacting us on that matter!

Which version of RDM and what type of Data Source you are currently using? Also, do you experience the same error if you copy a file into the same bucket outside of RDM?

Best regards,

Hi,

The latest and greatest


If I use Powershell I have to compute the MD5 hash, I believe this is a requirement

$hash = Get-FileHash .\test.txt -Algorithm md5
$hashByteArray = [byte[]] ($hash.hash -replace '..', '0x$&,' -split ',' -ne '')
$hashb64=[System.Convert]::ToBase64String($hashByteArray)
write-S3Object -BucketName <S3 Bucket Name> -File c:\temp\test.txt -ProfileName temp -HeaderCollection @{ 'Content-Md5' = $hashb64}

The file now exist in the S3 bucket

Hello,

Thank you for your response!

I will contact our engineering team regarding your case to see what could be done to solve this issue.

We will get back to you as soon as we have new information to share!

Best regards,

Hello,

A ticket has been opened with our Engineering Department to see what can be done.
We will be in touch as soon as we will have an update to provide.

Best regards,

Hello,

A fix for this issue has been deployed and will be available in version 2022.2.13.0.

Regards

Thank you, is there an ETA when 2022.2.13.0 will be released?

Hello Steven,

The 2022.1.13 version is now available, you can download your preferred installer format from our website, or by doing a check for update in RDM.
https://devolutions.net/remote-desktop-manager/home/downloadenterprise

Let us know if the issue is fixed in this release.

Best regards,

Hi,

I've tested the new update and it looks to be working as expected, I can upload data into an Object locked bucket.
I had to make on minor change to the S3 Browser item and specifying the region (Asia Pacific (Sydney)), if left as "Default" it threw the below error message

Hello,

Indeed, when opening a specific bucket, the correct region now has to be chosen in the entry settings. (Default refers to US East (Virginia))

Before, we were able to switch automatically to the correct region by getting the info directly from AWS, but this required extra permissions (ListAllMyBuckets and GetBucketLocation). These permissions are otherwise irrelevant in that context, and in some user cases impossible to attribute, so we made the choice to use the region configured in RDM directly.

Regards