fix: Name of special header for AWS credential

amanda-tarafa · amanda-tarafa · commit 63e5edc82a1e · 2022-10-14T14:04:47.000+01:00
The JSON example is correct.
See b/151677419 for more context.
diff --git a/aip/auth/4117.md b/aip/auth/4117.md
@@ -290,7 +290,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
`@@ -290,7 +290,7 @@ The auth libraries and applications must follow the steps below:`
`290`	`290`	`"body": ""`
`291`	`291`	`}`
`292`	`292`	```
`293`		- 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.
	`293`	+ 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.
`294`	`294`
`295`	`295`	`### Determining the subject token in Microsoft Azure and URL-sourced credentials`
`296`	`296`