AWS resilience-hub: Correct API path prefix from /v3 to /v2
Summary
Fixes the documented API path prefix for Next generation Resilience Hub APIs from /v3 to /v2; SigV4 signing requirement unchanged.
Security assessment
This is a factual correction of the API path prefix in an authentication page; the SigV4 signing requirement is unchanged and no vulnerability is fixed.
Evidence
+Next generation Resilience Hub APIs use the `/v2` path prefix. All requests must be signed with AWS Signature Version 4 (SigV4).
Diff
diff --git a/resilience-hub/latest/userguide/next-gen-api-authentication.md b/resilience-hub/latest/userguide/next-gen-api-authentication.md index 66037b4b3..b70c21c6f 100644 --- a//resilience-hub/latest/userguide/next-gen-api-authentication.md +++ b//resilience-hub/latest/userguide/next-gen-api-authentication.md @@ -16 +16 @@ -Next generation Resilience Hub APIs use the `/v3` path prefix. All requests must be signed with AWS Signature Version 4 (SigV4). +Next generation Resilience Hub APIs use the `/v2` path prefix. All requests must be signed with AWS Signature Version 4 (SigV4).