Error: DynamoDB Network Error: self signed certificate in chain
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 connection timeout
- aws lambda dynamodb nodejs not working after few puts
- missing required key 'key' in params dynamodb
- aws.dynamodb.documentclient is not a constructor
- ImportError: No module named boto3 (DynamoDB)
- aws.dynamodb.converter.unmarshall not working
- sls dynamodb install not working
- ConfigError: Missing region in config
- AWS DynamoDB errors ResourceNotFoundException
- Float types are not supported. Use decimal types instead.
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- Unable to start DynamoDB Local process
- dynamodb: one or more parameter values were invalid: type mismatch for index key
- accessdeniedexception dynamodb
Spend less time in the AWS console, use Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2023 Dynobase