You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{site.data.keyword.tg_full}} uses the IBM Cloud Identity and Access Management (IAM) platform access roles to manage access to the service's resources. IAM access roles allow account administrators to assign different levels of permission for using the service. The following tables provide the list of actions that you can take against the {{site.data.keyword.tg_full_notm}} service and its resources depending on a user's assigned roles.
28
28
29
29
## Platform-access roles
30
-
{: #platform-access-roles}
30
+
{: #platform-roles-iam}
31
31
32
-
{{site.data.keyword.tg_full_notm}} supports Viewer, Operator, Editor, and Administrator platform-access roles.
32
+
{{site.data.keyword.tg_full_notm}} supports Administrator, Editor, Operator, and Viewer platform-access roles.
33
33
34
34
| Role | Description of Actions | Actions |
35
35
|---|---|---|
36
-
| Viewer and Operator | Can only perform actions that don't change the state of resources. |<ul><li>List gateways</li><li>Get gateways</li><li>List a gateway's connections</li><li>View a gateway's connections</li><li>View incoming connection requests ✽ </li></ul>
37
-
| Editor | Can perform all actions, including managing gateways and connections, but cannot assign {{site.data.keyword.tg_full_notm}} IAM access policies to other users. |<ul><li>Create gateways</li><li>Delete gateways</li><li>Edit gateways</li><li>Add or remove gateway connections ✽ </li><li>Accept or reject a cross account connection request ✽ </li><li>Edit gateway connections
38
36
| Administrator | Can perform all actions, including managing gateways and connections, and assign {{site.data.keyword.tg_full_notm}} IAM access policies to other users. | <ul><li>Create gateways</li><li>Delete gateways</li><li>Edit gateways</li><li>Add or remove gateway connections ✽ </li><li>Accept or reject a cross account connection request ✽ </li><li>Edit gateway connections</li><li>Update user access policies for the service ||
37
+
| Editor | Can perform all actions, including managing gateways and connections, but cannot assign {{site.data.keyword.tg_full_notm}} IAM access policies to other users. |<ul><li>Create gateways</li><li>Delete gateways</li><li>Edit gateways</li><li>Add or remove gateway connections ✽ </li><li>Accept or reject a cross account connection request ✽ </li><li>Edit gateway connections |
38
+
| Operator and Viewer | Can only perform actions that don't change the state of resources. |<ul><li>List gateways</li><li>Get gateways</li><li>List a gateway's connections</li><li>View a gateway's connections</li><li>View incoming connection requests ✽ </li></ul>|
39
39
{: caption="Table 1. IAM platform-access user roles and actions" caption-side="top"}
40
40
41
-
✽ To add or remove connections to VPCs, or to accept or reject a cross account connection request, the user must also have Editor or Administrator platform-access role permissions to the VPC being connected to. See [VPC: Getting started with IAM](/docs/vpc?topic=vpc-iam-getting-started) for more information.
41
+
✽ To add or remove connections to VPCs, or to accept or reject a cross account connection request, the user must also have Administrator or Editor platform-access role permissions to the VPC being connected to. See [VPC: Getting started with IAM](/docs/vpc?topic=vpc-iam-getting-started) for more information.
42
42
43
43
## Service name
44
-
{: #service-name}
44
+
{: #transit-service-name}
45
45
46
-
The service name you designate will vary depending on how you access IBM Cloud Transit Gateway. If you are using the IBM Cloud CLI, APIs, or Terraform, then you should use `transit` for your service name. If you are using the UI, `Transit Gateway` should be the service name.
46
+
The service name that you designate will vary depending on how you access IBM Cloud Transit Gateway. If you are using the IBM Cloud CLI, APIs, or Terraform, then you should use `transit` for your service name. If you are using the UI, `Transit Gateway` should be the service name.
0 commit comments