Questions tagged with Amazon ElastiCache for Redis

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

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)
2
answers
0
votes
3370
views
asked 5 months ago

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?
1
answers
0
votes
274
views
asked 6 months ago