Skip to content

Latest commit

 

History

History
139 lines (93 loc) · 7.61 KB

README.md

File metadata and controls

139 lines (93 loc) · 7.61 KB
Raw

Compute instance in Oracle Cloud Infrastructure (OCI)

Executing the Terraform you will get an OCI Compute Instance that could be used as a remote working station.

Features, installed, configured tools

  • ssh to be able to connect to the instance
  • Git (with the given ssh key, and user settings)
  • nvm
  • etc.

Look into the cloud_init and user_init scripts for further information, modification of the preinstalled tools.

Prerequisites

  • Oracle Cloud Infrastructure account
  • Oracle Cloud Infrastructure CLI
  • Terraform CLI (check supported version)

Before you begin

IMPORTANT

  • Be on the right OCI account!
  • DO NOT create instances on a WRONG account!
  • Check what is the supported Terraform version by OCI to prevent nasty problems like (s3 bucket access problem, etc.)

Use the correct Terraform version

Check the OCI-Supported Terraform Versions documentation what is the latest currently supported Terraform version. Check the .terraform-version and update if required. Use tfenv install where the .terraform-version is to install the correct TF version.

Set up OCI CLI

You have 2 options to configure the OCI CLI. Either way, you need to create RSA keys. But this could be done during the OCI CLI setup or before.

Create a user

Create a user in the OCI console in the compartment where you want to create the resources (Do NOT use the root compartment and the root user for security reasons!)

Create RSA keys for the user

See OCI Set Up OCI-Terraform

You create RSA keys to let Terraform signing in to your Oracle Cloud Infrastructure account.

  • Generate a PEM file locally
  • Upload the PEM file to the OCI console as an API signing key for the previously created user.
  • Use this key during the OCI CLI configuration

Create OCI Configuration

  • PREFERRED - Configure the OCI CLI with a configuration file (using an optional profile) For this see Setting up the OCI CLI Configuration File This is the preferred way because the OCI CLI would be helpful for example turn ON/OFF the Compute instance, etc. And the Terraform could use this too.

    Execute the oci setup config command to start the configuration

  • Configure the OCI CLI with the Terraform Provider configuration For this see OCI Getting Started with Terraform Provider

Create a compartment on the OCI console

See OCI Compartment Structure for more info about compartments.

Note the OCID of the compartment, we will use this later.

Create an ssh key pair to be used for connecting to the Compute instance

See OCI Create SSH Key Pair

You can create a ssh key pair in the OCI console or locally and upload the public key to the OCI console.

Create an SSH key pair to let the instance access Github

The instance will use this ssh key to access the github with it.

If you don't already have an ssh key to use with this instance create a new one

mkdir ~/.ssh/<USER_NAME>
ssh-keygen -t ed25519 -f ~/.ssh/<USER_NAME>/<USER_NAME>_oci_ci_github_key -C "<YOUR_EMAIL>@gmail.com"

Create/Update the terraform.tfvars file

  • Update the compartment_id with the OCID of the compartment where you want to create the resources
  • Update the region with the region where you want to create the resources
  • Update the ssh_public_key_path with the path of the ssh public key file for accessing the Compute Instance
  • Update the ssh_github_privatekey_path with the path of the private SSH Key, git_user_name and gith_user_email for accessing Github

Terraform State

  • Terraform state is stored in a bucket in the OCI console
  • The bucket name is configured in the terraform.tfvars file
  • The bucket is created automatically when you run terraform init just uncomment the relevant part from the backend.init.tf file. This file won't bee needed later so feel free to comment its content out again after the bucket is successfully created and you have the backend configuration.
  • PUT the backend output in the backend.tf file that is gitignored because of the generated content

OCI Resource Schedule

It could be wise to create an automation to stop your Compute Instances daily. It could be created with Terraform, but than you need a user with special rights or a root user, because the Schedules could only live in the root compartments (that is the tenancy). So probably this time we should pick the easier way and create the Schedules manually on the OCI Console.

Steps

  • Create a ResourceSchedule on the OCI Console
    • !!! Note that the time of the Schedule is in UTC
  • Create a Policy for the schedule to enable it to manipulate compute instances. Something like this.
Allow any-user to manage instance in compartment id <compartmentid of the compute instances e.q.: ocid1.compartment.oc1.....> where all{request.principal.type='resourceschedule'}

Look the Links below for further information and possible solutions.

Links