diff --git a/docs/documentation/platform/secret-rotation/aws-iam.mdx b/docs/documentation/platform/secret-rotation/aws-iam.mdx
index ee6520382..b4247af80 100644
--- a/docs/documentation/platform/secret-rotation/aws-iam.mdx
+++ b/docs/documentation/platform/secret-rotation/aws-iam.mdx
@@ -3,121 +3,141 @@ title: "AWS IAM User"
description: "Rotated access key id and secret key of AWS IAM Users"
---
-Infisical AWS IAM User rotation enables the periodic updating of AWS IAM User access keys. Each user can maintain up to two keys simultaneously.
+Infisical's AWS IAM User secret rotation capability lets you update the **Access key** and **Secret access key** credentials of a target IAM user from within Infisical
+at a specified interval or on-demand.
-## Prerequisite
+## Workflow
+
+The typical workflow for using the AWS IAM User rotation strategy consists of four steps:
+
+1. Creating the target IAM user whose credentials you wish to rotate.
+2. Creating the managing IAM user used by Infisical to rotate the credentials of the target IAM user.
+3. Configuring the rotation strategy in Infisical with the credentials of the managing IAM user.
+4. Pressing the **Rotate** button in the Infisical dashboard to trigger the rotation of the target IAM user's credentials. The strategy can also be configured to rotate the credentials automatically at a specified interval.
+
+In the following steps, we explore the end-to-end workflow for setting up this strategy in Infisical.
-
- This AWS IAM User is the one that Infisical uses to get into your AWS account and handle the access keys for the IAM users underneath.
-
- Create the manager user IAM Policy
+
+ To begin, create an IAM user whose credentials you wish to rotate. If you already have an IAM user,
+ then you can skip this step.
+
+
+ Next, create another IAM user to be used by Infisical to rotate the credentials of the IAM user in the previous step.
- 1. Open [AWS Policy Builder](https://console.aws.amazon.com/iam/home#/policies$new?step=edit)
- 2. Use JSON tab to paste the JSON policy
- 3. Paste the following scope
- ```json
- {
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "VisualEditor0",
- "Effect": "Allow",
- "Action": [
- "iam:DeleteAccessKey",
- "iam:GetAccessKeyLastUsed",
- "iam:CreateAccessKey"
- ],
- "Resource": "arn:aws:iam::*:user/infisical/rotate/*"
- }
- ]
- }
- ```
-
- The IAM policy mentioned above is configured with an IAM path of **/infisical/rotate**.
-
- This implies that managing users must be positioned within this specified path.
- If modifying this path, ensure that corresponding adjustments are made in the subsequent steps when creating managed users.
-
- During testing, you have the option to utilize the wildcard option **Resource: "*"**. However, it's crucial to refrain from using * in production environments.
-
-
- Create the managed user IAM
-
- 1. Create the IAM user in AWS with the above policy.
- 2. Then create the [AWS IAM User access key.](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey)
-
-
- This AWS IAM User is designated to manage credential rotations for infisical.
-
- If this user already exists, ensure all other access keys associated with it are removed. AWS enforces a strict limit of 2 access keys per IAM User.
-
-
- 1. Go to the AWS IAM Section.
- 2. Select Users and then click on Create User.
- 3. Attach policies as required.
-
- As mentioned in the previous step, if you've specified a path to control access for the manager user, you must also provide the path when creating the user here.
-
- However, the AWS console does not support the path option for this purpose. You'll need to use either the CLI or AWS API to create a user with a specified path.
-
- [Please refer to the AWS documentation for further guidance](https://aws.amazon.com/blogs/security/optimize-aws-administration-with-iam-paths/).
-
-
-
-## Working
-
-1. Infisical connects your provided `manager aws iam` user.
-2. It will then create the new access key id and secret key for the `managed iam user`.
-3. Save the new credentials to the mapped outputs in your secret board, so that rest of the systems can access it.
-4. The retired credentials gets deleted on each cycle.
-
-## Rotation Configuration
-
-
-
- Head over to Secret Rotation configuration page of your project by clicking on `Secret Rotation` in the left side bar
-
-
-
-
- These are inputs required by AWS IAM Rotation Providers
-
- - Manager User Access Key
-
- AWS IAM Rotator user access key
-
- - Manager User Secret Key
-
- AWS IAM Rotator user secret key
-
- - Manager User AWS Region
+ 2.1. In your AWS console, head to IAM > Access management > Users and press **Create user**.
- IAM policies are global. But AWS needs to know a region to send requests to a partition.
+ 
+
+ 2.2. Next, give the user a username like **infisical-rotation-manager** and press **Next**.
- - IAM Username
+ 
+
+ 2.3. Next, in the **Set permissions** step, select **Attach policies directly** and then press **Create policy**.
+
+ 
+
+ 2.4. Next, in the **Policy editor**, paste the following JSON and press **Next**:
- AWS IAM User's username whose credentials are rotated
-
-
+ ```json
+ {
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Sid": "VisualEditor0",
+ "Effect": "Allow",
+ "Action": [
+ "iam:DeleteAccessKey",
+ "iam:GetAccessKeyLastUsed",
+ "iam:CreateAccessKey"
+ ],
+ "Resource": "*"
+ }
+ ]
+ }
+ ```
-
+
+ The IAM policy above uses the wildcard option in Resource: "*".
+
+ You may want to restrict the policy to a specific path, and make any adjustments as necessary, to control access for the managing user in production.
+
+ Read more about this [here](https://aws.amazon.com/blogs/security/optimize-aws-administration-with-iam-paths/).
+
+
+ In the **Review and create** step, give the policy a name like **infisical-rotation-manager**, press **Create policy** to finish creating the policy.
+
+ 
- The secret keys to be replaced in the provided board after successful secret rotation
+ 2.5. Back in the **Set permissions** step from step 2.3, refresh the policy list and search for the policy you just created from step 2.4.
+
+ Select the policy and press **Next**.
+
+ 
+
+ In the **Review and create** step, press **Create user** to finish creating the IAM user.
+
+ 
+
+ 2.5. Having created the user, head to its Security credentials > Access keys and press **Create access key**.
- - Select `Environment`, `Secret Path` and `Interval` to rotate the secrets
- - Finally select the secrets in your provided board to replace with new secret after each rotation
+ Follow the subsequent steps to create the **access key** and **secret access key** credential pair for the user.
- - IAM User Access Key
+ 
+
+ At the end of the flow, copy the **Access key** and **Secret access key** to use when configuring the AWS IAM User rotation strategy back in Infisical next.
+
+ 
+
+
+ 3.1. Back in Infisical, head to the Project > Secrets > Environment and path where you want the rotated AWS IAM credentials to appear and create two placeholder secrets.
+
+ In this example, we'll create two secrets called `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY`.
+
+ 
+
+ 3.2. Next, in the **Secret Rotation** tab, press on the **AWS IAM** tile to configure the AWS IAM User rotation strategy.
+
+ 
+
+ 3.3. Input the configuration details for the AWS IAM User rotation strategy obtained from steps 1 and 2:
+
+ 
+
+ Here's some guidance on each field:
+
+ - Manager User Access Key: The managing IAM user's access key from step 2.5.
+ - Manager User Secret Key: The managing IAM user's secret access key from step 2.5.
+ - Manager User AWS Region: The [AWS region](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html) for Infisical to make requests to such as `us-east-1`.
+ - IAM Username: The IAM username of the user from step 1.
+
+ Next, specify the output secret mappings configuration for the rotated AWS IAM credentials; this is the secrets whose values will be replaced with new credentials after each rotation.
+ Here, you can also specify a rotation interval for the credentials to be automatically rotated periodically.
- The rotated AWS IAM User access key id
-
- - IAM User Secret Key
-
- The rotated AWS IAM User secret key
-
- - Your done and good to go.
-
+ In this example, we want to map the output of the rotated AWS IAM credentials to the secrets that we created in step 3.1 (i.e. `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY`).
+
+ 
+
+ Finally, press **Submit** to create the secret rotation strategy.
+
+
+ You should now see the AWS IAM User rotation strategy listed in the **Secret Rotation** tab.
+
+ To manually trigger a rotation, you can press the **Rotate** button on the strategy.
+ Once triggered, the secrets in step 3.1 should be updated with new rotated credential values.
+
+ 
+
-Congratulations. You have improved your AWS IAM User security.
+**FAQ**
+
+
+
+ There are a few reasons for why this might happen:
+
+ - The strategy configuration is invalid (e.g. the managing IAM user's credentials are incorrect, the target IAM username is incorrect, etc.).
+ - The managing IAM user is insufficently permissioned to rotate the credentials of the target IAM user. For instance, you may have setup [paths](https://aws.amazon.com/blogs/security/optimize-aws-administration-with-iam-paths/) for the managing IAM user and the policy does not have the necessary permissions to rotate the credentials.
+ - The target IAM user already has 2 access keys configured in AWS; you should delete one of the access keys to allow for rotation.
+
+
\ No newline at end of file
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-config-1.png b/docs/images/platform/secret-rotation/aws-iam/rotation-config-1.png
new file mode 100644
index 000000000..2e6e5b830
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-config-1.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-config-2.png b/docs/images/platform/secret-rotation/aws-iam/rotation-config-2.png
new file mode 100644
index 000000000..487147c47
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-config-2.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-config-secrets.png b/docs/images/platform/secret-rotation/aws-iam/rotation-config-secrets.png
new file mode 100644
index 000000000..8a15d486f
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-config-secrets.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-key-third-party.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-key-third-party.png
new file mode 100644
index 000000000..8e01b60f5
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-key-third-party.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-keys.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-keys.png
new file mode 100644
index 000000000..f30b69dad
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-access-keys.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-attach-policy.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-attach-policy.png
new file mode 100644
index 000000000..4944366de
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-attach-policy.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-access-key.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-access-key.png
new file mode 100644
index 000000000..7a71e4a5e
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-access-key.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-policy.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-policy.png
new file mode 100644
index 000000000..46ae782e1
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-policy.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-user.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-user.png
new file mode 100644
index 000000000..05542dae3
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-create-user.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-policy-review.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-policy-review.png
new file mode 100644
index 000000000..ae81055b0
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-policy-review.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-user-review.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-user-review.png
new file mode 100644
index 000000000..34773f913
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-user-review.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotation-manager-username.png b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-username.png
new file mode 100644
index 000000000..573c3cf94
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotation-manager-username.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotations-aws-iam-user.png b/docs/images/platform/secret-rotation/aws-iam/rotations-aws-iam-user.png
new file mode 100644
index 000000000..5ea395e68
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotations-aws-iam-user.png differ
diff --git a/docs/images/platform/secret-rotation/aws-iam/rotations-select-aws-iam-user.png b/docs/images/platform/secret-rotation/aws-iam/rotations-select-aws-iam-user.png
new file mode 100644
index 000000000..17bbe3b1f
Binary files /dev/null and b/docs/images/platform/secret-rotation/aws-iam/rotations-select-aws-iam-user.png differ
diff --git a/docs/images/secret-rotation/aws-iam-inputs.png b/docs/images/secret-rotation/aws-iam-inputs.png
deleted file mode 100644
index 5b113e119..000000000
Binary files a/docs/images/secret-rotation/aws-iam-inputs.png and /dev/null differ
diff --git a/docs/images/secret-rotation/aws-iam-outputs.png b/docs/images/secret-rotation/aws-iam-outputs.png
deleted file mode 100644
index 500682cd6..000000000
Binary files a/docs/images/secret-rotation/aws-iam-outputs.png and /dev/null differ