-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Description
When attempting to connect to an ElastiCache instance running in Redis Cluster mode using the --elasticache flag, the process fails during the Fargate container startup phase.
It seems to work fine with other configurations (non-cluster), but fails specifically when a cluster node is selected.
Reproduction Steps
- Run
7777 --elasticache --verbose - Select an ElastiCache instance that is part of a Redis Cluster (e.g.,
cluster - redisorcluster - valkey). - Wait for the Fargate container to start.
Expected Behavior
The Fargate container starts successfully, and the tunnel is established.
Actual Behavior
The tool waits at "Starting the Fargate container" and eventually fails with a ResourceNotReady error.
I checked the AWS Console, and the Fargate task status remained in PENDING state. Also, no logs were output.
Logs
$ 7777 --elasticache --verbose
Using the AWS region ap-northeast-1.
Validating the 7777 license.
Generating unique RSA keys for the SSH tunnel.
Checking if the port 7777 is available.
Port 7777 selected.
Listing ElastiCache instances and serverless caches.
Which Elasticache instance would you like to connect to?
[1] xxxx-sample-prd-redis-0001-001 (cluster - redis - cache.m5.xlarge)
[2] xxxx-sample-prd-redis-0001-002 (cluster - redis - cache.m5.xlarge)
...
: 1
Selected cache xxxx-sample-prd-redis-0001-001.
Using subnet subnet-xxxxxxxxxxxxxxxxx
Checking if 7777 is set up in the AWS account.
7777 is already set up, moving on.
Retrieving the container security group.
Retrieving the computer's IP address.
Authorizing xxx.xxx.xxx.xxx on the security group.
Starting the Fargate container.
ResourceNotReady: Resource is not in the state tasksRunning
Code: ResourceNotReady
Environment Information
- OS: macOS
- 7777 version: 1.1.29
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels