Skip to content

Commit f4a0bea

Browse files
author
iru
authored
Update README.md
1 parent 2282c82 commit f4a0bea

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

README.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,13 @@ Your user **must** have following **roles** in your GCP credentials
3030

3131
### Use a Service Account
3232

33-
You can also deploy the module using a Service Account (SA). In order to create a SA for the organization, you need to go
33+
Instead of using a user, you can also deploy the module using a Service Account (SA). In order to create a SA for the organization, you need to go
3434
to one of your organization projects and create a SA.
3535
This SA must have been granted with _Organization Admin_ role. Additionally, you should allow your user to be able to use this SA.
3636

37-
38-
3937
| SA role | SA user permissions |
4038
|--------------|-----------|
41-
| ![Service Account Role](./resources/sa-role.jpeg) | ![Service Accouynt User](./resources/sa-user.jpeg) |
39+
| ![Service Account Role](https://raw.githubusercontent.com/sysdiglabs/terraform-google-secure-for-cloud/master/resources/sa-role.jpeg) | ![Service Accouynt User](https://raw.githubusercontent.com/sysdiglabs/terraform-google-secure-for-cloud/master/resources/sa-user.jpeg) |
4240

4341
### APIs
4442
Besides, the following GCP **APIs must be enabled** to deploy resources correctly for:

0 commit comments

Comments
 (0)