CodexBloom - Programming Q&A Platform

OCI Resource Manager: how to to Access Private Subnet with Remote Backend Configuration scenarios

👀 Views: 1 💬 Answers: 1 📅 Created: 2025-06-11
oci terraform resource-manager HCL

I keep running into I'm sure I'm missing something obvious here, but I'm having trouble with OCI Resource Manager when trying to configure a remote backend for Terraform..... I've set up a private subnet for my resources, but I keep getting the behavior message `behavior: Unable to access the remote backend: behavior making API request: Post "https://<my-backend-endpoint>": dial tcp <ip>:443: i/o timeout`. I’ve verified that my VCN and security lists allow outbound traffic, and I’ve also created a NAT gateway to facilitate internet access for my private subnet. Here’s a snippet of my `main.tf` file: ```hcl terraform { backend "oci" { region = "us-ashburn-1" tenancy_ocid = var.tenancy_ocid user_ocid = var.user_ocid key_file = var.key_file fingerprint = var.fingerprint compartment_ocid = var.compartment_ocid private_subnet_id = var.private_subnet_id remote_backend_url = "https://<my-backend-endpoint>" } } ``` I’ve confirmed that the endpoint is correct and reachable from my local environment, but it seems like the configuration doesn’t allow the Resource Manager to access it. I’ve also tried using the `oci iam` command to check the networking settings, which seem fine. Additionally, I’ve ensured that my IAM policies allow the necessary access. Is there something I’m missing regarding the private subnet configuration or potential issues with Resource Manager accessing remote backends? Any insights would be greatly appreciated! This issue appeared after updating to Hcl 3.9. Hoping someone can shed some light on this.