Skip to content
This repository was archived by the owner on Aug 28, 2024. It is now read-only.

Commit da2387f

Browse files
authored
Merge pull request #13 from ltvolks/ltvolks/add-service-accounts
Update Service Account descriptions
2 parents e815496 + 0ec564b commit da2387f

File tree

2 files changed

+41
-13
lines changed

2 files changed

+41
-13
lines changed

docs/access-and-permissions/index.rst

Lines changed: 40 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -45,18 +45,46 @@ applied at service levels, for example. Rackspace’s policy to avoid granting
4545
access unless necessary, and then grant it at the most granular level
4646
possible is necessary to ensure unintentional access is not granted.
4747

48-
In order to ensure that your aviator projects meet this permissions model,
49-
Rackspace may periodically audit the permissions being passed to the project
50-
and require adjustments to to utilize the least permissive model.
51-
52-
Rackspace will add a service account with the Project Owner role to each of
53-
your GCP projects that we
54-
manage: ``automation@rackspace-mgcp.iam.gserviceaccount.com``. Additionally, we
55-
will grant ``resource-observer@rackspace-mgcp.iam.gserviceaccount.com`` the
56-
Viewer role on all Aviator projects. Do not remove these accounts or alter
57-
their permissions in any way without first consulting with your
58-
:ref:`support team <support>`. We will also temporarily add accounts from the
59-
gcp.rackspace.com domain as Rackers and automation need access to your
48+
To ensure that your Aviator or Service Blocks projects meet this permissions model,
49+
Rackspace might periodically audit the permissions being passed to the project
50+
and require adjustments to use the least permissive model.
51+
52+
Service Accounts
53+
^^^^^^^^^^^^^^^^
54+
55+
Rackspace adds a service account with the Project Owner role to each of
56+
your GCP projects that we manage: ``automation@rackspace-mgcp.iam.gserviceaccount.com``.
57+
58+
Additionally, we grant these service accounts access with the following roles to enable support tooling for all Aviator and Service Blocks projects:
59+
60+
- ``resource-observer@rackspace-mgcp.iam.gserviceaccount.com``
61+
62+
The Resource Observer collects project metadata for support inventory
63+
64+
+ Viewer
65+
66+
- ``smart-tickets@rackspace-mgcp.iam.gserviceaccount.com``
67+
68+
Smart Tickets works with Watchman to provide automated diagnostics and additional context for monitoring alerts that are turned to tickets for Rackers to address
69+
70+
+ Viewer
71+
+ IAP-secured Tunnel User
72+
+ Compute Instance Admin
73+
+ Compute Security Admin
74+
75+
- ``mgcp-operations@rackspace-mgcp.iam.gserviceaccount.com``
76+
77+
MGCP Operations facilitates integration of Operations monitoring (formerly Stackdriver) with Watchman
78+
79+
+ Viewer
80+
+ Monitoring Admin
81+
82+
83+
Do not remove these accounts or alter their permissions in any way without first consulting with your
84+
:ref:`support team <support>`.
85+
86+
We also temporarily add accounts from the
87+
gcp.rackspace.com domain as Rackers and automations need access to your
6088
projects, so do not remove those accounts or alter their permissions.
6189

6290

docs/service-blocks/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ the service options to match your needs. These offers are described below.
1616

1717

1818
Platform Essentials
19-
^^^^^^^^^^^^^^^^
19+
^^^^^^^^^^^^^^^^^^^
2020

2121
Platform Essentials is a prerequisite for all other GCP service blocks.
2222
Platform Essentials includes:

0 commit comments

Comments
 (0)