Skip to content

Commit 0fa0b3d

Browse files
committed
Call out where a user can find their deployment service account ID
This is important as we do not have references to it anywhere and is information needed by the user to set up deployment observability.
1 parent c651441 commit 0fa0b3d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/nginxaas-google/monitoring/access-management.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ nd-product: NGOOGL
1010

1111

1212

13-
F5 NGINXaaS for Google Cloud (NGINXaaS) leverages Workload Identity Federation (WIF) to integrate with Google Cloud services. For example, when WIF is configured, NGINXaaS can export logs and metrics from your deployment to Cloud Monitoring in your chosen Google project. To learn more about WIF on Google Cloud, see [Google's Workload Identity Federation documentation](https://cloud.google.com/iam/docs/workload-identity-federation).
13+
F5 NGINXaaS for Google Cloud (NGINXaaS) leverages Workload Identity Federation (WIF) to integrate with Google Cloud services. For example, when WIF is configured, NGINXaaS can export logs and metrics from your deployment to Cloud Monitoring in your chosen Google project. To learn more about WIF on Google Cloud, see [Google's Workload Identity Federation documentation](https://cloud.google.com/iam/docs/workload-identity-federation).
1414

1515
## Prerequisites
1616

@@ -28,7 +28,7 @@ F5 NGINXaaS for Google Cloud (NGINXaaS) leverages Workload Identity Federation (
2828
- `Issuer URL` must be `https://accounts.google.com`.
2929
- `Allowed audiences` must contain the full canonical resource name of the workload identity pool provider, for example, `https://iam.googleapis.com/projects/<project-number>/locations/<location>/workloadIdentityPools/<pool-id>/providers/<provider-id>`. If `Allowed audiences` is empty, the full canonical resource name of the workload identity pool provider will be included by default.
3030
- Add the following **attribute mapping**: `google.subject=assertion.sub`.
31-
- Add the following **attribute condition**: `assertion.sub=='$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID'` where `$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID` is your NGINXaaS deployment's service account's unique ID.
31+
- Add the following **attribute condition**: `assertion.sub=='$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID'`, where `$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID` is the unique ID of your NGINXaaS deployment's service account. This ID can be found in the `F5 NGINXaaS Service Account Unique ID` field under the **Cloud Info** section in the **Details** tab of your deployment.
3232

3333
### Grant access to the WIF principal with your desired roles
3434

@@ -37,7 +37,7 @@ In the [Google Cloud Console](https://console.cloud.google.com/),
3737
1. Go to the **IAM** page.
3838
1. Select **Grant Access**.
3939
1. Enter your principal, for example, `principal://iam.googleapis.com/projects/$WIF_PROJECT_NUMBER/locations/global/workloadIdentityPools/$WIF_POOL_ID/subject/$NGINXAAS_SERVICE_ACCOUNT_UNIQUE_ID`.
40-
1. Assign roles. For example,
40+
1. Assign roles. For example,
4141
- To grant access to export logs, add the **Logs Writer** role.
4242
- To grant access to export metrics, add the **Monitoring Metric Writer** role.
4343

0 commit comments

Comments
 (0)