how to Access OCI Load Balancer Health Checks from Private Subnet - 403 Forbidden scenarios
I'm working with an scenario with accessing my Oracle Cloud Infrastructure (OCI) Load Balancer health checks from a private subnet. I have set up a load balancer in a public subnet that fronts a set of application servers in a private subnet. When I attempt to access the health check endpoint, I receive a `403 Forbidden` behavior. I confirmed that the health check URL is correctly configured and uses the same endpoint as my application, which is `/health`. I have the following security list rules set for the public subnet where the load balancer resides: ```json { "ingressRules": [ { "source": "0.0.0.0/0", "protocol": "6", "sourcePortRange": "", "destinationPortRange": "80" } ] } ``` I also ensured that the load balancer has a proper listener set up for HTTP on port 80. Despite this, when I check the load balancer logs, I see entries indicating that my requests to `http://<load-balancer-ip>/health` are being rejected with a `403` status. I've checked the IAM policies associated with the load balancer and the private subnet, and they look fine. Additionally, I verified that the application servers are reachable within the private subnet and are responding correctly when accessed directly. The load balancer configuration seems to be accurate, but I'm wondering if there are any special considerations for internal health checks or possible misconfigurations in the subnet. Is there something I'm missing in terms of permissions or configurations that could lead to this `403 Forbidden` behavior? Any insights would be greatly appreciated! This is part of a larger application I'm building. I'm on Linux using the latest version of Json. Has anyone else encountered this?