Learn how to get set up to use AWS Services. Learn how to access the console and view AWS service costs.
- [Instructor] Now as we start working with the analytic services available on Amazon, we're going to be working mostly with the console. And when you're working with the console, there's a couple of best practices that I'm going to show you and a couple of tips in general working with Amazon services. You can of course follow along with me if you have an Amazon account. If you don't, you can just watch and you'll still get a lot of value out of this course. So, if you are brand new to Amazon, you need to sign up for a new account, and you can then take advantage of some of the free tiers and the free services.
I will caution you though that some of the things that we're going to be working with in this course are not in the free tier. So you'll need to sign in to the console. Now if you are already working with Amazon, maybe at work or for a project, you might want to set up a separate dedicated account just for studying and learning. It's an absolute way to have a separate boundary from any sort of production system, and it is really recommended. And it's just simpler sometimes. When you're done you can actually delete the account. So you need to figure out how you want to handle the account for studying, however you set up your account, you want to sign into the console, and then I'm going to show you a little bit about the billing console so you can understand the service charges that you could be incurring.
And another tip which is service object tagging, just helps you to find services that you've turned on. So let's jump over to the console and just show you some of these basics as we're getting set up. So here I've logged in, the first thing that you want to do is make sure you're logged in with the appropriate user. So you can see your login here, and then you want to make sure you're in the correct area. So I'm going to be recording this, and I want to be working with the services that are in US East one, which is North Virginia. So when you log into the console, you want to make sure you're in the appropriate region for whatever works for you.
Do be aware that some of the services I'm showing you may not be available in all regions of the world. So if you are in your region, you don't see it, you may have to switch to another region. North Virginia is the first region and so Amazon makes most of the services available there first. The next thing that you're going to want to do is understand the service cost. Now if I click on my login name here, I can go to my billing dashboard. Now if you attempt to go here and you don't see this, it might be that you're working with an account that does not have the privileges to see the billing dashboard.
This could be a work account, so don't think its anything wrong with the Amazon services. This is actually set up to be viewable only when it is appropriate for the permissions and for the security requirements. So um, by default it is viewable by what's called the route, or the top level user. So you can see that this is a new account. I have no services that have been used here. In addition to just looking at this, you can also set up alerts at a basic level. I'll show you how to set up a budget.
So you just click the blue button here to create a budget, and you can set up a cost budget. And I can just call this monthly, and you can set it up monthly, quarterly, or annually. There are other types of notifications you can get more frequently then this, but this is just the simplest thing to do. So here we've got the start date here, and we can have an end date of the end of the year. And, I can have a budgeted amount monthly. And this is a learning account, so I don't want to spend more then $100.00 US. And then I can set up notifications.
Notify me when actual costs are greater than 95% of budgeted amount. And then I want to put in my email address here. And then I want to put budget alert. And I want to create this. And there we can see that my budget is pending.
And it will be activated here shortly, and then I would get an alert when the budget amount was exceeded. Now in addition to this, I can set up tagging. And probably the easiest way to see this if I open a new console window. So I'll do that. And I'll create a basic object. So I'll create an S3 bucket. And this is a container for files, which we'll be using. So I'm going to create a bucket, I'm going to call this one demo for lynnlangit January.
Bucket names have to be unique, and they have a home region, even though they replicate worldwide. So I'm going to say next, and next, and next, and create bucket. Now inside of my bucket, notice it has properties. And I have zero tags. So if I click on the tags, it takes me over to the advanced settings, and I can go ahead and I can add tags. Tags are just key value pairs, and it's very much a best practice in any Amazon services to use tags.
And you'll see why in just a second. Say purpose demo, do be aware that tag values are case sensitive. Say save. Okay so I have one tag on my bucket. So now, if I go to look for these tags, I can look at them in two ways. I can look at them from a billing perspective, but I can look at them also from what's called a resource group perspective. So let me show you that first. So I go to resource groups, and I go to tag editor. And I go to resource types, and I type S3 buckets, and I select the tag key, purpose.
And I say tagged with any value. And I say from US East. Then I click on find resources, and you can see I have an S3 bucket which I just created with this ID, that has been tagged with the value demo. So, if I wanted to filter if I had additional tags, I could say not tagged, empty value, or tag names. And this is a great quick way for you to find out what you turned on, which as you learn you can easily forget to turn services off.
Now in addition to just finding things, with this resource group tag editor, you can also associate them to cost management. So if I go over to the billing management console, and I go to cost allocation tags, notice that my tag is there, but it's not activated for cost allocation, and that means you could define a budget based on the tags associated with the services. And when you're building complex analytics pipelines, with many different types of services, this is really a best practice from the beginning to tag your resources even when you're learning.
So you can understand what resources are associated with the solutions that you're working with, you can delete them when you're done, and then when you want to recreate, you can recreate them and associate them to the various sections of your business and tag them so those business units can understand their spend in Amazon. So if I just click activate, and then I click on this tag, and I click activate. Now this tag is activated for cost allocation.
So this is a very elegant way to manage the spend around your services and all of Amazon. But I find this is particularly important in the analytics area, because you can get into some big spend when you're bringing in your data and working with it in the Amazon ecosystem.
- AWS analytics design concepts
- Files vs. databases
- Which analytics type to use
- Using code tools for analytics
- AWS IoT device message analytics
- Working with data using Spark commands
- Using AWS QuickSight for visualizations
- Top analytics architectural patterns and their associated AWS services