Creating AWS Identity and Access Management (IAM) Policies

In AWS, IAM files are used to create policies that control access to resources in a VPC. IAM roles allow EC2 instances to make API requests without the need to use or distribute AWS credentials (accessKey and secretAccessKey).

For more information about IAM, see the following topics in the AWS documentation:
Use the AWS Policy Generator to create the IAM file, keeping in mind the following requirements:
  • For EC2, Altus Director requires permissions for the following methods:
    • CreateTags
    • DescribeAvailabilityZones
    • DescribeImages
    • DescribeInstanceStatus
    • DescribeInstances
    • DescribeKeyPairs
    • DescribePlacementGroups
    • DescribeRegions
    • DescribeSecurityGroups
    • DescribeNetworkAcls
    • DescribeSubnets
    • DescribeInstanceAttribute
    • RunInstances
    • TerminateInstances
  • To use SSH host key retrieval type with the PROVIDER option, the following additional EC2 permission is required:
    • GetConsoleOutput
    For more information, see SSH Host Key Retrieval and Verification.
  • To use EBS volumes, the following additional EC2 permissions are required:
    • CreateVolume
    • DescribeVolumes
    • AttachVolume
    • DeleteVolume
    • ModifyInstanceAttribute
  • To use the importKeyPairIfMissing property, Altus Director requires the following EC2 permission:
    • ImportKeyPair
  • To use spot instances, the following additional EC2 permissions are required:
    • RequestSpotInstances
    • CancelSpotInstanceRequests
    • DescribeSpotInstanceRequests
  • When working with encrypted EBS volumes (including AMIs with encrypted volumes) that use a custom key stored in KMS, Altus Director also requires the following KMS permissions:
    • DescribeKey
    • CreateGrant
    • ReEncrypt
    • GenerateDataKey
  • To validate the templates used for EC2 instance creation, Altus Director requires permissions for the following IAM methods:
    • GetInstanceProfile
    • PassRole
  • To create RDS database servers for persistence on demand, Altus Director requires permissions for the following methods:
    • CreateDBInstance
    • DeleteDBInstance
    • DescribeDBInstances
    • DescribeDBEngineVersions
    • DescribeDBSubnetGroups

Example IAM Policy

The following example IAM policy shows the format to use with Altus Director. Your Amazon Resource Name (ARN) will be different. For more information on ARNs, see Amazon Resource Names (ARNs) and AWS Service Namespaces in the AWS documentation.

    "Version": "2012-10-17",
    "Statement": [
            "Sid": "directorEc2",
            "Effect": "Allow",
            "Action": [
            "Resource": "*"
            "Sid": "directorKms",
            "Effect": "Allow",
            "Action": [
            "Resource": "*"
            "Sid": "directorIam",
            "Effect": "Allow",
            "Action": [
            "Resource": "*"
            "Sid": "directorRds",
            "Effect": "Allow",
            "Action": [
            "Resource": "*"