Let's go back to the AWB management console.
And from here, we're going to go to all services in case this isn't opened, and we said that we want
to use the S3 service and we'll find that under storage.
You want to get started with us three, we need to create a bucket, you can view a bucket like a folder,
but with a bit more advanced settings that you can make the plastic.
Bienstock has already created a bucket required for the application.
But for the artifacts that we want to upload, we're going to create a new bucket.
And call it cars, API deployment's.
You will need to select a bucket team that doesn't exist anymore because the bucket will be created
for the entire region using a three star, for example, if you enter something generic as simply cars.
It always will come back with an arrow and tell you, hey, this bucket name already exists.
So for that reason you have that I created a API deployment will not be able to create anything else
with this name in this specific region.
So select something that hasn't been created yet.
You can leave the options as they are.
And when it comes to permissions, make sure that you block public access.
This would ensure that nobody with access to this URL will be able to see it content.
And finally, the last page, we issue an overview of what you have configured and you can click on
Create Barguti.
Everything looks good.
So as you can see, the bucket has been created and if you go inside it, you will see that it doesn't
contain any files or any folders.
As with any storage service, you can manually upload files.
They are called objects in S3 download files or anything similar.
But as our goal is automation, we are not going to use this interface to upload files, but they're
going to use catalepsy in order to upload our artifacts here.