From b50639376578a08481d5216b17e3acedca9889ba Mon Sep 17 00:00:00 2001
From: carlosmonastyrski <charly.monastyrski@gmail.com>
Date: Fri, 25 Apr 2025 16:35:57 -0300
Subject: [PATCH] feat(aws-iam-rotation): docs improvements

---
 .../platform/secret-rotation/aws-iam-user-secret.mdx      | 8 ++++----
 .../AwsIamUserSecretRotationParametersFields.tsx          | 3 ++-
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/documentation/platform/secret-rotation/aws-iam-user-secret.mdx b/docs/documentation/platform/secret-rotation/aws-iam-user-secret.mdx
index 2b7a44c40..1e8eb3950 100644
--- a/docs/documentation/platform/secret-rotation/aws-iam-user-secret.mdx
+++ b/docs/documentation/platform/secret-rotation/aws-iam-user-secret.mdx
@@ -22,7 +22,7 @@ at a specified interval or on-demand.
           "iam:CreateAccessKey",
           "iam:UpdateAccessKey",
           "iam:DeleteAccessKey",
-		  "iam:ListUsers"
+          "iam:ListUsers"
         ],
         "Resource": "*"
       }
@@ -68,7 +68,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
 				5. Specify the secret names that the AWS IAM access key credentials should be mapped to. Then click **Next**.
 				![Rotation Secrets Mapping](/images/secret-rotations-v2/aws-iam-user-secret/aws-iam-user-secret-secrets-mapping.png)
 
-					- **Access Key ID** - the name of the secret that the aws access key ID will be mapped to.
+					- **Access Key ID** - the name of the secret that the AWS access key ID will be mapped to.
 					- **Secret Access Key** - the name of the secret that the rotated secret access key will be mapped to.
 
 				6. Give your rotation a name and description (optional). Then click **Next**.
@@ -97,7 +97,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
 					--url https://us.infisical.com/api/v2/secret-rotations/aws-iam-user-secret \
 					--header 'Content-Type: application/json' \
 					--data '{
-					"name": "My AWS rotation",
+					"name": "my-aws-rotation",
 					"projectId": "9602cfc5-20b9-4c35-a056-dd7372db0f25",
 					"description": "My rotation strategy description",
 					"connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
@@ -126,7 +126,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
 				{
 					"secretRotation": {
 						"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
-						"name": "My AWS rotation",
+						"name": "my-aws-rotation",
 						"description": "My rotation strategy description",
 						"secretsMapping": {
 							"accessKeyId": "AWS_ACCESS_KEY_ID",
diff --git a/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ParametersFields/AwsIamUserSecretRotationParametersFields.tsx b/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ParametersFields/AwsIamUserSecretRotationParametersFields.tsx
index 3898655d2..525bde198 100644
--- a/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ParametersFields/AwsIamUserSecretRotationParametersFields.tsx
+++ b/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ParametersFields/AwsIamUserSecretRotationParametersFields.tsx
@@ -69,10 +69,11 @@ export const AwsIamUserSecretRotationParametersFields = () => {
         name="parameters.region"
         render={({ field: { value, onChange }, fieldState: { error } }) => (
           <FormControl
+            isOptional
             isError={Boolean(error)}
             errorText={error?.message}
             label="Region"
-            helperText="Required only if no global scope is set."
+            tooltipText="Required only if no global scope is set."
           >
             <AwsRegionSelect value={value ?? ""} onChange={onChange} />
           </FormControl>