- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello!
Errors with Elasticache Redis during the connection establishment process such as SocketClosedUnexpectedlyError
are typically due to some sort of configuration issue occurring when attempting to connect to the cluster. This includes situations such as:
-
Your cluster has in-transit encryption (TLS) enabled, but your client/application is not using TLS when attempting to establish a connection (https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html).
-
Too many new or existing connections in the cluster (during the point in time when the connection attempt was made) to where new connections are not being accepted (which may require reviewing how your application handles connections, such as if connection pooling is used or not https://aws.amazon.com/blogs/database/best-practices-redis-clients-and-amazon-elasticache-for-redis/).
I would first recommend making sure you can establish a connection to the cluster from the instance/machine that your application/client is running in (see this guide for instructions on how to perform this https://repost.aws/knowledge-center/elasticache-connection-test).
Should you require further assistance with this, please create an AWS support case with additional details such as the cluster ID and timestamp (in UTC format) of when the connection attempt was made to get in touch with an available engineer.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Hi, Its seems that you successfully create the client, but its fail to connect. Your code is failing on /var/app/current/node_modules/@redis/client/dist/lib/client/socket.js:194:118 which is part of the socket connection. Its hard to say from the info shared what could be the problem, can you please share a bit more info? maybe try to add error logging to the connection. Please check that your configuration are right, as access from your app to your Elasticache.