Start docs for AWS IAM auth

docs/documentation/platform/identities/aws-iam-auth.mdx

@@ -0,0 +1,12 @@
+---
+title: AWS IAM Auth
+description: "Learn how to authenticate with Infisical from AWS."
+---
+
+**AWS IAM Auth** is an AWS-native authentication method that can be configured for a [machine identity](/documentation/platform/identities/machine-identities) to access Infisical from AWS.
+
+In this method, each identity is configured to represent one or more IAM principals in AWS with shared privileges.
+
+## Workflow
+
+TODO

docs/documentation/platform/identities/universal-auth.mdx

@@ -27,18 +27,18 @@ using the Universal Auth authentication method.
     ![identities organization](/images/platform/identities/identities-org.png)
 
     When creating an identity, you specify an organization level [role](/documentation/platform/role-based-access-controls) for it to assume; you can configure roles in Organization Settings > Access Control > Organization Roles.
-    
+
     ![identities organization create](/images/platform/identities/identities-org-create.png)
 
     Now input a few details for your new identity. Here's some guidance for each field:
 
     - Name (required): A friendly name for the identity.
     - Role (required): A role from the **Organization Roles** tab for the identity to assume. The organization role assigned will determine what organization level resources this identity can have access to.
-    
+
     Once you've created an identity, you'll be prompted to configure the **Universal Auth** authentication method for it.
-    
+
     ![identities organization create auth method](/images/platform/identities/identities-org-create-auth-method.png)
-    
+
     Here's some more guidance on each field:
 
     - Access Token TTL (default is `2592000` equivalent to 30 days): The lifetime for an acccess token in seconds. This value will be referenced at renewal time.
@@ -78,8 +78,9 @@ using the Universal Auth authentication method.
     Next, select the identity you want to add to the project and the project level role you want to allow it to assume. The project role assigned will determine what project level resources this identity can have access to.
 
     ![identities project](/images/platform/identities/identities-project.png)
-    
+
     ![identities project create](/images/platform/identities/identities-project-create.png)
+
   </Step>
   <Step title="Accessing the Infisical API with the identity">
     To access the Infisical API as the identity, you should first perform a login operation
@@ -94,9 +95,9 @@ using the Universal Auth authentication method.
       --data-urlencode 'clientSecret=...' \
       --data-urlencode 'clientId=...'
     ```
-    
+
     #### Sample response
-    
+
     ```
     {
       "accessToken": "...",
@@ -107,7 +108,7 @@ using the Universal Auth authentication method.
     ```
 
     Next, you can use the access token to authenticate with the [Infisical API](/api-reference/overview/introduction)
-    
+
     <Note>
       Each identity access token has a time-to-live (TLL) which you can infer from the response of the login operation;
       the default TTL is `7200` seconds which can be adjusted.
@@ -115,6 +116,7 @@ using the Universal Auth authentication method.
       If an identity access token expires, it can no longer authenticate with the Infisical API. In this case,
       a new access token should be obtained by performing another login operation.
     </Note>
+
   </Step>
 </Steps>
 
@@ -134,7 +136,8 @@ using the Universal Auth authentication method.
   
   In certain cases, you may want to extend the lifespan of an access token; to do so, you must set a max TTL parameter.
 
-  A token can be renewed any number of time and each call to renew it will extend the toke life by increments of access token TTL. 
-  Regardless of how frequently an access token is renewed, its lifespan remains bound to the maximum TTL determined at its creation
+A token can be renewed any number of time and each call to renew it will extend the toke life by increments of access token TTL.
+Regardless of how frequently an access token is renewed, its lifespan remains bound to the maximum TTL determined at its creation
+
 </Accordion>
-</AccordionGroup>
+</AccordionGroup>