Questions tagged with Amazon ElastiCache for Redis
Content language: English
Sort by most recent
Elasticache shows network in and out as exceeded, but how?
I have a small redis instance running in Elasticach with one shard running with clustering mode off. It is showing that we have exceeded our network bandwidth in and out: ![Enter image description here](https://repost.aws/media/postImages/original/IMTwiqe9n0SwaUaYSxdwLnYQ) It also shows that we're barely using our network, with peaks below 30Mbps: ![Enter image description here](https://repost.aws/media/postImages/original/IMdacaB5xrSZOUqBFIgvgFUw) That's not much bandwidth that we're using, but to confirm what we have available, I went to the [pricing page](https://aws.amazon.com/elasticache/pricing/), which says that my instance (`cache.t4g.small`) provides "Up to 5 Gigabit" of network performance. Seems like 30Mbps is a lot less than 5Gbps! Is this an error in the metrics reporting or am I missing something? Should I be worried about the exceeded bandwidth problems? If so, I don't have many options. The next bigger instance that provides more network performance is a `cache.m6g.large`, which costs about 10× what I'm paying now! I'm not doing anything crazy with this cache. I'm surprised I'm running into all this. ## Edit, after scale-up Per comments, I scaled up Elasticache to the next size bigger, which has twice the baseline network capacity. I hoped this would remove the exceeded network problem or at least halve it, but it seems to have made no impact at all. Here's the latest charts. The spike in the middle is the scale-up event (when the entire DB was copied to the larger instance), so left of the spike is the small instance, right of it is the larger one: ![Enter image description here](https://repost.aws/media/postImages/original/IMzk4rBxTCS-KOJYuhk2KXxw)
Elastic BeanStalk can't connect to ElastiCache Redis
I'm having issues connecting from Elastic BeanStalk to ElastiCache Redis. When I SSH into the EBS instance and try to use redis-cli to connect, it times out. This is how I set up my environment: I have an existing VPC with two subnets. I created a Security Group specifically for this that has an Inbound rule for IPv4, Custom TCP, port 6379, source 0.0.0.0/0 I created an ElastiCache Redis cluster with the following relevant parameters: Cluster mode: disabled * Location: AWS Cloud, Multi-AZ enabled * Cluster settings: number of replicas - 2 * Subnet group settings: existing subnet group with two associated subnets * Availability Zone placements: no preference * Security: encryption at rest enabled, default key * Security: encryption in transit enabled, no access control * Selected security groups: the one I described above As for the EBS environment, it has this configuration: * Platform: managed, Node.js 16 on Amazon Linux 2 5.5.3 * Instance settings: Public IP address UNCHECKED, both Instance subnets checked * Everything else left default After getting all of that set up, I would SSH into the EBS instance and follow the directions here to install redis-cli and try to connect: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/GettingStarted.ConnectToCacheNode.html I've tried using the Primary endpoint, the Reader endpoint, and all of the individual node endpoints, but I get a timeout error for all of them. Is there some configuration that I'm missing?
Accessing Elastic Cache Redis from Celery in a docker-compose locally
Dear all, I am developing a python FastAPI application that uses Celery and Redis. So far I have run these services locally using docker-compose and everything worked fine. I would now like to use the Elastic Cache Redis instance from my company, however I have problems connecting to it. According to celery documentation https://docs.celeryq.dev/en/stable/userguide/configuration.html#std-setting-broker_url the CELERY_BROKER_URL should be `redis://:password@hostname:port/db_number` or `transport://userid:password@hostname:port/virtual_host `. Until now I simply had `redis://redis:6379/0` because I had redis running locally, however I am unsure about what to put when using the remote instance. I have tried using the `Primary endpoint` as the `hostname`, the `Account ID` as `userid` and the token as the password, is this correct? Also, is it actually possible to access the remote instance locally from celery?
Elasticcache scaling up takes time
Hi Team, I have configured dynamic scaling for elastic cache for 80% memory usage, adding shards. Configurations : 1- 3 primary 2- 2 replica each 3. cache.r6g.large When it's triggering up, AWS elastic cache modifying the cluster is taking up. Sometimes more than an hour for 14GB of instance. The impact is when modifying timeout is happening in the application. Is there any way to avoid this ?
When creating an elasticache global datastore group, does it affect the resources in the primary region elassticcache?
Assume that elaticcache is configured in area A. If I configure a global data store group and create elasticcache in region B, will it affect elasticcache in region A? Is it necessary to increase the memory of elatsticcache in area A or to increase the type?
Security group outbound rules for RDS, ElastiCache, EFS
We are using RDS PostgreSQL, ElastiCache Redis and EFS as managed services. For each service we have currently our security group allow any IPv4 outbound connections. We want to restrict this. Do we need to add any specific protocols/ports/destinations so that AWS can maintain the managed services, i.e. for performing updates?
Error on browser to open "redis create cluster"
Problem upgrading AWS ElastiCache Redis cluster
Upgrade of ElastiCache fails with the following error: *The selected service updates could not be applied on the following redis clusters: Error Type: InvalidParameterValueException : Error Message: The service update cannot be applied to global replication groups Trying to apply the upgrade from the Global DataStore page gives the following error * ModifyGlobalReplicationGroup API does not support cache parameter group modification without a change in major engine version
Elasticache for Redis cluster service update got stuck
We applied 'elasticache-redis-6-2-update' Service Update for our 1-node Redis cluster in ElastiCache but update got stuck. Currently cluster is in 'modifying' status for more than 4 hours. Is it possible to stop/cancel/rollback service update procedure?