If you read the rest of that thread (I know, it’s long) you can see that the problem was fixed back in Jun 2016 when DynamoDB moved to TLS1.2. The issue was caused by a bug in openssl which the DynamoDB service used at the time.