Identity and access Management - OCI

 OCI -IAM 

OCI IAM deals with more secured and interesting features or entities when compared to other cloud competitors. I would like to share some brief information about OCI IAM.

  •  IAM enables you to control what type of access a group of users have and to which specific resources resource is a cloud object that you create and use it in OCI 
  • Each OCI has unique Oracle-assigned Identifier called as OCID
  • IAM uses traditional identity concepts such as principals, users, Groups, AuthN, AuthZ and introduces new capability called Compartment
  • Principal -> it is an IAM entity that is allowed to interact with OCI resources , infact it is a kind of permission
  • users -> it is a persistent identity setup through IAM service to represent individual people 
  • Group -> it is a collection of users 
  • Instance principals -> It will allow OCI instances to make API calls against other OCI services removing the need to configure user credentials or a configuration file.
  • Authentication-> username/password , API signing key,Auth tokens 
  • Authorization-> Authorization specifies varius actions an authenticated principal can perform
  • Policies -> are comprised of group of statements which specify what groups can access what resources and at what level of access 
  • Policies are written in human-readable format 
Allow group <grp-name> to <verb> <resource-type> in tenancy
Allow group <grp-name> to <verb> <resource-type> in compartment <compartment_name> [where <condition>]

verb -> [inspect/read/use/manage]
resource type -> [all-resources/database-family/instance-family/object-family/virtual-network-family/volume-family/cluster-family/file-family/dns]

Allow group <grp-name> to <verb> <resource-type> in tenancy

Resource Locations:
=================== 
Global(IAM/Key vaults,keys/DNS)
Availability Domains(subnet/compute instances/block volumes/DB systems/File Systems(& mount targets)/Ephimeral public ips)
Regional : everything else 

Moving a compartment :
you can move a compartment to different parent compartment with in same tenancy , but make sure the name of the compartment should be unique 

tag Namespace:
============== 
A tag namespace is a container for set of tag keys with tag key definitions.
tag key definitions specifies its key and what types of values are allowed (string,number,text,date,enumerations,etc) 
Tag key definition cannot be deleted but rather retired and if required we can reactivate 











Comments

Popular posts from this blog

How to make CRS and ASM not to restart after server reboot

Understanding Terraform

How to repair ASM disk header