[MUSIC] In this video, you will see a few demonstrations to use the Cloud shell along with some OCICLI commands from the Cloud Shell. I have logged into the browser console and I have chosen the Frankfurt region. Let me invoke the Cloud Shell here. And when we invoke the cloud shell remember, the clouds shell is instantiated in the region that you are currently in, as a result, we see over here in Frankfurt is where the Cloud Shell is invoked. If you switch the context to any other region this Cloud Shell environment is still in the region where you invoked in so that's where the cloud shell environment is currently running. When you have Cloud Shell, the CLA is by default configured and the details of the configuration are available within the EPC OCI directory. Inside this there is a configuration file, let me open the configuration file to list its contents, we see various settings available and some details are given here in terms of different profiles. The default profile points to the region, it is invoked in, but there are additional profiles created which point to a specific region. So if you want to execute a command from the Cloud Shell which is in Frankfurt, you can point it to the region by giving a profile option so that it will execute it and that. We will see that when we go into some commands. First of all, I'm going to show you to create a VCN in the same region, as where the Cloud Shell is running. I have my command here to create the VCN with a display name of so and so. And if I go to my VCN page such a VCN would have been just now created and it will get listed in a moment it is just getting created, let me hit the Enter. Cider block is given here the compartment is given here, so the compartment was picked up by going to the compartment page and getting the OCID. Right now it has given me a response that the VCN is created, we see that it has just now got created. The OCD of the VCN is given which you may use to create additional resources. So first of all, how did I get this compartment OCID, If I go to IAM and go to compartments and go to the compartment of interest in which I want to create the resources, you can get the OCID and use it. Now when you create a VCN with CLI, it creates just the VCN no subnets or any other components will be created using CLI additional commands you can go and create all of them. Now that a VCN is available, let me copy the OCD this VCN and use CLI to terminate the same VCN that I created and the action you will do for this is to Delete. So if I remove this command that is available here and replace the command here with the OCI VCN to network is the service, VCN is the resource, delete is the action and the OCID of the VCN is taken. This will result in the VCN getting deleted, it prompts whether you want to delete it, I type yes and Enter, it deletes the VCN, and in a moment, you will see that the VCN, CLI VCN disappears as it got deleted. Next, let's use the object storage service and create a bucket. I am in Frankfort region, there are no buckets here to create a bucket the command is very simple. There is a command for object storage in the form of OES objects storage, bucket is the resource create, give a name, what is the tier of storage in this case standard tier and in which compartment. This will result in the bucket getting created and this will result in a prompt response by OCI to give me the OCID of the bucket that got created. I will use this to terminate the bucket, or for the bucket you also have the option to use the bucket name to terminate it. So let's give it a moment to refresh or you can click elsewhere and go back to see that the bucket is created and we should see that listed here. If you want to terminate a bucket the simplest way you can do it is OCI object storage, bucket is the resource and the option you want to use is to delete it and give the name of the bucket. You have the ability to give the name and as a result of this it will prompt are you sure you want to delete the bucket? Okay, so I'm sorry I missed one additional hyphen here, should have had a double dash and delete this bucket. It should now prompt, do you want to delete the bucket and typing yes, we'll delete this bucket. And in a moment in your object storage listing over here, the bucket would get deleted as you see here. Now we saw earlier the option to use profiles, what i'm going to do now is create a block volume, but not in the default region, but in another region by giving the availability domain in London and choose the profile to be London one. When I create a block volume now, if I go to London and go to block volumes, I should see a block volume getting created with the option I gave, the option I gave is display name CLI block volume. It is currently provisioning it based on the size specification I gave in the availability domain I created, so how do you choose the availability name? Availability domain names, they are available here you'd have to use them and remember, the volume got created in London based on the profile option that I gave, and the AD name is also specific to that region. Now there is an ID for the block volume that is given which is nothing but the OCID of the block volume. If you go into the block volume page, any resource page also, you will get it's OCID, you see that it ends with the BQ, it is the same value here. Now if you want to delete the volume, again, you use the CLI to specify the OCID of the volume ID and I've added the profile option. This will result in the block volume getting terminated with a prompt from OCI asking me do you want to terminate, type, yes, and in a moment, my block volume would also be terminated, so you see that it is terminated. So, the Cloud Shell is running in a particular region, remember that, and profiles can be used to not only customize region, it could be with variables about compartments or user various options available, you can explore them in the documentation. But let's say I close this Cloud Shell environment, and now launch Cloud Shell again, notice that when i'm launching Cloud Shell, it is in London. This time around the Cloud Shell environment will be provisioned in London and as per the profile for this, the default region for it will be London keep that in mind. That's a quick overview about using Cloud Shell as well as CLI from within the Cloud Shell. You can explore more details from the documentation which I had given earlier. So if we look into the documentation, there are various commands available for the various services in CLA. Clicking on each one of them you can explore how do you give those options and create and manage resources in OCI.
