AWS Connection

Learn how to configure an AWS Connection for Infisical.

Infisical supports two methods for connecting to AWS.

Assume Role (Recommended)

Infisical will assume the provided role in your AWS account securely, without the need to share any credentials.

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 Infisical instance is deployed on AWS (e.g. EC2, ECS, or EKS), you do not need to provide static credentials. When the INF_APP_CONNECTION_AWS_ACCESS_KEY_ID and INF_APP_CONNECTION_AWS_SECRET_ACCESS_KEY environment variables are not set, Infisical will automatically retrieve credentials from your instance’s environment (instance profile, task role, or IRSA). Simply ensure that the IAM role attached to your compute has the permission policy below to assume your target roles.

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:

   {
       "Version": "2012-10-17",
       "Statement": [
   {
       "Sid": "AllowAssumeAnyRole",
       "Effect": "Allow",
       "Action": "sts:AssumeRole",
       "Resource": "arn:aws:iam::*:role/*"
   }
       ]
   }
   
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

   1. Set the access key as INF_APP_CONNECTION_AWS_ACCESS_KEY_ID.
   2. Set the secret key as INF_APP_CONNECTION_AWS_SECRET_ACCESS_KEY.

1. Create the Managing User IAM Role for Infisical

   1. Navigate to the Create IAM Role page in your AWS Console.

      

   2. Select AWS Account as the Trusted Entity Type.

   3. 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.

   For Dedicated Instances: Your AWS account ID differs from the one provided above. Please reach out to Infisical support to obtain your AWS account ID.

   4. (Recommended) Enable “Require external ID” and input your Organization ID to strengthen security and mitigate the confused deputy problem.

   When configuring an IAM Role that Infisical will assume, it’s highly recommended to enable the “Require external ID” option and specify your Organization 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. Add Required Permissions to the IAM Role

   Navigate to your IAM role permissions and click Create Inline Policy.

   

   Depending on your use case, add one or more of the following policies to your IAM Role:

   Secret Sync

   AWS Secrets Manager

   Use the following custom policy to grant the minimum permissions required by Infisical to sync secrets to AWS Secrets Manager:

   

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowSecretsManagerAccess",
               "Effect": "Allow",
               "Action": [
                   "secretsmanager:ListSecrets",
                   "secretsmanager:GetSecretValue",
                   "secretsmanager:BatchGetSecretValue",
                   "secretsmanager:CreateSecret",
                   "secretsmanager:UpdateSecret",
                   "secretsmanager:DeleteSecret",
                   "secretsmanager:DescribeSecret",
                   "secretsmanager:TagResource",
                   "secretsmanager:UntagResource",
                   "kms:ListAliases", // if you need to specify the KMS key
                   "kms:Encrypt", // if you need to specify the KMS key
                   "kms:Decrypt", // if you need to specify the KMS key
                   "kms:DescribeKey" // if you need to specify the KMS key
               ],
               "Resource": "*"
           }
       ]
   }
   

   If using a custom KMS key, be sure to add the IAM user or role as a key user.

   AWS Parameter Store

   Use the following custom policy to grant the minimum permissions required by Infisical to sync secrets to AWS Parameter Store:

   

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowSSMAccess",
               "Effect": "Allow",
               "Action": [
                   "ssm:PutParameter",
                   "ssm:GetParameters",
                   "ssm:GetParametersByPath",
                   "ssm:DescribeParameters",
                   "ssm:DeleteParameters",
                   "ssm:ListTagsForResource", // if you need to add tags to secrets
                   "ssm:AddTagsToResource", // if you need to add tags to secrets
                   "ssm:RemoveTagsFromResource", // if you need to add tags to secrets
                   "kms:ListAliases", // if you need to specify the KMS key
                   "kms:Encrypt", // if you need to specify the KMS key
                   "kms:Decrypt", // if you need to specify the KMS key
                   "kms:DescribeKey" // if you need to specify the KMS key
               ],
               "Resource": "*"
           }
       ]
   }
   

   If using a custom KMS key, be sure to add the IAM user or role as a key user.

   Secret Rotation

   AWS IAM

   Use the following custom policy to grant the minimum permissions required by Infisical to rotate secrets to AWS Access Keys:

   

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Effect": "Allow",
               "Action": [
                   "iam:ListAccessKeys",
                   "iam:CreateAccessKey",
                   "iam:UpdateAccessKey",
                   "iam:DeleteAccessKey",
                   "iam:ListUsers"
               ],
               "Resource": "*"
           }
       ]
   }
   

   PKI Sync

   AWS Certificate Manager

   Use the following custom policy to grant the minimum permissions required by Infisical to sync certificates to AWS Certificate Manager:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowCertificateManagerAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:ListCertificates",
                   "acm:DescribeCertificate",
                   "acm:GetCertificate",
                   "acm:ImportCertificate",
                   "acm:ExportCertificate",
                   "acm:DeleteCertificate",
                   "acm:AddTagsToCertificate",
                   "acm:RemoveTagsFromCertificate",
                   "acm:ListTagsForCertificate"
               ],
               "Resource": "*"
           }
       ]
   }
   

   • ListCertificates: Lists all certificates in the account
   • ImportCertificate: Imports certificates from Infisical into AWS Certificate Manager
   • ExportCertificate: Exports certificates for synchronization
   • DeleteCertificate: Removes certificates that are no longer managed by Infisical
   • DescribeCertificate and GetCertificate: Retrieves certificate details for comparison during sync
   • Tag-related permissions: Manages certificate tags for identification and organization

   AWS Elastic Load Balancer

   Use the following custom policy to grant the minimum permissions required by Infisical to sync certificates to AWS Elastic Load Balancers:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowCertificateManagerAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:ListCertificates",
                   "acm:DescribeCertificate",
                   "acm:ImportCertificate",
                   "acm:DeleteCertificate",
                   "acm:ListTagsForCertificate"
               ],
               "Resource": "*"
           },
           {
               "Sid": "AllowElasticLoadBalancerAccess",
               "Effect": "Allow",
               "Action": [
                   "elasticloadbalancing:DescribeLoadBalancers",
                   "elasticloadbalancing:DescribeListeners",
                   "elasticloadbalancing:DescribeListenerCertificates",
                   "elasticloadbalancing:AddListenerCertificates",
                   "elasticloadbalancing:RemoveListenerCertificates",
                   "elasticloadbalancing:ModifyListener"
               ],
               "Resource": "*"
           }
       ]
   }
   

   ACM Permissions:

   • ListCertificates: Lists all certificates in the account
   • ImportCertificate: Imports certificates from Infisical into AWS Certificate Manager
   • DeleteCertificate: Removes certificates that are no longer managed by Infisical
   • DescribeCertificate: Retrieves certificate details for comparison during sync
   • ListTagsForCertificate: Retrieves certificate tags for identification

   ELB Permissions:

   • DescribeLoadBalancers: Lists available load balancers for selection
   • DescribeListeners: Lists HTTPS/TLS listeners on load balancers
   • DescribeListenerCertificates: Lists certificates attached to listeners
   • AddListenerCertificates: Attaches certificates to listeners
   • RemoveListenerCertificates: Removes certificates from listeners
   • ModifyListener: Sets the default certificate on listeners

   External Certificate Authority

   AWS Private CA

   Use the following custom policy to grant the minimum permissions required by Infisical to issue certificates via AWS Private CA.

   For a single CA, scope the Resource to that CA’s ARN:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAwsPrivateCAAccess",
               "Effect": "Allow",
               "Action": [
                   "acm-pca:DescribeCertificateAuthority",
                   "acm-pca:GetCertificateAuthorityCertificate",
                   "acm-pca:IssueCertificate",
                   "acm-pca:GetCertificate",
                   "acm-pca:RevokeCertificate"
               ],
               "Resource": "arn:aws:acm-pca:us-east-1:123456789012:certificate-authority/your-ca-id"
           }
       ]
   }
   

   For multiple CAs, list each ARN in the Resource array:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAwsPrivateCAAccess",
               "Effect": "Allow",
               "Action": [
                   "acm-pca:DescribeCertificateAuthority",
                   "acm-pca:GetCertificateAuthorityCertificate",
                   "acm-pca:IssueCertificate",
                   "acm-pca:GetCertificate",
                   "acm-pca:RevokeCertificate"
               ],
               "Resource": [
                   "arn:aws:acm-pca:us-east-1:123456789012:certificate-authority/ca-id-1",
                   "arn:aws:acm-pca:us-west-2:123456789012:certificate-authority/ca-id-2"
               ]
           }
       ]
   }
   

   • DescribeCertificateAuthority: Validates the CA status and configuration
   • GetCertificateAuthorityCertificate: Retrieves the CA certificate and chain
   • IssueCertificate: Issues certificates from the private CA
   • GetCertificate: Retrieves issued certificates
   • RevokeCertificate: Revokes previously issued certificates

   Using a specific CA ARN in Resource is recommended over "*" to follow the principle of least privilege.

   AWS ACM Public CA

   Use the following custom policy to grant the minimum permissions required by Infisical to issue publicly-trusted certificates via AWS Certificate Manager and perform DNS validation through Route 53.

   ACM permissions — RequestCertificate cannot be scoped below "*" because the certificate ARN does not exist until after the call succeeds:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAcmPublicCaAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:RequestCertificate",
                   "acm:DescribeCertificate",
                   "acm:ExportCertificate",
                   "acm:RenewCertificate",
                   "acm:RevokeCertificate",
                   "acm:ListCertificates"
               ],
               "Resource": "*"
           }
       ]
   }
   

   Route 53 permissions — scope to the hosted zone(s) used for DNS validation:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowRoute53ForAcmValidation",
               "Effect": "Allow",
               "Action": [
                   "route53:GetHostedZone",
                   "route53:ChangeResourceRecordSets"
               ],
               "Resource": "arn:aws:route53:::hostedzone/YOUR_HOSTED_ZONE_ID"
           }
       ]
   }
   

   ACM and Route 53 permissions can live on the same IAM principal, or be split across two separate connections in Infisical.

   ACM Permissions:

   • RequestCertificate: Requests a new public certificate from ACM
   • DescribeCertificate: Retrieves certificate status and DNS validation records
   • ExportCertificate: Exports the issued certificate and private key to Infisical
   • RenewCertificate: Triggers renewal of an existing certificate
   • RevokeCertificate: Revokes a previously issued certificate
   • ListCertificates: Used during connection validation

   Route 53 Permissions:

   • GetHostedZone: Validates the hosted zone during CA setup
   • ChangeResourceRecordSets: Writes the ACM DNS validation CNAME records

   PAM Session Recording

   AWS S3 Bucket

   Use the following custom policy to grant the minimum permissions required by Infisical to store and play back PAM session recordings in your S3 bucket. Replace your-pam-recordings-bucket with the bucket name you configure in Project Settings → Session Recording.

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowPamRecordingBucketAccess",
               "Effect": "Allow",
               "Action": [
                   "s3:PutObject",
                   "s3:GetObject"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket/*"
           },
           {
               "Sid": "AllowPamRecordingBucketTest",
               "Effect": "Allow",
               "Action": [
                   "s3:ListBucket"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket"
           },
           {
               "Sid": "AllowPamRecordingConnectionTestCleanup",
               "Effect": "Allow",
               "Action": [
                   "s3:DeleteObject"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket/.test/*"
           }
       ]
   }
   

   If you scoped the recording config to a key prefix (for example pam/prod), update all three Resource ARNs to include the prefix:

   "Resource": "arn:aws:s3:::your-pam-recordings-bucket/pam/prod/*"
   

   "Resource": "arn:aws:s3:::your-pam-recordings-bucket/pam/prod/.test/*"
   

   S3 Permissions:

   • PutObject: Lets the gateway upload encrypted recording chunks via presigned PUT URLs. Also used by the connection test to write a probe object under {prefix}/.test/{uuid}.
   • GetObject: Lets the browser fetch encrypted chunks during playback via presigned GET URLs. Decryption happens locally in the browser; Infisical only ever sees ciphertext.
   • ListBucket: Required by HeadBucket, which Infisical calls during the connection test to confirm the bucket exists and the credentials can reach it.
   • DeleteObject (scoped to .test/*): Used only to clean up the probe object after the connection test. Infisical never deletes recording chunks. Your bucket lifecycle policy owns retention. When using a key prefix, the test object is written under {prefix}/.test/, so the DeleteObject resource must include the prefix.

   Recording chunks are encrypted with a per-session AES-256-GCM key on the gateway before they leave your network, and the session key is wrapped with Infisical’s KMS using session-bound AAD. Even if the bucket policy is wider than the principle of least privilege suggests, the ciphertext is not readable without an authenticated session-key unwrap.

   Bucket CORS Configuration

   During playback the browser fetches encrypted chunks directly from S3 using presigned GET URLs. For this to work the bucket needs a CORS policy that allows requests from your Infisical domain.

   Open the bucket in the AWS console, go to Permissions → Cross-origin resource sharing (CORS), and add:

   [
       {
           "AllowedHeaders": ["*"],
           "AllowedMethods": ["GET"],
           "AllowedOrigins": ["https://app.infisical.com"],
           "ExposeHeaders": [],
           "MaxAgeSeconds": 3600
       }
   ]
   

   Replace https://app.infisical.com with the origin where your Infisical dashboard is served (for example https://eu.infisical.com or http://localhost:8080 during development). You can list multiple origins if needed.

3. Copy the AWS IAM Role ARN

   
4. Setup AWS Connection in Infisical

   Infisical UI

   1. Navigate to the Integrations tab in the desired project, then select App Connections.

      

   2. Select the AWS Connection option.

      

   3. Select the Assume Role method option and provide the AWS IAM Role ARN obtained from the previous step and press Connect to AWS.

      

   4. Your AWS Connection is now available for use.

      

   API

   To create an AWS Connection, make an API request to the Create AWS Connection API endpoint.

   Sample request

   Request

   curl    --request POST \
           --url https://app.infisical.com/api/v1/app-connections/aws \
           --header 'Content-Type: application/json' \
           --data '{
               "name": "my-aws-connection",
               "method": "assume-role",
               "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
               "credentials": {
                   "roleArn": "...",
               }
           }'
   

   Sample response

   Response

   {
       "appConnection": {
           "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
           "name": "my-aws-connection",
           "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
           "version": 123,
           "orgId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
           "createdAt": "2023-11-07T05:31:56Z",
           "updatedAt": "2023-11-07T05:31:56Z",
           "app": "aws",
           "method": "assume-role",
           "credentials": {}
       }
   }
   

Access Key

Infisical will use the provided Access Key ID and Secret Key to connect to your AWS instance.

1. Add Required Permissions to the IAM User

   Navigate to your IAM user permissions and click Create Inline Policy.

   

   Depending on your use case, add one or more of the following policies to your user:

   Secret Sync

   AWS Secrets Manager

   Use the following custom policy to grant the minimum permissions required by Infisical to sync secrets to AWS Secrets Manager:

   

   {
       "Version": "2012-10-17",
       "Statement": [
   {
       "Sid": "AllowSecretsManagerAccess",
       "Effect": "Allow",
       "Action": [
           "secretsmanager:ListSecrets",
           "secretsmanager:GetSecretValue",
           "secretsmanager:BatchGetSecretValue",
           "secretsmanager:CreateSecret",
           "secretsmanager:UpdateSecret",
           "secretsmanager:DeleteSecret",
           "secretsmanager:DescribeSecret",
           "secretsmanager:TagResource",
           "secretsmanager:UntagResource",
           "kms:ListAliases", // if you need to specify the KMS key
           "kms:Encrypt", // if you need to specify the KMS key
           "kms:Decrypt", // if you need to specify the KMS key
           "kms:DescribeKey" // if you need to specify the KMS key
       ],
       "Resource": "*"
   }
       ]
   }
   

   If using a custom KMS key, be sure to add the IAM user or role as a key user.

   AWS Parameter Store

   Use the following custom policy to grant the minimum permissions required by Infisical to sync secrets to AWS Parameter Store:

   

   {
       "Version": "2012-10-17",
       "Statement": [
   {
       "Sid": "AllowSSMAccess",
       "Effect": "Allow",
       "Action": [
           "ssm:PutParameter",
           "ssm:GetParameters",
           "ssm:GetParametersByPath",
           "ssm:DescribeParameters",
           "ssm:DeleteParameters",
           "ssm:ListTagsForResource", // if you need to add tags to secrets
           "ssm:AddTagsToResource", // if you need to add tags to secrets
           "ssm:RemoveTagsFromResource", // if you need to add tags to secrets
           "kms:ListAliases", // if you need to specify the KMS key
           "kms:Encrypt", // if you need to specify the KMS key
           "kms:Decrypt", // if you need to specify the KMS key
           "kms:DescribeKey" // if you need to specify the KMS key
       ],
       "Resource": "*"
   }
       ]
   }
   

   If using a custom KMS key, be sure to add the IAM user or role as a key user.

   Secret Rotation

   AWS IAM

   Use the following custom policy to grant the minimum permissions required by Infisical to rotate secrets to AWS Access Keys:

   

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Effect": "Allow",
               "Action": [
                   "iam:ListAccessKeys",
                   "iam:CreateAccessKey",
                   "iam:UpdateAccessKey",
                   "iam:DeleteAccessKey",
                   "iam:ListUsers"
               ],
               "Resource": "*"
           }
       ]
   }
   

   PKI Sync

   AWS Certificate Manager

   Use the following custom policy to grant the minimum permissions required by Infisical to sync certificates to AWS Certificate Manager:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowCertificateManagerAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:ListCertificates",
                   "acm:DescribeCertificate",
                   "acm:GetCertificate",
                   "acm:ImportCertificate",
                   "acm:ExportCertificate",
                   "acm:DeleteCertificate",
                   "acm:AddTagsToCertificate",
                   "acm:RemoveTagsFromCertificate",
                   "acm:ListTagsForCertificate"
               ],
               "Resource": "*"
           }
       ]
   }
   

   • ListCertificates: Lists all certificates in the account
   • ImportCertificate: Imports certificates from Infisical into AWS Certificate Manager
   • ExportCertificate: Exports certificates for synchronization
   • DeleteCertificate: Removes certificates that are no longer managed by Infisical
   • DescribeCertificate and GetCertificate: Retrieves certificate details for comparison during sync
   • Tag-related permissions: Manages certificate tags for identification and organization

   AWS Elastic Load Balancer

   Use the following custom policy to grant the minimum permissions required by Infisical to sync certificates to AWS Elastic Load Balancers:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowCertificateManagerAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:ListCertificates",
                   "acm:DescribeCertificate",
                   "acm:ImportCertificate",
                   "acm:DeleteCertificate",
                   "acm:ListTagsForCertificate"
               ],
               "Resource": "*"
           },
           {
               "Sid": "AllowElasticLoadBalancerAccess",
               "Effect": "Allow",
               "Action": [
                   "elasticloadbalancing:DescribeLoadBalancers",
                   "elasticloadbalancing:DescribeListeners",
                   "elasticloadbalancing:DescribeListenerCertificates",
                   "elasticloadbalancing:AddListenerCertificates",
                   "elasticloadbalancing:RemoveListenerCertificates",
                   "elasticloadbalancing:ModifyListener"
               ],
               "Resource": "*"
           }
       ]
   }
   

   ACM Permissions:

   • ListCertificates: Lists all certificates in the account
   • ImportCertificate: Imports certificates from Infisical into AWS Certificate Manager
   • DeleteCertificate: Removes certificates that are no longer managed by Infisical
   • DescribeCertificate: Retrieves certificate details for comparison during sync
   • ListTagsForCertificate: Retrieves certificate tags for identification

   ELB Permissions:

   • DescribeLoadBalancers: Lists available load balancers for selection
   • DescribeListeners: Lists HTTPS/TLS listeners on load balancers
   • DescribeListenerCertificates: Lists certificates attached to listeners
   • AddListenerCertificates: Attaches certificates to listeners
   • RemoveListenerCertificates: Removes certificates from listeners
   • ModifyListener: Sets the default certificate on listeners

   External CA

   AWS Private CA

   Use the following custom policy to grant the minimum permissions required by Infisical to issue certificates via AWS Private CA.

   For a single CA, scope the Resource to that CA’s ARN:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAwsPrivateCAAccess",
               "Effect": "Allow",
               "Action": [
                   "acm-pca:DescribeCertificateAuthority",
                   "acm-pca:GetCertificateAuthorityCertificate",
                   "acm-pca:IssueCertificate",
                   "acm-pca:GetCertificate",
                   "acm-pca:RevokeCertificate"
               ],
               "Resource": "arn:aws:acm-pca:us-east-1:123456789012:certificate-authority/your-ca-id"
           }
       ]
   }
   

   For multiple CAs, list each ARN in the Resource array:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAwsPrivateCAAccess",
               "Effect": "Allow",
               "Action": [
                   "acm-pca:DescribeCertificateAuthority",
                   "acm-pca:GetCertificateAuthorityCertificate",
                   "acm-pca:IssueCertificate",
                   "acm-pca:GetCertificate",
                   "acm-pca:RevokeCertificate"
               ],
               "Resource": [
                   "arn:aws:acm-pca:us-east-1:123456789012:certificate-authority/ca-id-1",
                   "arn:aws:acm-pca:us-west-2:123456789012:certificate-authority/ca-id-2"
               ]
           }
       ]
   }
   

   • DescribeCertificateAuthority: Validates the CA status and configuration
   • GetCertificateAuthorityCertificate: Retrieves the CA certificate and chain
   • IssueCertificate: Issues certificates from the private CA
   • GetCertificate: Retrieves issued certificates
   • RevokeCertificate: Revokes previously issued certificates

   Using a specific CA ARN in Resource is recommended over "*" to follow the principle of least privilege.

   AWS ACM Public CA

   Use the following custom policy to grant the minimum permissions required by Infisical to issue publicly-trusted certificates via AWS Certificate Manager and perform DNS validation through Route 53.

   ACM permissions — RequestCertificate cannot be scoped below "*" because the certificate ARN does not exist until after the call succeeds:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowAcmPublicCaAccess",
               "Effect": "Allow",
               "Action": [
                   "acm:RequestCertificate",
                   "acm:DescribeCertificate",
                   "acm:ExportCertificate",
                   "acm:RenewCertificate",
                   "acm:RevokeCertificate",
                   "acm:ListCertificates"
               ],
               "Resource": "*"
           }
       ]
   }
   

   Route 53 permissions — scope to the hosted zone(s) used for DNS validation:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowRoute53ForAcmValidation",
               "Effect": "Allow",
               "Action": [
                   "route53:GetHostedZone",
                   "route53:ChangeResourceRecordSets"
               ],
               "Resource": "arn:aws:route53:::hostedzone/YOUR_HOSTED_ZONE_ID"
           }
       ]
   }
   

   ACM and Route 53 permissions can live on the same IAM principal, or be split across two separate connections in Infisical.

   ACM Permissions:

   • RequestCertificate: Requests a new public certificate from ACM
   • DescribeCertificate: Retrieves certificate status and DNS validation records
   • ExportCertificate: Exports the issued certificate and private key to Infisical
   • RenewCertificate: Triggers renewal of an existing certificate
   • RevokeCertificate: Revokes a previously issued certificate
   • ListCertificates: Used during connection validation

   Route 53 Permissions:

   • GetHostedZone: Validates the hosted zone during CA setup
   • ChangeResourceRecordSets: Writes the ACM DNS validation CNAME records

   PAM Session Recording

   AWS S3 Bucket

   Use the following custom policy to grant the minimum permissions required by Infisical to store and play back PAM session recordings in your S3 bucket. Replace your-pam-recordings-bucket with the bucket name you configure in Project Settings → Session Recording.

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "AllowPamRecordingBucketAccess",
               "Effect": "Allow",
               "Action": [
                   "s3:PutObject",
                   "s3:GetObject"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket/*"
           },
           {
               "Sid": "AllowPamRecordingBucketTest",
               "Effect": "Allow",
               "Action": [
                   "s3:ListBucket"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket"
           },
           {
               "Sid": "AllowPamRecordingConnectionTestCleanup",
               "Effect": "Allow",
               "Action": [
                   "s3:DeleteObject"
               ],
               "Resource": "arn:aws:s3:::your-pam-recordings-bucket/.test/*"
           }
       ]
   }
   

   If you scoped the recording config to a key prefix (for example pam/prod), update all three Resource ARNs to include the prefix:

   "Resource": "arn:aws:s3:::your-pam-recordings-bucket/pam/prod/*"
   

   "Resource": "arn:aws:s3:::your-pam-recordings-bucket/pam/prod/.test/*"
   

   S3 Permissions:

   • PutObject: Lets the gateway upload encrypted recording chunks via presigned PUT URLs. Also used by the connection test to write a probe object under {prefix}/.test/{uuid}.
   • GetObject: Lets the browser fetch encrypted chunks during playback via presigned GET URLs. Decryption happens locally in the browser; Infisical only ever sees ciphertext.
   • ListBucket: Required by HeadBucket, which Infisical calls during the connection test to confirm the bucket exists and the credentials can reach it.
   • DeleteObject (scoped to .test/*): Used only to clean up the probe object after the connection test. Infisical never deletes recording chunks. Your bucket lifecycle policy owns retention. When using a key prefix, the test object is written under {prefix}/.test/, so the DeleteObject resource must include the prefix.

   Recording chunks are encrypted with a per-session AES-256-GCM key on the gateway before they leave your network, and the session key is wrapped with Infisical’s KMS using session-bound AAD. Even if the bucket policy is wider than the principle of least privilege suggests, the ciphertext is not readable without an authenticated session-key unwrap.

   Bucket CORS Configuration

   During playback the browser fetches encrypted chunks directly from S3 using presigned GET URLs. For this to work the bucket needs a CORS policy that allows requests from your Infisical domain.

   Open the bucket in the AWS console, go to Permissions → Cross-origin resource sharing (CORS), and add:

   [
       {
           "AllowedHeaders": ["*"],
           "AllowedMethods": ["GET"],
           "AllowedOrigins": ["https://app.infisical.com"],
           "ExposeHeaders": [],
           "MaxAgeSeconds": 3600
       }
   ]
   

   Replace https://app.infisical.com with the origin where your Infisical dashboard is served (for example https://eu.infisical.com or http://localhost:8080 during development). You can list multiple origins if needed.

2. Obtain Access Key ID and Secret Access Key

   Retrieve an AWS Access Key ID and a Secret Key for your IAM user in IAM > Users > User > Security credentials > Access keys.

   
3. Setup AWS Connection in Infisical

   Infisical UI

   1. Navigate to the Integrations tab in the desired project, then select App Connections.

      

   2. Select the AWS Connection option.

      

   3. Select the Access Key method option and provide the Access Key ID and Secret Key obtained from the previous step and press Connect to AWS.

      

   4. Your AWS Connection is now available for use.

      

   API

   To create an AWS Connection, make an API request to the Create AWS Connection API endpoint.

   Sample request

   Request

   curl    --request POST \
           --url https://app.infisical.com/api/v1/app-connections/aws \
           --header 'Content-Type: application/json' \
           --data '{
               "name": "my-aws-connection",
               "method": "access-key",
               "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
               "credentials": {
                   "accessKeyId": "...",
                   "secretKey": "..."
               }
           }'
   

   Sample response

   Response

   {
       "appConnection": {
           "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
           "name": "my-aws-connection",
           "projectId": "7ffbb072-2575-495a-b5b0-127f88caef78",
           "version": 123,
           "orgId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
           "createdAt": "2023-11-07T05:31:56Z",
           "updatedAt": "2023-11-07T05:31:56Z",
           "app": "aws",
           "method": "access-key",
           "credentials": {
               "accessKeyId": "..."
           }
       }
   }