diff --git a/website/source/docs/auth/aws.html.md b/website/source/docs/auth/aws.html.md
index ff82c2b79a..0911d510c4 100644
--- a/website/source/docs/auth/aws.html.md
+++ b/website/source/docs/auth/aws.html.md
@@ -570,8 +570,8 @@ and EC2 instances in the target account.
 
 The account in which Vault is running (i.e. the master account) must be listed as
 a trusted entity in the IAM Role being assumed on the remote account. The Role itself
-should allow the permissions specified in the (Recommended Vault IAM
-Policy)(#recommended-vault-iam-policy) except it doesn't need any further
+should allow the permissions specified in the [Recommended Vault IAM
+Policy](#recommended-vault-iam-policy) except it doesn't need any further
 `sts:AssumeRole` permissions.
 
 Furthermore, in the master account, Vault must be granted the action `sts:AssumeRole`