OCI Foundations Flashcards
What is OCI IAM?
Identity and Access Management Service
* Fine-grained Access Control
* Role Based Access Control
* AuthN - Who are you?
* AuthZ - What permissions do you have?
OCI Identity Concepts
- Identity Domains
- Users
- Groups
- Policies
- Federation
- Networks Sources
- Principals
- Dynamic Groups
- Compartments
- Resource
Identity Domains
An identity domain represents a user population in OCI and associated configurations and security settings
Identity Domain
- Users
- Groups
- Identity Domain
- Users
- Groups
- Policies - Role Based Access Control
- Compartments
- Resources - Cloud Object
How to Identify an OCI Resources?
Oracle Cloud ID (OCID)
ex:ocid1.<RESOURCE TYPE>.<REALM>.[REGION][.FUTURE USE].<UNIQUE ID>
- ocid1: The literal string indicating the version of the OCID.
- resource type: The type of resource (for example, instance, volume, vcn, subnet, user, group, and so on).
- realm: The realm the resource is in. A realm is a set of regions that share entities. Possible values are oc1 for the commercial realm, oc2 for the Government Cloud realm, or oc3 for the Federal Government Cloud realm. The regions in the commercial realm (OC1) belong to the domain oraclecloud.com. The regions in the Government Cloud (OC2) belong to the domain oraclegovcloud.com.
- region: The region the resource is in (for example, phx, iad, eu-frankfurt-1). With the introduction of the Frankfurt region, the format switched from a three-character code to a longer string. This part is present in the OCID only for regional resources or those specific to a single availability domain. If the region is not applicable to the resource, this part might be blank (see the example tenancy ID below).
- future use: Reserved for future use. Currently blank.
- unique ID: The unique portion of the ID. The format may vary depending on the type of resource or service.
Compartment
- Get a Root Compartment when create a account (can hold all the cloud resources)
- Collection of related resources
- Isolated and control access
Best practice: Create dedicated compartements to isolate resources
Compartment
- Each resource belongs to a single compartment
- Resources can be moved from one compartment to another
- Groups + Policies = Access to Compartments
- Resources can interact with other resources in different compartments
- Resources from multiple regions can be in the same compartment.
- Six levels of Nesting allowed (Nested Compartment)
- Set Quotas and Budgets on Compartments
Principals
IAM entities that are allowed to interact with OCI resources
AuthN
- User name/Password
- API Signing Key
- Authentication Tokens
- Oracle-generated token strings
- Authenticate third party APIs
AuthZ
What permissions do you have?
AuthZ in OCI - IAM Policies
Policies - human readable statements to define granular permissions
policy can be attach to a compartment or tenancy
policy statement basic syntax
Allow group <identity_domain_name>/<group_name> to <verb> <resource-type> in compartment <compartment_name>
Allow <group_name> to <verb> <resource-type> in <location> where <conditions>
Verb
* manage
* use
* read
* inspect
Aggregate resource-type
* all-resources
* database-family
* instance-family
* object-family
* virtual-network-family
* volume-family
Tencnacy Setup Best Practices
- Don’t use the tenancy administrator account for day-to-day operations
- Create dedicated compartments to isoldate resources
- Enforce the use of Multi-Factor Authentication (MFA)
Virtual Cloud Network (VCN)
- software define private network
- for secure communication use
- lives in a OCI region
- VCN is:
- Highly Available
- Scalable
- Secure
VCN Address Space
ip address CIDR
Public Subnet
Private Subnet
- Internet Gateway
- NAT Gateway
- Service Gateway
- Dynamic Routing Gateway - connection to On-Premises
Route Table
Local Peering
Remote Peering - DRG
Dynamic Routing Gateway v2
VCN Security
- Security Lists
Firewall rules
stateful and stateless
direction ingress and egress - Network Security Group (NSG)
Load Balancer
- Layer 7 HTTP/S
- Scalable - Flexible/Dynamic shapes
- Public/Private
- Highly Available
- Advanced features
- Routing intelligence
- Network Load Balancer
- Layer 4 TCP & UDP
- Public/Private
- Highly Available
- Scalable
- Faster than HTTP/S LB; lower latency
- Virtual Machines
- Shared
- Multi tenant
- Bare Metal Servers
- Dedicated Host