From 4e2f55d7c0f8f9c1064bf7a3c254a87e1ec61820 Mon Sep 17 00:00:00 2001
From: Victor Santos <victor@infisical.com>
Date: Tue, 9 Dec 2025 14:48:05 -0300
Subject: [PATCH] fix(pam): correct wildcard notation in AWS IAM resource
 documentation

- Updated the documentation to replace the wildcard notation from "/*" to "*" for clarity in the policy description, enhancing user understanding of role assumption permissions.
---
 .../components/PamResourceForm/AwsIamResourceForm.tsx           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frontend/src/pages/pam/PamResourcesPage/components/PamResourceForm/AwsIamResourceForm.tsx b/frontend/src/pages/pam/PamResourcesPage/components/PamResourceForm/AwsIamResourceForm.tsx
index 80652b3b5..671f913e4 100644
--- a/frontend/src/pages/pam/PamResourcesPage/components/PamResourceForm/AwsIamResourceForm.tsx
+++ b/frontend/src/pages/pam/PamResourcesPage/components/PamResourceForm/AwsIamResourceForm.tsx
@@ -153,7 +153,7 @@ export const AwsIamResourceForm = ({ resource, onSubmit }: Props) => {
               <p className="mb-3 text-sm text-mineshaft-300">
                 This policy allows the Resource Role to assume target roles. For simplicity, use a
                 wildcard to allow assuming any role in your account. For more granular control,
-                replace <code className="rounded bg-mineshaft-700 px-1 text-xs">/*</code> with a
+                replace <code className="rounded bg-mineshaft-700 px-1 text-xs">*</code> with a
                 specific pattern like{" "}
                 <code className="rounded bg-mineshaft-700 px-1 text-xs">/pam-*</code> or{" "}
                 <code className="rounded bg-mineshaft-700 px-1 text-xs">/infisical-*</code>.