AWS rolesanywhere documentation change
Summary
Changed 'Signature verification' to 'Signature validation' in documentation link text
Security assessment
Minor terminology correction without security implications
Diff
diff --git a/rolesanywhere/latest/userguide/getting-started.md b/rolesanywhere/latest/userguide/getting-started.md index c9e0f900f..286fe199b 100644 --- a//rolesanywhere/latest/userguide/getting-started.md +++ b//rolesanywhere/latest/userguide/getting-started.md @@ -28 +28 @@ To specify which roles IAM Roles Anywhere assumes and what your workloads can do -The first step of using IAM Roles Anywhere is creating a trust anchor, which requires you to reference a certificate authority (CA) that IAM Roles Anywhere will use to validate your authentication requests. Both root and intermediate CAs can be used as trust anchors. You will have to use either a AWS Private CA resource in your account or upload your external CA certificate. Note that CA certificates that are used as trust anchors have to satisfy certain constraints. For more information, see [ Signature verification](https://docs.aws.amazon.com/rolesanywhere/latest/userguide/trust-model.html#signature-verification). +The first step of using IAM Roles Anywhere is creating a trust anchor, which requires you to reference a certificate authority (CA) that IAM Roles Anywhere will use to validate your authentication requests. Both root and intermediate CAs can be used as trust anchors. You will have to use either a AWS Private CA resource in your account or upload your external CA certificate. Note that CA certificates that are used as trust anchors have to satisfy certain constraints. For more information, see [ Signature validation](https://docs.aws.amazon.com/rolesanywhere/latest/userguide/trust-model.html#signature-verification).