- Welcome to this demonstration.
In this demo
we are going to create an S3 bucket using the AWS console.
So we can either go to recently visited if S3 shows
up in there, or we can search for it using the search bar.
Now, once we're in the console, again, bright orange buttons
that's gonna help us create the bucket
but we can also use this little nav right here to expand
and give us other options,
in this case we're gonna go ahead and just create the bucket
and this wizard can either be really simple
or maybe add a little bit of complexity.
Let's start with our bucket name.
So what are we gonna call our bucket?
We will call it bright key live lessons bucket.
Now this bucket name does have to be globally unique
and it also has to conform to DNS standards.
If we go a little bit further.
We get to pick a region
and we have all these different options here.
I will stick with US east one.
Now here's an interesting option.
We can choose to copy the settings
from an existing bucket to the new one.
As we go down a little bit further
we have an option that says
do you want to disable ACLs on your bucket entirely?
There are certain features of AWS
like cloud front access logs, S3 access logs,
pre-signed URLs, and so forth that require ACLs.
But for most use cases
you can simply disable them entirely.
And it simplifies permissions management because
it's no longer possible to utilize ACLs on the bucket.
So we go down a little bit further.
Now we have the block public access settings.
The default is for everything to be turned on
meaning you cannot use bucket policies or ACLs
to grant public access to either the bucket or an object.
And so if we uncheck this
we have the ability to check individual boxes.
This is something that we can change later if
we choose to do so.
So we keep going further.
This is where we enable versioning.
We will leave that disabled and we can apply tags.
So for this tag, we will add a cost center.
We can deal with default encryption.
This is a pretty easy win to enable encryption
of data at rest.
So when we click on enable, we have options
we can use Amazon managed keys where Amazon owns
the entire chain of trust, or we can use our own.
But if we do, we have to be more specific.
Do we use the KMS key that is default for all of S3
in our account in the region, or do we choose from our own
from a list or do we just enter an ARN?
So I'm going to stick with Amazon managed
for this one and under advanced settings,
the only thing we have here at this time is object lock.
And it explains to you that if you enable it
it permanently allows objects in this bucket to be locked.
So this is going to be another one of those configurations
kind of like the glacier vault lock that can be
used to disable the ability to delete data.
And so we'll leave that disabled as well
and create the bucket.
Now let's see bucket with the save name already exists.
So apparently I've created one
of these in one of my other accounts.
So we can call this bright key live lessons
S3 demo instead,
scroll down to the bottom and create bucket.
Now, remember the bucket,
there's no data here.
It's just configuration and access control.
If we want to add data
we have to actually upload it into the bucket directly.
And that completes this demonstration.