Answer
Oct 25, 2022 - 05:11 PM
There are multiple ways to troubleshoot this scenario.
1) VPC-peer-sharing - You may be connecting to a private database and not publicly available. You would need to route traffic between two VPCs. For more information https://docs.aws.amazon.com/vpc/lates...
2) NAT Gateway - If you have a NAT gateway you can route your traffic out of the VPC and then back into the second VPC. You would need to allow the elastic IP address ingress rules. Such as NACLS, security group.
3) You can also deploy Panintelligence into the same VPC to keep your database access private.
4) You may have your database that's private and not publicly available. This can be checked on the database configurations in AWS.
1) VPC-peer-sharing - You may be connecting to a private database and not publicly available. You would need to route traffic between two VPCs. For more information https://docs.aws.amazon.com/vpc/lates...
2) NAT Gateway - If you have a NAT gateway you can route your traffic out of the VPC and then back into the second VPC. You would need to allow the elastic IP address ingress rules. Such as NACLS, security group.
3) You can also deploy Panintelligence into the same VPC to keep your database access private.
4) You may have your database that's private and not publicly available. This can be checked on the database configurations in AWS.
Add New Comment