oracle-cloud

Configure the oracle/oci provider with tenancy OCID, user OCID, fingerprint, and private key, then define resources like oci_core_vcn, oci_core_instance, and oci_database_autonomous_database. Use remote state in OCI Object Storage and organize code into modules for compute, networking, and database tiers.

Allocate a /16 CIDR for the VCN and /24 blocks per subnet, placing load balancers and bastion hosts in public subnets with an internet gateway route, and databases in private subnets routing through a NAT gateway. Combine security lists for subnet-level rules with network security groups for fine-grained instance control.

Security lists apply rules to all VNICs in a subnet, while network security groups apply rules to specific VNICs regardless of subnet. Use security lists for broad subnet-level policies and NSGs for targeted rules like allowing database port 3306 only from the application tier NSG.

Yes, setting is_auto_scaling_enabled to true lets Autonomous Database scale CPU up to three times the base OCPU count based on utilization. Storage auto scaling can be enabled separately with is_auto_scaling_for_storage_enabled.

Grant groups only the verbs they need, such as inspect, read, use, or manage, scoped to specific compartments rather than the tenancy. Use dynamic groups with matching rules for compute instances and add conditions like network sources or tags to further restrict access.

Authorization failures typically mean the compartment OCID is wrong or the user's group lacks a policy granting access to that resource type. Verify the compartment hierarchy, confirm the IAM policy statements, and test authentication with oci iam region list.