OCI Compute Instance how to to Access Private Subnet Resources Despite Correct Security List Rules
I'm working with an scenario with an OCI Compute instance that I launched in a private subnet. Despite having the security list configured to allow ingress traffic on the required ports (22 for SSH and 8080 for my application), I'm unable to reach an internal API running on another instance in the same VCN. The security list rules are as follows: - **Allow Ingress** for source 10.0.0.0/16 on port 22 - **Allow Ingress** for source 10.0.0.0/16 on port 8080 I've verified that both instances are in the same VCN and subnet, and all route tables seem to be configured correctly. I can SSH into the instance without any issues, but when trying to `curl http://10.0.0.2:8080` from the working instance, I get a `Connection refused` behavior. Here’s how I set up the instance: ```bash oci compute instance launch --compartment-id <compartment_id> --availability-domain <availability_domain> --shape VM.Standard2.1 --image-id <image_id> --subnet-id <subnet_id> --assign-public-ip false --display-name MyPrivateInstance ``` For troubleshooting, I also checked the following: 1. The application on the target instance is running and listening on port 8080 (verified with `netstat -tuln`). 2. The firewall on the target instance (iptables) is configured to allow connections on port 8080. 3. Both instances are part of the same security list. Finally, I’ve tried restarting both instances and checked the logs for any denied connections. The logs show no sign of the request hitting the application. What am I missing? Is there something specific to OCI networking that I need to address?