diff --git a/docs/documentation/platform/dynamic-secrets/aws-iam.mdx b/docs/documentation/platform/dynamic-secrets/aws-iam.mdx
new file mode 100644
index 000000000..a8e201b54
--- /dev/null
+++ b/docs/documentation/platform/dynamic-secrets/aws-iam.mdx
@@ -0,0 +1,151 @@
+---
+title: "AWS IAM"
+description: "How to dynamically generate AWS IAM Users."
+---
+
+The Infisical AWS IAM dynamic secret allows you to generate AWS IAM Users on demand based on configured AWS policy.
+
+## Prerequisite
+
+Infisical requires an AWS IAM user with the necessary permissions. This will be the managing user who will create new users, new access keys, attach policies and remove all on clean up.
+
+
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:AttachUserPolicy",
+ "iam:CreateAccessKey",
+ "iam:CreateUser",
+ "iam:DeleteAccessKey",
+ "iam:DeleteUser",
+ "iam:DeleteUserPolicy",
+ "iam:DetachUserPolicy",
+ "iam:GetUser",
+ "iam:ListAccessKeys",
+ "iam:ListAttachedUserPolicies",
+ "iam:ListGroupsForUser",
+ "iam:ListUserPolicies",
+ "iam:PutUserPolicy",
+ "iam:AddUserToGroup",
+ "iam:RemoveUserFromGroup"
+ ],
+ "Resource": ["*"]
+ }
+ ]
+}
+```
+
+To minimise managing user access you can attach a resource in format
+
+> arn:aws:iam::\:user/\
+
+Replace **\** with your AWS account id and **\** with a path to minimize managing user access.
+
+
+
+## Set up Dynamic Secrets with AWS IAM
+
+
+
+ Open the Secret Overview dashboard and select the environment in which you would like to add a dynamic secret.
+
+
+ 
+
+
+ 
+
+
+
+ Name by which you want the secret to be referenced
+
+
+
+ Default time-to-live for a generated secret (it is possible to modify this value when a secret is generate)
+
+
+
+ Maximum time-to-live for a generated secret
+
+
+
+ The managing AWS IAM User Access Key
+
+
+
+ The managing AWS IAM User Secret Key
+
+
+
+ [IAM AWS Path](https://aws.amazon.com/blogs/security/optimize-aws-administration-with-iam-paths/) to scope created IAM User resource access.
+
+
+
+ The AWS data center region.
+
+
+
+ The IAM Policy ARN of the [AWS Permissions Boundary](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) to attach to IAM users created in the role.
+
+
+
+ The AWS IAM groups that should be assigned to the created users. Multiple values can be provided by separating them with commas
+
+
+
+ The AWS IAM managed policies that should be attached to the created users. Multiple values can be provided by separating them with commas
+
+
+
+ The AWS IAM inline policy that should be attached to the created users. Multiple values can be provided by separating them with commas
+
+
+ 
+
+
+
+ After submitting the form, you will see a dynamic secret created in the dashboard.
+
+ 
+
+
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
+
+ 
+ 
+
+ When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
+
+ 
+
+
+ Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret in step 4.
+
+
+
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+
+ 
+
+
+
+## Audit or Revoke Leases
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+This will allow you see the lease details and delete the lease ahead of its expiration time.
+
+
+
+## Renew Leases
+To extend the life of the generated dynamic secret lease past its initial time to live, simply click on the **Renew** as illustrated below.
+
+
+
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-modal-aws-iam.png b/docs/images/platform/dynamic-secrets/dynamic-secret-modal-aws-iam.png
new file mode 100644
index 000000000..3ae9155a3
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-modal-aws-iam.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png b/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png
new file mode 100644
index 000000000..d412109fa
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png differ
diff --git a/docs/images/platform/dynamic-secrets/lease-values-aws-iam.png b/docs/images/platform/dynamic-secrets/lease-values-aws-iam.png
new file mode 100644
index 000000000..4764eceb2
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/lease-values-aws-iam.png differ
diff --git a/docs/mint.json b/docs/mint.json
index b38b5fa52..f74a422a4 100644
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -146,7 +146,8 @@
"documentation/platform/dynamic-secrets/postgresql",
"documentation/platform/dynamic-secrets/mysql",
"documentation/platform/dynamic-secrets/oracle",
- "documentation/platform/dynamic-secrets/cassandra"
+ "documentation/platform/dynamic-secrets/cassandra",
+ "documentation/platform/dynamic-secrets/aws-iam"
]
},
"documentation/platform/groups"