Python连接AWS Redis超时问题排查与解决求助

Looks like you're hitting a classic connection timeout with AWS ElastiCache Redis—let's break down the fixes step by step, since I've debugged this exact issue a bunch of times.

First, let's recap your code (I fixed a tiny Python 3 syntax error in the print statement that would have caused an extra issue):

import redis, time, datetime, sys
endpoint='myred-0041.dpchko.0001.amazonaws.com'

def prepareConn(endpoint):
    r = redis.StrictRedis(host=endpoint, port=6379, db=0, socket_timeout=1)
    return r

r = prepareConn(endpoint)
while True:
    print(datetime.datetime.now())
    try:
        print(r.set('foo','bar'))
    except:
        print("Unexpected error:", sys.exc_info()[0])  # Fixed Python 3 print syntax
    time.sleep(1)

Now let's go through the most likely causes and fixes:

1. AWS Security Group Misconfiguration (Most Common!) #

• Your Redis ElastiCache instance uses a security group to control inbound traffic. Make sure:
  • The security group attached to your Redis instance allows inbound connections on port 6379 from your client's IP (if testing locally) or the security group of your EC2 instance (if running code on AWS).
  • If testing from your local machine, add your public IP address (e.g., 123.45.67.89/32) as an inbound rule for port 6379 in the Redis security group.

2. VPC/Subnet Access Restrictions #

• If your Redis instance is in a private subnet, your client (local machine or EC2 in a different VPC) can't reach it directly. Options here:
  • Enable "Public access" for the Redis instance (only for testing—avoid this in production). Toggle this in the ElastiCache console under "Modify" > "Network settings".
  • Use a VPN, Direct Connect, or VPC peering to connect your client's network to the Redis VPC.
  • If running code on AWS, ensure your EC2 is in the same VPC as the Redis instance.

3. Verify the Redis Endpoint #

• Double-check that the endpoint string is exactly what's listed in the ElastiCache console. It's easy to miss a character or copy a trailing space—even a tiny typo will cause timeouts.

4. Adjust Connection Timeout and Error Handling #

• Your current socket_timeout=1 is really short—AWS Redis can take a few seconds to establish the first connection, especially for new instances. Try increasing it to 5 seconds:

  r = redis.StrictRedis(host=endpoint, port=6379, db=0, socket_timeout=5)
  

• Also, catch specific exceptions instead of a broad except block—this will give you more detailed error messages to debug:

  try:
      print(r.set('foo','bar'))
  except redis.exceptions.ConnectionError as e:
      print(f"Redis connection failed: {str(e)}")
  except Exception as e:
      print(f"Unexpected error: {type(e).__name__}: {str(e)}")
  

5. Check Redis Instance Status #

• Head over to the ElastiCache console and make sure your Redis instance is in the Available state. If it's still creating, updating, or in maintenance, connections will fail until it's ready.

Give these steps a try—9 times out of 10, it's either a security group or VPC issue. If you still hit problems, share the specific error message from the improved exception handling, and we can dig deeper!

内容的提问来源于stack exchange，提问作者Amaal Zohny