I have created an instance of the Memory store in my project but I am unable to telnet / connect to it, either from my local or the Google Cloud Shell. Searching online, I see that other people have been granted the same host IP as mine so I am a little confused (10.0.0.3). Some assistance on how to proceed here would be great. Do I have to expose something here?
I have completed the following:
Recreated my VM on the same region as the memory store
Created a new instance of the memory store (gave me a new IP) but I am still unable to telnet
You can connect to Cloud MemoryStore provided that you are in the same project, region and network. If any of these are different you will not be able to connect.
The IP address 10.0.0.3 is an RFC 1918 private address. This is why you must be in the same network to be able to connect. Also you need to enable firewall rules to allow traffic between your instance and Cloud Memorystore.
This link shows you how to connect to Cloud Memorystore from a GCE instance.
Connecting to a Redis Instance
Related
With AWS Elasticache, the connection host is returned as a CNAME (for example mycluster.1abc4d.0001.usw2.cache.amazonaws.com)
I am using GCP App Engine With GCP Memorystore.
It looks like Memorystore Redis returns an IP to an instance, rather than a CNAME.
Is this IP forever fixed? (What happens when clusters are added/removed?)
Is there any way to discover this IP for this host?
Should we have any concerns with using the IP directly? Or is there any settings that I can turn on to get a CNAME back from GCP that points to the Redis instance?
Just so you know Memorystore for Redis supports two connection modes, direct peering and private service access. Regardless of the connection mode, Memorystore for Redis always uses internal IP addresses to provision Redis instances.
Is this IP forever fixed? (What happens when clusters are added/removed?)
Yes, there are no specific events that would cause the IP address of a running Redis instance to change except the deletion of the Instance
Should we have any concerns with using the IP directly?
You should not have any concerns using IP directly, however to improve your security and facilitate your IP management it is strongly suggested that you use Private services access
Is there any settings that I can turn on to get a CNAME back from GCP that points to the Redis instance?
Yes, you can create a CNAME record using our service Cloud DNS to points to your Redis instance
I created an instance on GCP, but I am not able to access it.
This is similar to this one, but the proposed solution isn't working for me:
Unable to telnet to GCP MemoryStore
I have tried to telnet to it, I am in the same project and region, but apparently I need to be in the same network as it's a private ip, but what if you want to connect using the cloud shell? Also, how would an application running on my local machine access it?
I also included a firewall rule to make sure incoming connections are allowed.
To connect a client to a Cloud Memorystore for Redis instance, the client and the instance must be located in the same region, in same project and in the same VPC network. Please check the “Networking” document where you’ll have information on Basic network settings, limited and unsupported networks, network peering, IP address range.
You can connect to Redis from different GCP products like Compute Engine VM, Google Kubernetes Engine Cluster or Google Kubernetes Engine pod, but you can’t connect directly from the Cloud shell or from your local machine since they are not in your VPC network.
It may also have to do with a missing peering connection to your network. Check in your console at https://console.cloud.google.com/networking/peering/ to see if the peering is set up properly.
Using terraform you can use the following docs: https://www.terraform.io/docs/providers/google/r/redis_instance.html
After creating a new Google Memorystore of type Redis Standard, I'm allocated an internal IP address of 10.0.0.#. However, none of my compute instances in the project can access it (telnet fails).
Also unable to access it via the Cloud Shell.
From the documentation: "You can connect to the Redis instance from any Compute Engine VM instance located within the same project, region and network as the Redis instance." I don't see anything to suggest that cross-region is possible.
I have one CentOS instance in AWS and another instance in Hybris Cloud.
The AWS instance is running a Jenkins Server and I want to install a slave for it in the Hybris Cloud Instance.
I have followed the steps to establish SSH connection between two machine but still can't get them to connect.
What am I missing? Is there any special SSH configuration for establishing connection between different cloud providers?
I cant speak for Hybris, but AWS has a security group for your EC2 instance. The security group for your AWS instance must allow port 22 from the IP address of your Hybris server (or a range of IP addresses). In addition, the host firewall on the EC2 Jenkins server must allow for this as well.
Likewise, the Hybris server must have the same ports opened up.
If you continue having issues after checking security groups and host firewalls, check the Network ACL in AWS. If you are in your default VPC and there have been no alterations, the Network ACL should allow for your use case. However if you are in a non-default VPC, whoever created it may have adjusted the Network ACL.
I have two vnets that are connected using a gateway. VnET1 and VNET2. VNET2 has a VM which hosts a mongodb instance. I have a webjob running within an App service environment which is deployed into a subnet within VNET1. From this subnet i am able to access the VM in VNET2 with its DNS. But i am unable to access the VM's internal IP. Any suggestions are welcome.
An internal IP address is internal to a VNET, and VNETs are isolated from one another by design. See this site for a good overview.. https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-overview/. If you want to connect internally you might want to consider having multiple subnets within the same VNET instead.
At present, connecting two vnets using a gateway allows IP communication but doesn't allow DNS name resolution. In this scenario we recommend managing a local DNS server. This page shows the requirements for using your own DNS server in Azure.
Hth, Gareth