DynamoDB EPROTO workaround no longer required, DynamoDB uses tls 1.2 now
jnngrm opened this issue · comments
See comment from chrisradek Jun 29 (towards bottom)
aws/aws-sdk-js#862 (comment)
Once http agent options removed, EPROTO error (mitigated) will go away. Right now the workaround works somewhat, but still plenty of hits on it even with mitigation. I suspect that the TLSv1_method option is holding aws-sdk back at TLS version where this happens, once removed hopefully the security will auto upgrade to TLS 1.2 based on handshake.