Doing.
And welcome back now into this video we'll be discussing about the escort service in detail now just
to devise a dress code, comet is a manmade source control service provided by Eatables for hosting
the repository.
Now, generally, a lot of organizations, they make use of third party platforms like BitBucket, GitHub,
and there are a lot of them that are available for hosting.
They're get repositories.
So either good committee is also one of the great options that can be explored upon now will quickly
look into the code, commit console.
You see that there are multiple repositories that are available.
So very quickly open up one among them within the repository there are multiple files and along with
that code also offers all the basic set of features that are available in a typical gate based platform.
So you have pulled request, you have comments, branches and various others.
Now, at this stage of a professional or a specialty level certification, I assume that you already
know the basics of established code commit and also the basics of getting a repository so that we can
go ahead and discuss about various important features of code it in more detail.
Now, I still remember many years back when the escort service was launched, in fact, we were evaluating
it for our organization.
But during that time, the code comit had a very basic set of features, and that was one of the reasons
why a lot of organizations did not really opt for it.
But now, after a few years, it has a good amount of features.
And one of the great benefits for which organizations are opting for this or other third party providers
is its tight integration with various other services.
So let's go ahead and discuss about it in more detail.
Now, the first important feature of code that we should note is the repository text.
So the repositories are within the database code.
Commit can be tagged, which will further help to identify and organize your resources.
So if you see I have a code repository of demo code commit and it has its tag off team of payments.
So whenever you make use of various services like Resource Group and you want to see what are the resources
associated with team of payments, maybe code comment repository, easy to instant's as three buckets
and so on.
This is something that you can easily do with the help of the repository tags if they are added to the
code repository.
Now one of the things where repository tags are extensively used in the organization, from what I have
seen, is the identity based policies.
Now, with the AIM policy, you can go ahead and create a lower Denyer action on the repository based
on the Edelstein's that are associated with it.
So let's take a simple use case.
Let's assume that there are 20 developers that are part of the team payments.
So what we want is those 20 developers should have access only to their sect of repositories.
So in order to do that, the first thing that you will need to do is you'll have to Baghdad repository.
So you'll tag all the payments repository with the appropriate tag and then you create in policy.
So the policy action is going to start on all the resources with the condition of time of payment.
So any court comment repository which has this specific tag, the payment team will have full control
over it.
So that is what the identity policy allows you to do.
Now, let me quickly show you this as well.
So currently within the code community repository, if I quickly go to settings Aurier under the repository
tags, you see that you have a tag of team payments.
So now what you do, you go ahead and associate this specific AM policy to all the developers that are
part of being payments and hence they'll be able to have full access on the repository which has its
associated tag.
So let's quickly try it out in a demo perspective.
So for today's demo, I have an user named Demo User and this user has a good command based policy associated
with it.
So let's go ahead and explore what this policy is all about.
So if you'll see, it is basically allowing the code commit extraction action on all of the resources,
considering that the resource has a tag of team of payments.
So now from the demo user, let's quickly go to the code, commit console.
Now, at this stage, the user is able to list all of the repositories now we know that the team of
payments that is associated with the demo could.
So if I quickly open this up and we try to read the file, let's do that.
You see, it is working perfectly well now in a similar way.
Let's go back to the repository.
You also have one more repository called a secret repository.
Now, this repository does not have a tag of team of payments.
So let's go ahead and try opening this up.
And immediately you get access denied exception.
So the identity based policies based on the resource stack is a very important feature.
And this is something that you will be using extensively provided your organization is using.
It could come in.
Now, when you discuss about the identity policies, one of the things that we just saw was the access
based on resource tax.
However, there are a lot of things that you can do based on that.
So let's take some sample use case so you can say denying all access to a repository with a tag of status,
a secret.
So this is something that can be done.
You can say allow access to a repository only in the Mumbai region, or you can allow user only connecting
from a specific IP to connect to a repository.
This is also something that can be done or you can deny Bush access to the master branch or various
other.
So if you see there is a lot of flexibility that you can get with the help of and policies for eatables
could come in.
And this is very important.
So if you are very familiar with the IAM policies, you can try a great set of policies for the committee
and this is what will make even the auditors happy.
So now let's look into the next set of features of code coming primarily related to the integration
with A.W. services.
And this is very important.
So Aydan escort service integrated various other services like LAMDA.
You have even breached your cloud trail code, build a database, Caymans and various others.
And this is one of the reasons why a lot of organizations are primarily opting for code coming.
So, for example, you have a code commit service, you have certain set of actions.
Maybe if someone has pushed the latest set of code, it can go ahead and trigger a lambda functions.
You can do a lot of things when it comes to integration with code committee.
So database code is integrated with cloud.
So in the previous slide, also we were discussing about the integration of the code commit service
that even breach cloud Trillian others so that since it is integrated with Cloud three, it will allow
administrators to capture great insights into activities by users.
So you can go ahead and create great dashboards on what are the repositories that are being pulled,
how many pushes that are happening, what are the files that are being deleted in the code repository
and so on.
And this is very important specifically for the security team.
I remember in the organizations where I was working with so we were building the same related dashboard
security, monitoring the related dashboard set, and one of the rules specifically related to the gate
repository and auditors were very strict about it, is that if a user, lets say a user is leaving the
organization and just a day before his last day, he suddenly he pulls all of the repositories that
are part of that specific organization belonging to his team as well as belonging to all other teams.
So that is one of the things based on which alert is raised.
So now one of the question that comes is why is he pulling all of the repositories associated with the
organization in his last day of working?
So something like that.
There are a lot of important security use cases that can be built based on gett.
And with the help of the code commits integration with cloud, it becomes very easy to go ahead and
do this.
So it will quickly look into the cloud console.
We have basically filtered the event source based on the core service.
So you see there are multiple events, name like list repositories and get references, get the repository
and so many others.
And based on that, it is also giving you the associated user name.
So this username has performed this operation on this specific event.
So if I go a bit down, you have certain activities by then, more user, you have certain activities
by other users and so on.
So if you'll quickly open this up.
So at this stage, if you will see that a great repository event was made, but you do not really know
which repository was created on.
So if you'll open this specific event, let's go back down.
So within the area you can see it is the demo code repository.
It also shows you various other details here, like the source IP address from which the query was made
and various others.
So all of this information is like a gold mine specifically if you want to build the security.
Related dashboards for gate repositories now the next important feature for Qualcomm, it is it's notification
rules so you can set up notification rules for repositories so that the repository users receive emails
about the repository event types that you specify.
So, for example, let's say that you want to go ahead and get the email whenever a certain event occurs.
So maybe whenever there is a bold request or whenever there is a merge or whenever a brand is created
or deleted or administrator of that team needs to get the email.
So this is something that can be done with the help of notification rules.
So within the code, if file quickly open up the settings area under the notifications, you'll see
that in terms of event that triggers the notification, you can specify.
So whenever you want an email, when there is a pull request or when a brand is created or deleted or
merged, depending upon what you need, you can go ahead and trigger the notification accordingly.
And again, one great thing is that the notification need not be always email.
You can also integrated, which lacks a lot of organizations are using slack.
Now, the last important feature for today's video associated code coming is the data protection.
So data encoded repositories is encrypted in transit as well as rest.
This is very important to know.
So whenever the data is pushed into a repository, so for example, let's say you do get push, then
the code commit encryption to receive data as it is stored in the repository.
So whenever you pull the data from code contrapositive, it could pull goldkamp, commit, automatically
decrypt the data and then sends the decrypted version to the caller.
And also note that whatever data that is transmitted over the network, it is always encrypted.
And this is the reason why whenever you create a good command repository, if you go to the key management
service in the W.S. under the AWG managed keys, you will see that you'll always have a key associated
with the eatables code curcumin.
And this is important, primarily related to the use case of storing the encrypted data as well as decrypting
it whenever required.
So at a high level overview, these are some of the important features related to the established code
coming.
Again, there are a lot of other features that can be explored upon.
We look into it as and when required in more detail.
However, for this we will keep it simple and a high level overview and with this will conclude today's
video.