ColdFusion 2016 / 2018 and Amazon S3





Hello everyone,

Does anyone know if ColdFusion 2018 has an updated connection to Amazon AWS S3? I am getting this error from ColdFusion 2016: "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256."

This happens for newer regions since Amazon updated their encryption for any S3 regions added after 2014.

  
Thank you for any help you can provide!
Unfortunately, ColdFusion 2018 does not natively support v4 signing, which is required for regions added after September, 2014. Please request this feature on the [Adobe bug tracker](https://tracker.adobe.com/), and it may be addressed in a future release.You can use the AWS Java SDK, which has v4 signing built in. I'm writing [a series on using the AWS Java SDK from ColdFusion](https://brianklaas.net/), and there is an entry on [the basic steps you need to go through to use the AWS Java SDK from within CF.](https://brianklaas.net/aws/coldfusion/2018/05/21/Basic-Setup-Needed-To-Access-AWS-From-CFML.html)
i think it’s too early to think about h.266.

in any case if it will be supported then you need new hardware. [orafik](/members/orafik) thanks, unfortunately this is for an older version that i am not using. i actually found one 

<https://support.solarwinds.com/successcenter/s/article/setup-ssl-and-enable-smart-card-cac-pki-user-authentication-for-orion-web-console?language=en_us> a search for other 1106 error posts shows you really do need to contact support, as it says. 
[login to cloudflare](https://dash.cloudflare.com/login) and then [contact cloudflare support](https://dash.cloudflare.com/?account=support) by clicking on the get more help button. for everyone who may have the same question:
it is not supported by microsoft to use gmsa accounts for scsm and scorch. We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … hmm…i wonder why it didnt

fine buddy

is it community edition or enterprise edition

if its enterprise edition of orchestrator kindly raise a ticket to technical team

[image]

[contact technical support](https://www.uipath.com/company/contact-us/contact-technical-support)

contact uipath technical support department.

cheers [@brun…](/u/bruno_silveira_uy) after further research and coming across [this answer to a similar issue](https://community.auth0.com/t/failed-silent-auth-login-required/33165/39), i made the switch to auth0’s custom domain solution and it fixed all of the issues mentioned above. this topic can be closed! missing ws in the end of the url.

wss://fstream.binance.com/ws hi kenhaught, thanks for your replies. i finally fixed the problem. i had built the vms on a previous version of esxi, version 5.5, so they had an earlier vm version of the hardware. once i updated the hardware version, of the guest, to "esxi 6.5 and later (vm version 13)" the windows server 2016 option appeared.