Error: DynamoDB Network Error: self signed certificate in chain

Answered by Rafal Wilinski
Solution
Explanation: DynamoDB SDK/CLI has a problem negotiating SSL with AWS' servers.
Troubleshooting steps:
- If you're running this command behind a firewall, make sure it's not blocking for modiyfing requests to the AWS. Try disabling the firewall and try again
- If you're using Node.js, you can try setting NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0.
- Disable SSL (not recommended)
- If you're using Node.js, you might also want to import the certificate manually:
const https = require('https'); const fs = require('fs'); const customAgent = new https.Agent({ ca: fs.readFileSync('/etc/ssl/path/to/your/certificate/myCustomCA.pem')}); AWS.config.update({ httpOptions: { agent: customAgent } });
Other Common DynamoDB Errors (with Solutions)
- DynamoDB FilterExpression not working
- dynamodb query is null
- dynamodb could not connect to the endpoint url
- moto dynamodb not working
- dynamodb attribute does not exist
- DynamoDB Error 413
- dynamodb could not instantiate class
- dynamodb does not support null values
- dynamodb request is missing authentication token
- dynamodb property projection cannot be empty
- KMS Key Access Denied Error DynamoDB
- DynamoDB No Regionendpoint Or Serviceurl Configured
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- DynamoDB ConditionalCheckFailedException
- an expression attribute name used in the document path is not defined
Spend less time in the AWS console, use Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase