Configuring Storage Account Services
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
1 hour 52 minutes
In this next lesson, we're gonna talk about how we can configure the different services available. Insider new storage account.
The objectives include reviewing those storage account services that are now available to us and then jumping out to the azure portal and take a look at a demo how we can create and configure some of them.
So are four main storage account services that we're gonna look at our container file Q and Table,
and our demo later is going to focus on the container and file services.
First, let's talk about container
containers are used for storing unstructured data like binary, large objects or blobs.
Our containers are what utilized the access tears that we set our storage account to, such as hot, cool and archive.
Now a storage account can be set to the archive tear, but individual blob objects inside the container can be set to the archived here, and we'll see the center demo later. Now, within our container. When we upload objects, we do have a couple of different types that we can configure for our blobs. First, we have blocked, which are just binary or text files.
Next, we have Page, which are optimized for random read write operations like virtual machine dis drives.
Finally, we have upend, which are optimized for upend operations like you might see in log files where you're just riding to the end of the file.
In this diagram on the right, I've tried to outline what this relationship looks like. First, we have individual pictures, container and a movies container, and this is where I like to think as containers as almost like the parent folder in a file system.
And within each container we have our individual blob objects over and pictures. We have image one, an image to and over in movies. We have movie one and movie, too.
Earlier, when we talked about configuring our storage accounts, I mentioned that the name of the storage account is appended with court dot windows dot net.
And actually, each service has its own unique euro that we can use to access the service. So for containers, it's gonna be the name of the storage account dot blob dot core dot windows dot net.
Next, we have the file service. This is a managed file share, just like you might have with other file shares through Windows or Lennox servers. They support the server message block or S and B protocol, which is a which is pretty standard across the industry.
What's really great is with these manage file shares, you can have concurrent mounts so you can mount the foul share to multiple systems.
And with azure file sync on Windows Server, we can cash the files for faster access on the server instead of always having to reach out into the storage account. We also have snapshot capabilities, and these are point in time. Read only copies of the data
they'll protect against application errors that might be accessing the data or any other data corruption or accidental deletions. That might happen again. We have a special you Earl for this. It's going to be the name of the storage account dot file that core dot windows dot net.
Next, we have the Q service and these air used as an application message queue. What that means is, if you have communication between different application components for the program you've written,
you can store messages inside these cues and have another part of the application. Go to the Q and retrieve them. An example for this might be incoming and outgoing orders in an order taking system. This Q is accessible over http requests, and in this diagram over here again,
stealing from my earlier diagram a little bit, we have two different cues. We have an incoming que in an outgoing que
and each of them we have different messages. These could be orders so you could have an incoming order that you need to process or an outgoing order that you need to process. And just like our other services, this has its own unique girl is going to be the name of the storage account doc. You dot core dot windows dot net.
Next, let's talk about the table service. This allows for storing large amounts of structure data
and provides a flexible data set for your applications
data. Anna is stored in a name value pair inside of each of the entities in your table,
and here's a little diagram starting to look familiar. I have two different tables here, a customer's table and a products table,
and the customers have two different entities in him, and we have name value pairs of named John and a customer I D of 123
and likewise for our products. We have a vendor and M S R P or a price for each product.
Just like our other services. It has its own unique Eurail that's based off the storage account. Name dot table dot core dot windows dot net
the desert for concepts Let's jump out to our demo, where we're going to create a container and a file share and see how those work
Harry are back in the azure portal and to get started. Let's go over to storage accounts and access our J V T 2020 storage account
Back in the overview page over storage account, you can see our four services that we talked about containers, fall shares, tables and queues. Let's get started by going into containers first
and inside containers. Let's click the plus sign and create our first container,
going to name this container training videos
and I'm gonna set the public access level to Blob. Now in a future episode will discuss thes access levels before. Right now, I just want to make sure I can read it anonymously through the browser.
Once this is set, let's go and click on OK,
and let's go ahead and create a second container called vacation pics,
and we'll set the same public access level to Blob
with our two containers. Now let's jump back into the training videos.
I'm going to select upload to put some data in here.
It was like the folder icon to choose a file
you see here actually have recordings of the first episodes of this course. Let's go ahead and select lesson 1.1
and let's go check out some of the advanced options.
First we have our authentication type will just leave it at account key,
and we can also set our blood type.
For right now, I'm gonna leave it at Block Blob, but we do have the option of going in here and selecting our page blob or pen blob.
We'll leave our block size
at four megabytes,
and this is where we consider access to your
right now the hot is selected by default because that's what our storage accounts configure to. But then we could also change it to cool, and this is where we have the archive access to your option
that does it for a settings. So let's go and select on upload
with our upload complete. Let's go back to our foul list here.
I'll select the three dot context menu over here
and let's choose properties.
And here in our properties, we have a euro right here of where we can access our file. I'm going to copy this to the clipboard.
Let's go ahead and open up a new tab
and paste this in here. I'm going to zoom in on this and you can see we have our storage account name dot blob that core dot windows dot net
the name of our container training videos and then the name of our file. So this makes up the euro. We could use to access this file if we need it to.
Let's go ahead and go to this euro and you can see the first lesson in this course pop up.
So this is successful. I'm able to access this file inside our container and our blob storage accounts.
Let's go back to containers.
It's going to our other container vacation pics.
I'm going to do the same thing. Let's go to upload.
I'm going to choose a couple of files to upload here
I have three National Park vacation pictures.
I'm gonna go ahead and leave all our advanced settings at their default on Let's select upload.
Let's clear out of these
and again. Let's go to the first picture here. Properties will grab the access your l
open up a new tab,
paste it in
and Walla were able to access the picture inside our container storage.
So hopefully this illustrates how we can use containers to divide up our blob objects and then upload files and access. Um three Euro.
Let's go back to the overview of our storage account
and this time was going to file shares.
We'll click the plus sign to create our first file share,
going to give it a name of just department data, and we could set a quota here for maximum storage. We wanted in it. Right now, I'm just gonna leave at the default. I believe it's five terabytes.
Let's click on create.
Next. Let's go into our new fall share.
First, I'm gonna upload some data, so when we connect it to our Windows server will be able to see the data in it
again. I'm going to just select a couple of these vacation pictures.
Let's clear out of these prompts.
Next, let's go click on the Connect button,
and here we have the instructions of how to connect this to our different servers. We have Windows, Linux and Mac OS.
Let's go back to Windows
and has instructions. Here we can select the drive letter, and it tells us to run this command down here in a regular power show window.
This little script here has the commands necessary to connect to the storage account. Let's go ahead and copy this to the clipboard,
and then I'm going to switch over to a Windows server. I have running an azure so we can test this connection and make sure we could connect to our foul share
Here in our Windows virtual machine
already have our power show window open, and I want to switch over to Windows Explorer and show that we don't have any network shares connected. Right now.
It's going switch back to power show
going to open up. No pad real quick.
I want to paste this command here and talk about what it does.
First, we're running a test net connection to make sure we can connect to our
file share girl over port for 45 which is the S and B Protocol.
And if that connection is successful, we're going to store an access key in order to connect to our foul share.
And by storing this using the CMD key command will be able to reconnect to this foul share after reboots.
Finally, we'll create a new PS drive
with the drive letter z out to our foul share.
Let's go ahead and grab this first command here
will drop back to power Shell. Let's run our test net connection.
It looks like it succeeded. So let's check out the Connect test result Variable.
We can see the TCP tests succeeded is true. So let's go back and grab the rest of this command
back to power show will paste it in, and we know it's going to be successful. So let's go ahead and run it and also want to get this out of the way so we can watch in the background and see our drive letter connect
so it creates the command key with are stored access key and then successfully creates the PS drive. If you notice in the background. We now have a new drive letter and Windows Explorer, and if we open it
there, we have it there. The three pictures I uploaded to our foul share so you can see how great this could be. We can create fall shares and connect him to our different systems for applications or maybe department data and use buyer users without spinning up an actual server to host it. Whether it's the Windows or Lennox one
that does it for a demo, let's jump back to the slides and wrap this up.
That is it for this lesson where we discussed our different storage account services that are available to us and took a look at how we can configure our containers and files
coming up. Next, we're going to take a look at a tool called Storage Explorer and see how we can use it to access our storage account.
See you in the next episode.