Skip to content

Commit 40761d4

Browse files
committed
Add IAM getting started instructions
1 parent 4cb1fe6 commit 40761d4

1 file changed

Lines changed: 19 additions & 1 deletion

File tree

iam/docs/getting-started.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,19 @@
1-
Something about IAM
1+
Our Identity and Access Management system gives you full control over who or what can access specific resources on the
2+
CBWS platform.
3+
4+
Most resources have an IAM policy that describes which principals (users, groups or service accounts)
5+
can access the particular resource and what can be done with it.
6+
7+
You can for example give developers read-only access to your production projects, give administrators owner rights
8+
and auditors access to view logs. This can even be controlled on individual resources like a specific virtual machine,
9+
service account, or something else.
10+
11+
To assign permissions we define a policy on a resource, this policy has one or more bindings. Each binding uses a
12+
predefined role (owner, virtual machine admin, something else), has a description you can define for future reference
13+
and a list of members (principals like users, groups and service accounts) to which this binding applies.
14+
15+
The CBWS platform provides a number of predefined roles per service as well as more generic roles like owner, editor
16+
and viewer.
17+
18+
The IAM service also provides service accounts which allow services, scripts, background jobs etc to access our APIs,
19+
the service accounts are full on principals that can be given access to specific resources via IAM policies.

0 commit comments

Comments
 (0)