Browse through the questions and answers listed below or filter and sort to narrow down your results.
Uncaught RedisClusterException: Can't communicate with any node in the cluster in /home/cloudpanel/public_html/RedisCache.php
Hello Everyone, We are getting "Uncaught RedisClusterException: Can't communicate with any node in the cluster in" this error. We are using Elastic Cache redis cluster with 2 node and cluster mode was enable PHP library ==>https://github.com/cheprasov/php-redis-client we are using this library. This error randomly occurs in our websites. At the time of error Elastic cache load was normal. Is there any way to trouble shoot this issue.
Private Instance and Public ELB HTTPS Problem.
My VPC structure looks like this: VPC: 1 Public Subnet : 2 (1 Public Instance in each Subnet) Public ELB : 1 (Public ELB for Public Instance above) Public Subnet : 1 (for NAT Gateway) Private Subnet : 1 (1 Private Instance) Here, the Private Instance should connect to the Public ELB. At this time, HTTPS communication should be established between the Private Instance and the Public Instance behind the ELB, but HTTPS communication is not possible because the Public ELB is playing an intermediate role. How can I solve the problem? Or is the structure wrong?
Is it possible Private EC2 Instance send outbound traffic to Public ELB?
Here is the AWS structure I created. - VPC : 1 - Public Subnet : 2 (1 EC2 Instance in each Subnet) - Public ELB : 1 (About Public Instance) - Private Subnet : 1 (1 EC2 Instance) Here, I want to make a request to the Public ELB from the instance in the Private Subnet. How can I do this? Or did I get the structure wrong?
Is the Overlay IP CIDR range for SAP on AWS just a secondary CIDR range added to same VPC?
I was reading [the docs on HA configurations for SAP on AWS](https://docs.aws.amazon.com/sap/latest/sap-hana/sap-hana-on-aws-ha-configuration.html), and I see that you need a non-overlapping CIDR range to draw your overlay IP from. Is that just a secondary CIDR range that you need to add to the VPC in which your SAP cluster lives?
Healthd service not sending data to ElasticBeanstalk
Hi, I'm deploying an app on tomcat8 on 2 t3.micro instances hosted both on a private subnets with NAT access to 2 public subnets, and registred as targets on an Application loadbalancer. My environment works well except that it doesn't receive data from the instances for the enhanced health check. I've checked `/var/log/healthd/daemon.log` and find this error `Aws::Errors::MissingCredentialsError) unable to sign request without credentials set. Backing off by 200 seconds in addition to delay interval` as a Warning when I was assigning public IP addresses to my instances and a classic loadbalancer the health checks pass but now it doesn't. Is there another config to add in order to make it work ? Thanks
connect to an internal sftp server from outside private vpc (on prem)
Hi team, I have a private VPC with all private subnets, I create an sftp server: - Protocols = SFTP - Identity provider = Service managed - VPC = my private VPC - access = Internal - Domain = Amazon S3 the objective is to allow the other team from the same corporate to load files into my s3 bucket. when I finish creating the sftp server, it doesn't give me an endpoint ==> (Endpoint = '-' and Custom hostname = '_') I just want to know how the other team from the same corporate can interact with the sftp server to put files on my bucket as my sftp server is not publically accessible and I don't have an endpoint URL to give them. so how can they connect to my server to put files? can they use clients like FileZilla or putty or winSCP ... to transfer files? Thank you!
VPC peering between Atlas cluster and AWS
I have set up VPC Peering between my AWS VPC and Atlas cluster. My problem is that when I go to change my “IP access list” to remove the “0.0.0.0/0” IP, I am no longer able to connect to the cluster. I have included the VPC’s CIDR block in the allowed IPs and have also tried adding the Security group ID that is associated with the VPC. On the AWS side, I have a lambda that is being triggered and which then communicates with Mongo. The VPC that the lambda sits within, has no “internet gateway” so as I understand it, it should not be able to connect to the open internet. The VPC’s Route table diverts all traffic (from the lambda) to the peering connection (which connects Atlas to my VPC). From my setup, it seems that no traffic should be leaving my AWS VPC from any other IP address than the ones included in my VPC CIDR block. So why is it that removing the “0.0.0.0/0” IP from the list of allowed IP’s on mongo stops me from being able to connect?
aws site to site vpn private ip vpns over direct connect -- new feature
https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-site-to-site-vpn-private-ip-vpns/ 1) Going through the document, It tells to reserve a 10.0.0.0/24 cidr block on the transit gateway, what is the relevance of this block? where is it exactly used? It is not shown in the diagram in the document. 2) Do we need to carve out a separate cidr for The tunnel IPs, based on the number of tunnels. Is there any special consideration to be followed when assigning the tunnel outside IPs. 3) Any additional documents available on this topic would be helpful. What does that Cidr block do? are IPs from the block used anywhere ( tunnel headend or tailend IPs?). I understand the block is used for routing. How does one decide the Tunnel headend and tail end IPs? do the IPs subnets have anything to do with the CIDR block? If I have a 10G pipe, I am assuming I would be using 8 tunnels (1.25 cap), where do i know what the IPs would be? The IP Schema is dictated by what? Does the CIDR play a role here?
How to filter routers on a TG for Private IP VPN
I am implementing a new feature from AWS called Private IP VPN using Direct connect, My question is that how do i filter routes entering my P2P IPSec tunnel from the transit gateway towards onprem as i would like to receive all the routes that exist in the TG.
I have a microservice. What would be the most appropriate and economical infrastructure. The idea is to always keep the same public ip to associate it to the DNS. And that it does not change when we make new deployments. - Use Fargate with Balancer. - Use Api Gateway. - Use Beanstalk with Elastic Ip in an EC2 and without Balancer.