2.3 Create and Configure Storage Accounts

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

18 hours 43 minutes
Video Transcription
Welcome back In this episode, we're gonna take some of the concepts we've learned in the previous episodes and actually apply them out in the azure portal by creating and configuring storage accounts. My learning objectives for you include creating storage accounts and then viewing the properties of those storage accounts after creation, Let's jump over to the azure portal.
So here we are in our azure portal. And if you're watching these episodes in this course and chronology quarter, this is kind of the first time we've been in the azure portal eso. What I'm gonna be doing is as we go through and demo some of these different things we've been learning about,
I will create. Resource is in different ways just so you can kind of get a feel for the different ways
and different places inside the azure portal. You can't create things.
So here we are at the home page or azure portal. This is what should pop up after you first log in, and what we're going to do first is just right here in the middle under Azure Service's go to storage accounts and let's go create our first storage account.
Let's go ahead and click on add.
And here's some basic information we need to fill out for storage account. And really, you're going to see a commonality for any resource we create inside of Azure. First, we need to select our subscription. I only have one. My Microsoft Azure standard subscription. But you could have Maur subscriptions based on Prod Test or Dev
or even subscriptions based off of
business units. Maybe finance has their own or I t has their own for billing purposes.
Next thing we really haven't talked about his resource groups. Resource groups are just kind of a container for storing meta data. About all the different resource is that air in them?
Um, we don't have any currently, So let's go ahead and create a new one.
I'm just gonna name this one storage demo.
Next. Let's look at our instance details and start defining some properties of our storage account.
Now our storage account needs to be globally unique amongst all other azure accounts that are out there, so we can't just name it something like my storage account.
As you can see, it's gonna come back and say that name is already taken so if you are creating these and you don't have, like, a naming structure developed just quite yet inside of your organization just tossem random numbers at the end of this to make it unique.
Next, we need to choose our azure region. You can see here we have quite a few as some of the US ones. We're gonna come up at the very top East us West, U. S central us as well as one is available in other continents. Africa, Asia Pacific.
For now, we're just going to stick with East us.
We'll skip down here to account kind. You can see right now it defaults to the general Purpose V to which, as we talked about in our earlier episodes, that this is the most up to date current storage account type that you want to work with.
But what I want to do is click in here and check out some of the properties that change when we select another one. So let's go look at a general purpose version one.
You'll see we lose access down here to our hot and cool tears because those are simply not available for general purpose of V one
next. We also have our performance. We have a standard and premium like we mentioned earlier. So standard is gonna be backed by magnetic disk, which are a little bit slower, but a really good for storing large amounts of data and then our premium performance, which is backed by solid state disc and are used for V impartial hard disk drives.
For now, we're just gonna stick with standard
in our last option. Here is replication, which we also talked about. So let's look at some of our options in here
for the general purpose of Eve one. We have just l r s G r s or r A g e r s to keep the cost low for us. Just during this demo, I'm gonna select LRS
Now that we have the basics of our general purpose V one storage account. Let's click on next to goto our advanced options.
Now, our first option in here is security. Or are we gonna require a secure transfers now, this is gonna use https over http for making rest a p I calls or access in the storage account. So, in general, I think you'll want to keep this on.
The only time you would not be able to use https is if you're using a custom domain name for your storage account.
Next is virtual networks. This is selecting where you can access the storage account from. You can specify letting it be accessible from all your virtual networks or on Lee from selected virtual networks. For right now, we're just going to stick with all virtual networks.
Next is the data protection where you can do soft recoveries of blob. Snapshots will also just leave this disabled for right now. And, as you can see for the general purpose V one storage accounts, we are not able to do any options for a Data Lake storage. Let's go and click on next and go look at our tags
Now. Tags are used for governance on azure. Resource is, you can add key value Paris so you can identify them through billing or any other programmatic instances that you need to.
For example, we could simply have a key value here of department
and say this is for a storage account for the Finance Department.
Let's go ahead and click on next to go review our settings and create storage account,
you can see our validations have passed, and we could go and click on Create to create our storage account.
Now that we've got this first storage account, let's go ahead and go back and take a look at some other options when creating other types of storage accounts. You notice over here on the left we have our list of favorite Resource is and storage accounts is already pinned for us. So let's go ahead and select it,
and he's going click on add again to create another storage account.
Now we're gonna leave our account kind at general purpose. Be, too, which is going to give us options of access tears of either cool or hot. If you remember from our presentation earlier,
you cannot select an entire storage account to be at the archived. Here you We can set that later at in the the individual blobs or containers at the account storage level, you can only select hot or cool.
Let's go and switch our replication back to L. R s.
Now the rest of our options for creating storage account really aren't gonna change. So let's just go ahead and click on review and create
and let's create our general purpose V to storage account.
Now let's go ahead and go back to storage accounts
and let's go ahead and create our third type of storage account.
Let's go and select our third type of just a blob storage account.
After selecting blob storage, you'll see a little information. Papa come down here saying blob storage accounts on Lee Support blocking a pin blobs. We aren't gonna be able to support page blobs or foul shares, tables and Q's. This is Wives recommended that if you want to do blob storage, just go ahead and create a gin, too.
A storage account where you can have blob storage inside of it.
Let's go ahead and set the rest of our options and create this third storage account.
Now we have all our storage accounts created and you can see in the kind column. Here we have storage of eat, one stored to be, too, and our blob storage accounts
now real quick just to illustrate the differences between the blob storage and the storage V two. Let's bring up our storage fee to account.
After selecting storage account, you can see over here on the right. We have some the information displayed for when we created it, basically showing the performance tier access, tear our replication and the storage account kind.
And if we scroll down a little bit here, you can see the service is that we talked about previously blobs, files, tables and cues that are all available to be made inside of this gin to storage account.
If we go back and look at our blob storage,
you can see the only service we have available to create is blobs. Now let's go back to our storage accounts and go take a look at one more thing inside of our version. One storage account
for go down two settings and configuration,
as mentioned in an earlier episode version one. Storage accounts can be easily upgraded to version two storage accounts without any downtime or the need to copy that data over to a new storage account. You can see right here that that option is available just by clicking the upgrade button.
Now. I wanted to jump back to R V to storage account that we created and go look at its settings and configuration as well.
You can see, this is where we have the option to change some of the settings when we first created the storage account.
First, you can see we created this one using standard performance, but we don't have the option of switching that to premium. That is only something you can set when you first create the storage account.
However, we can switch over to http on our secure transfer option. And then we can also switch the entire storage account from a hot to a cool access tear
again, given you flexibility after you create it to change some of that, if you need to. If the data inside the storage account changes access requirements,
we can also change our replication option in case we decide that this storage needs to be a little bit more highly available, such as using the read only access Geo redundant storage or just geo redundant storage.
That about wraps it up for this lesson on creating storage accounts and look into some of the basic configuration. Let's jump back over to the slides to wrap this up
in the demo we just watched we created storage accounts, configured options based on the storage count type when we were creating them and then viewed some of the configuration options after creation, such as the ability to upgrade a V one storage account or change the access, tears, replication, options and security options after creation.
Coming up next, we're going to create and manage block containers and some of the security around those
See you in the next episode.
Up Next