- Newest
- Most votes
- Most comments
Based on the information provided, it appears that you're experiencing connectivity issues between your live production environment and your AWS DynamoDB backend. This could be due to several factors:
-
Network connectivity: There might be network issues preventing your live production environment from reaching the DynamoDB endpoints. This could explain why it works locally but not in production.
-
Security groups or firewall rules: Check if there have been any recent changes to your AWS security groups or firewall rules that might be blocking traffic from your production environment to DynamoDB.
-
SSL/TLS connection issues: There could be problems establishing a secure connection between your production environment and DynamoDB. This is particularly relevant if you're seeing "ERR_EMPTY_RESPONSE" errors, which can sometimes occur due to SSL/TLS negotiation failures.
-
DynamoDB service issues: While less likely, there could be ongoing DynamoDB service issues in your specific region.
To troubleshoot this issue:
-
Verify that your production environment can reach the DynamoDB endpoints. You can test this by trying to access a DynamoDB endpoint URL (e.g., https://dynamodb.[your-region].amazonaws.com) from your production server.
-
Check your AWS security groups and network ACLs to ensure they're not blocking traffic from your production environment.
-
Review your SSL/TLS configuration. Ensure that your production environment trusts the Amazon Trust Services (ATS) Certificate Authority, which is now used for DynamoDB connections.
-
Check the AWS Service Health Dashboard and your AWS Account Health Dashboard for any ongoing DynamoDB issues in your region.
-
Review your application logs for any specific error messages or request IDs that could provide more insight into the problem.
If you continue to experience issues after these steps, it would be advisable to open a support case with AWS, providing details such as the impacted DynamoDB tables or secondary indexes, the time window when the errors were observed, and any relevant DynamoDB request IDs from your application logs. This will help AWS support team to investigate and resolve the issue more quickly.
Sources
Troubleshooting internal server errors in Amazon DynamoDB - Amazon DynamoDB
Troubleshooting SSL/TLS connection establishment issues with DynamoDB - Amazon DynamoDB
answered 2 years ago
Relevant content
asked 9 months ago
asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago

My Target group is showing health check Failed:
This target's zonal shift state is not available through DescribeTargetHealth but can be viewed directly through the Amazon ARC API or console. Health Check Failed!
How to resolve this issue!
My Target group is showing health check Failed:
This target's zonal shift state is not available through DescribeTargetHealth but can be viewed directly through the Amazon ARC API or console. Health Check Failed!
How to resolve this issue!