- Welcome. In this demonstration,
we are gonna take a look at the code commit service
and create a code repository within that service.
Here we are in the AWS console home.
And if I search, I can just type the word code
and you'll see that there are a number of services
that come up automatically code commit, code pipeline,
we have this AWS signer,
we've got CodeDeploy.
The code build is in there somewhere too
but we want code commit.
So we'll start there.
When we create our repos, they are region scoped
but we can access those from any region.
It's just a matter of convenience
to have them in the same region,
that's one way of avoiding cross region traffic charges,
if you're performing a lot of pushes
or polls against that repo.
So I have no repos in here at the moment.
You can see that there's a number of different areas here
and it's recommends different services.
Artifacts, code artifact, build, code build,
deploy, CodeDeploy, pipelines.
And so we could actually look at these,
all within this same dashboard
as well as a number of settings around notifications.
So let's start here
with the bright orange button, create the repository.
You see that this is not a wizard.
There's no multiple pages of information required.
This is easy test repo
and we can give it a test description as well.
We can add a tag to it, cost center
and then we can go and click create.
And realistically that's all we need to create a repo.
Connecting to it is another set of tasks.
And AWS is going to give you some of those recommendations
right here under connection steps.
So it tells us right away
we are going to have a difficult time using HTTPS
because we're signed in using Federation.
We have temporary credentials.
The only way to use these is with the AWS CLI.
And we can use the credential helper on the CLI
as one way of connecting.
Otherwise we can create credentials
within an IAM user that would be able to connect to this.
Notice SSH is entirely grayed out
because that is not possible
when using the temporary credentials either.
If we wanted to create static credentials to use this repo,
we would then go to the IAM service,
we're gonna look at the IAM user
we've created called live lessons.
There are a number of different credential types
that can be applied to an IAM user.
We have the username and password for the console.
We have MFA and we have access keys for programmatic access
but take a look right here.
SSH keys for code commit, now,
it doesn't allow you to generate one,
it only allows you to upload one.
So you would have to upload
the public key of that key pair into the IAM dashboard,
if you wanted to use SSH.
You can also generate HTTPS credentials directly
for an IAM user.
And this gives you a one time opportunity to download those.
And you can see it creates a username.
There's a password.
We can download the CSV file
and then we can configure our local get client
to use those instead.
Let's go back to code commit.
Now there's also a mechanism
for using HTTPS with GRC, the get remote code commit
and that would be another way,
potentially of connecting to our repo.
And it's nice because AWS actually gives you
all of the steps required to make this happen.
And so if we go back to our repository
outside of all the instructions,
we can now look and see on the left hand side,
we've got poll requests, commits, branches, tags,
and settings, so that we can modify
these on a per repository basis.
And that completes this demonstration.