Prerequisite
Infisical needs an AWS IAM principal (a user or a role) with the required permissions to create and manage other IAM users. This principal will be responsible for the lifecycle of the dynamically generated users.Required IAM Permissions
Required IAM Permissions
arn:aws:iam::<account-id>:user/<aws-scope-path>Replace <account id> with your AWS account id and <aws-scope-path> with a path to minimize managing user access.
Set up Dynamic Secrets with AWS IAM
Infisical will assume the provided role in your AWS account securely, without the need to share any credentials.
Self-Hosted Instance
Self-Hosted Instance
To connect your self-hosted Infisical instance with AWS, you need to set up an AWS IAM User account that can assume the configured AWS IAM Role.If your instance is deployed on AWS, the aws-sdk will automatically retrieve the credentials. Ensure that you assign the provided permission policy to your deployed instance, such as ECS or EC2.The following steps are for instances not deployed on AWS:
1
Create an IAM User
Navigate to Create IAM User in your AWS Console.
2
Create an Inline Policy
Attach the following inline permission policy to the IAM User to allow it to assume any IAM Roles:
3
Obtain the IAM User Credentials
Obtain the AWS access key ID and secret access key for your IAM User by navigating to IAM > Users > [Your User] > Security credentials > Access keys.
4
Set Up Connection Keys
- Set the access key as DYNAMIC_SECRET_AWS_ACCESS_KEY_ID.
- Set the secret key as DYNAMIC_SECRET_AWS_SECRET_ACCESS_KEY.
1
Create the Managing User IAM Role for Infisical
-
Navigate to the Create IAM Role page in your AWS Console.
- Select AWS Account as the Trusted Entity Type.
- Select Another AWS Account and provide the appropriate Infisical AWS Account ID: use 381492033652 for the US region, and 345594589636 for the EU region. This restricts the role to be assumed only by Infisical. If self-hosting, provide your AWS account number instead.
- (Recommended) Enable “Require external ID” and input your Project ID to strengthen security and mitigate the confused deputy problem.
- Assign permission as shared in prerequisite.
When configuring an IAM Role that Infisical will assume, it’s highly recommended to enable the “Require external ID” option and specify your Project ID.This precaution helps protect your AWS account against the confused deputy problem, a potential security vulnerability where Infisical could be tricked into performing actions on your behalf by an unauthorized actor.
2
Copy the AWS IAM Role ARN
3
Secret Overview Dashboard
Navigate to the Secret Overview dashboard and select the environment in which you would like to add a dynamic secret to.
4
Click on the 'Add Dynamic Secret' button
5
Select AWS IAM
6
Provide the inputs for dynamic secret parameters
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 after a secret is generated)
Maximum time-to-live for a generated secret
Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.Allowed template variables are
{{randomUsername}}: Random username string{{unixTimestamp}}: Current Unix timestamp{{identity.name}}: Name of the identity that is generating the secret{{random N}}: Random string of N characters
truncate: Truncates a string to a specified lengthreplace: Replaces a substring with another value
Tags to be added to the created IAM User resource.
Select Assume Role method.
The ARN of the AWS Role to assume.
IAM AWS Path to scope created IAM User resource access.
The AWS data center region.
The IAM Policy ARN of the AWS Permissions Boundary 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
Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.Allowed template variables are
{{randomUsername}}: Random username string{{unixTimestamp}}: Current Unix timestamp
7
Click 'Submit'
After submitting the form, you will see a dynamic secret created in the dashboard.
8
Generate dynamic secrets
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.
Once you click the 
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 falls within the maximum TTL defined when configuring the dynamic secret in step 4.
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 to 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 button as illustrated below.
Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
secret