Series Overview for Deploying Oracle Analytics Cloud Resources using Oracle Cloud Shell and the OCI Terraform Provider

The Oracle Analytics platform comprises OAC (Oracle Analytics Cloud) and OAS (Oracle Analytics Server). It supports the efforts of every analytics user role. AI and ML are embedded throughout the platform to accelerate productivity and power better business decisions. Features include:

• Data visualization and storytelling
• Machine learning
• Mobile analytics
• Open data source connectivity
• Data preparation and enrichment
• Enterprise data modeling

This series provides best practices, architectural diagrams, and links to documentation for successfully deploying OAC (Oracle Analytics Cloud) resources using Oracle Cloud Shell and the OCI Terraform Provider. It provides an overview and a landing page for the other posts in the series.

Included in the series are the following posts:

• Deploy OCI Identity Components Before Provisioning Oracle Analytics Services
• Deploy OCI Network Components for Oracle Analytics Services
• Deploy Example Oracle Analytics Cloud Instances using the OCI Terraform Provider
• Deploy Example Oracle Analytics Cloud Private Access Channels using the OCI Terraform Provider
• Deploy Example Oracle Analytics Cloud Vanity URLs using the OCI Terraform Provider

Following the guidance in this series requires:

• An existing OCI tenancy.
• Privileges to manage all resources in a compartment.
• Privileges to inspect all resources in the tenancy.

The OCI cloud shell features a web browser-based Linux terminal accessible from the OCI console and:

• Is free to use
• Does not require prerequisites and setup (other than an OCI policy privilege).
• Provides client workstation operating system independence.
• Provides OCI CLI pre-authentication to all regions.
• Has dozens of pre-installed utilities and applications.

The OCI Terraform provider features:

• Infrastructure as Code (IaC) to manage, version, and persist infrastructure.
• A declarative language that describes an intended goal rather than the required steps.
• Support for multi-cloud resources.
• Reading or importing existing OCI resources.
• Management of resource dependencies.
• Deployment of resources in parallel by default.