Book Image

Oracle Cloud Infrastructure for Solutions Architects

By : Prasenjit Sarkar
Book Image

Oracle Cloud Infrastructure for Solutions Architects

By: Prasenjit Sarkar

Overview of this book

Oracle Cloud Infrastructure (OCI) is a set of complementary cloud services that enables you to build and run a wide range of applications and services in a highly available hosted environment. This book is a fast-paced practical guide that will help you develop the capabilities to leverage OCI services and effectively manage your cloud infrastructure. Oracle Cloud Infrastructure for Solutions Architects begins by helping you get to grips with the fundamentals of Oracle Cloud Infrastructure, and moves on to cover the building blocks of the layers of Infrastructure as a Service (IaaS), such as Identity and Access Management (IAM), compute, storage, network, and database. As you advance, you’ll delve into the development aspects of OCI, where you’ll learn to build cloud-native applications and perform operations on OCI resources as well as use the CLI, API, and SDK. Finally, you’ll explore the capabilities of building an Oracle hybrid cloud infrastructure. By the end of this book, you’ll have learned how to leverage the OCI and gained a solid understanding of the persona of an architect as well as a developer’s perspective.
Table of Contents (15 chapters)
1
Section 1: Core Concepts of Oracle Cloud Infrastructure
Free Chapter
2
Chapter 1: Introduction to Oracle Cloud Infrastructure
7
Section 2: Understanding the Additional Layers of Oracle Cloud Infrastructure

Connecting an OCVS cluster to the internet

Connecting an OCVS cluster to the internet is very straightforward and can be done using a simple workflow. If you selected the HCX option while deploying the cluster, then half of the work has already been done, as that workflow would have created a NAT Gateway, if one hadn't already been provided. Let's run the workflow to connect the cluster to the internet:

  1. From the SDDC Cluster details page, select Configure connectivity to the internet through NAT gateway, as shown in the following screenshot:
    Figure 11.16 – Internet connectivity workflow

    Figure 11.16 – Internet connectivity workflow

  2. Since a NAT gateway has already been provided, this workflow will use it.
  3. It will add a route rule to the Route Table entry for the NSD Edge Uplink 1 VLAN subnet. Basically, it will allow all the internal traffic to go out but via the NAT gateway.
  4. It will also add an allow any-any egress rule to the NSX Edge uplink VLAN's network security group, as shown in the...