I have an EKS cluster and trying to connect the application pod to the ElastiCache Redis endpoint. Both are in the same VPC. I allow the communication between both EKS and ElastiCache Redis.
When I telnet from a pod to the ElastiCache Redis endpoint is connected. But Unfortunately, I access from my nodejs application in won't work.
Can somebody help me to resolve this?
Related
I have an EKS cluster where I have a Keycloak service that is trying to connect to RDS within the same VPC.
I have also added a inbound rule to the RDS Security Group which allow postgresql from source eksctl-prod-cluster-ClusterSharedNodeSecurityGroup-XXXXXXXXX
When the application tries to connect to RDS i get the following message:
timeout reached before the port went into state "inuse"
I ended up replacing the inbound rule on the RDS Security Group from the eksctl-prod-cluster-ClusterSharedNodeSecurityGroup-XXXXXXXXX with an inbound rule allowing access from the EKS VPC CIDR address instead.
I want to deploy my full stack application using AWS EKS, with the backend pod connected to the databases(MongoDB hosted on AWS managed service) outside of the cluster. If the EKS cluster and the databases are in same VPC, how should I configure the pod to connect exterbal database but within same VPC.
We're going to need a bit more details, but see if this blog gives you an idea about how to accomplish this.
So I'm stuck in a problem, the hassle is I'm getting a connection timeout error after connecting to an elasticache endpoint using aws lambda and nodejs.
My aws lambda function is not using any vpc but an elasticache function of course has VPC and I already made it public by setting up the inbound traffic and outbound traffic rules.
Also I tried it on my local server and was not able to find elasticache endpoint msg by using OVPN.
How to connect redis from elasticache in nodejs.
I would really appreciate it if any of the people can give me a helping hand to solve this problem.
Thanks
I'm new with golang.
I've been looking documentation of lambda-golang-AWS and still had this timeout in when invoking the function.
I've been configuring:
Elasticache cluster (1 primary node),
VPC (one same VPC for redis and lambda),
Security groups,
Subnets,
Inbound and outbound,
role
I have this primary Redis endpoint xxxxxx
I just need an example.
So, my questions are:
Can we connect Redis in Linux without an EC2 instance? Possibly try it with RDM.
How do we put AWS redis's endpoint in the main function? (do we only need the endpoint? or else)
Is it possible to connect to Redis Elasticache with only endpoint (without AUTH)?
Thanks a lot!
Can we connect Redis in Linux without an EC2 instance?
Yes, of course, why would an EC2 instance be an additional requirement? You just need to include a Redis client library in your Lambda function's deployment artifact, and configure the Elasticache cluster to allow inbound traffic from the security group assigned to the Lambda function.
How do we put AWS redis's endpoint in the main function? (do we only
need the endpoint? or else)
I would configure the endpoint as one of the Lambda function's environment variables.
Is it possible to connect to Redis Elasticache with only endpoint
(without AUTH)?
If you don't enable AUTH on Elasticache, then you can connect without AUTH. AUTH is an optional configuration setting.
I have a Node app running on Elastic Beanstalk.
I also have a CloudFormation MongoDB cluster with 1 replica. I can connect to this directly by using the ec2 private IP 111.22.3.44 it's named PrimaryReplicaNode0.
However I keep getting MongoDB master slave errors so I don't think I'm supposed to connect to this directly. Which address am I supposed to use from within Elastic Beanstalk to connect?
Do I connect directly to the EC2 replica address or do I use a subnet of some sort?
Both the MongoDB cluster and Elastic Beanstalk servers are in the same VPC.
Connected to mongodb named app1 at 172.00.1.XX
Express https server listening on port 8081 in development mode
{ [MongoError: connect ETIMEDOUT 172.00.1.XX:27017]
name: 'MongoError',
message: 'connect ETIMEDOUT 172.00.1.XX:27017' }