Want this feature implemented, too? Please upvote by clicking Thumbs up!
(Posts as a reply won't be published in this feature request thread. Read Me!)
As a PRTG User, I want to use TLS 1.2 and, when supported by AWS, TLS 1.3.
Details of User Story
I have TLS 1.0 and lower disabled in my environment (PRTG Network Monitor 220.127.116.119 x64 on Windows Server 2012 R2). This results in the following errors from, for example, the Amazon Cloudwatch EC2 sensor in the gui:
|Could not create the sensor Amazon CloudWatch EC2 BETA on device MyDevice (x.x.x.x). A WebException with status ReceiveFailure was thrown.|
Manually running the sensor results in the following:
AWSv2.exe -ak="ACCESSKEY" -sk="SECRETKEY" -service="EC2" ?<?xml version="1.0" encoding="utf-8"?> <prtg> <error>1</error> <text>A WebException with status ReceiveFailure was thrown.</text> </prtg>
In .net 4.5, the default is only Ssl3|Tls. this can be expanded with System.Security.Principal: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls | SecurityProtocolType.Ssl3;
- Have TLS 1.2 working
- Have TLS 1.3 working, once released