fix: Name of special header for AWS credential

amanda-tarafa · amanda-tarafa · commit a6245ce7daea · 2025-10-17T12:16:36.000-07:00
The JSON example is correct.
See b/151677419 for more context.
diff --git a/aip/auth/4117.md b/aip/auth/4117.md
@@ -293,7 +293,7 @@ The auth libraries and applications **must** follow the steps below:
     "body": ""
   }
   ```
-  For the AWS token, STS requires a special header `x-goog-cloud-endpoint` to recognize that the token is for a specific workload identity provider.
+  For the AWS token, STS requires a special header `x-goog-cloud-target-resource` to recognize that the token is for a specific workload identity provider.
 
 ### Determining the subject token in Microsoft Azure and URL-sourced credentials
 

Original file line number	Diff line number	Diff line change
`@@ -293,7 +293,7 @@ The auth libraries and applications must follow the steps below:`
`293`	`293`	`"body": ""`
`294`	`294`	`}`
`295`	`295`	```
`296`		- For the AWS token, STS requires a special header `x-goog-cloud-endpoint` to recognize that the token is for a specific workload identity provider.
	`296`	+ For the AWS token, STS requires a special header `x-goog-cloud-target-resource` to recognize that the token is for a specific workload identity provider.
`297`	`297`
`298`	`298`	`### Determining the subject token in Microsoft Azure and URL-sourced credentials`
`299`	`299`