I am trying to get our application connected to a Stardog cluster using Stardog Graviton up in AWS. I have a VPC that contains two subnets, a public one for our internet-facing services and a private one for our backend. The application that needs a Stardog cluster is within the private subnet. Here's what I have done so far.
Created a VPC Peering connection from our VPC to the one that Graviton generates.
Updated the route tables to forward IP requests within the private subnet for the 10.0.0.0/16 CIDR block range (the CIDR block of the Stardog clusters VPC) and set the target destination to the peering connection ID.
Updated the security group that was generated to also allow ports 22 and 5821 from our VPC CIDR block range.
In addition, I also allowed all ICMP traffic from our VPC CIDR block so that I could ping specific instances. Our VPC is using the 172.16.x.x CIDR range so I know it's not an IP conflicting issue. The goal is to lock this down as much as possible and not utilize the internet-facing load balancer at all.
I am unable to ping any of the instances within the generated VPC and am unable to connect to the cluster from neither our application or Stardog studio - pointing to either of the load balancers or even instances directly. Any idea as to what the issue might be?
I am trying to get our application connected to a Stardog cluster using Stardog Graviton up in AWS. I have a VPC that contains two subnets, a public one for our internet-facing services and a private one for our backend. The application that needs a Stardog cluster is within the private subnet. Here's what I have done so far.
In addition, I also allowed all ICMP traffic from our VPC CIDR block so that I could ping specific instances. Our VPC is using the 172.16.x.x CIDR range so I know it's not an IP conflicting issue. The goal is to lock this down as much as possible and not utilize the internet-facing load balancer at all.
I am unable to ping any of the instances within the generated VPC and am unable to connect to the cluster from neither our application or Stardog studio - pointing to either of the load balancers or even instances directly. Any idea as to what the issue might be?