Share

Creating Autodesk Flame Family AMIs

To simplify the deployment to the cloud, Autodesk provides a Rocky Linux AMI. Available from the Flame Family 2025 Linux (ISO, AMI) and DKU page, this AMI comes configured with the DKU, NVIDIA GRID drivers, and all the tools required to use Flame Family in the cloud.

To use the Rocky Linux 9.3 AMI and create from it Flame Family AMIs:

  1. Set up the import privileges for your AWS account. You do this only once.
  2. Upload to your AWS account the Rocky Linux 9.3 AMI file from Autodesk.
  3. Create from the configured Rocky Linux AMI a new, specialized AMI. Create the AMI you need: only the Flame Family one if standalone configuration is your goal, or all three types of AMI if a full collaborative environment is your intent. Once these AMI are created, you can create as many instances of each type as you need.

In this topic you learn how to set up your AMS import privileges and how to upload the Rocky Linux 9.3 AMI. If you've already completed these steps and are ready to create an instance, skip the rest of this topic and go create:

Set Your AWS Account Import Privileges

Prerequisites:

  • A fully configured AWS account, with access to an access key.
  • A local machine running Windows, Linux, or macOS.
  • The AWS CLI installed and configured on your local machine.

If this is the first time you import an image through your AWS account, you must configure your account with the right import privileges.

Note:

You can skip this section if you've already done this in the past.

  1. In your AWS account, create an S3 bucket. You will be using this bucket to transfer AMI and TAR files in later procedures.

  2. On your local machine, create a text file with the following content, and save it as vmimport-trust-policy.json:

    {
 "Version": "2012-10-17",
 "Statement": [
     {
         "Effect": "Allow",
         "Principal": { "Service": "vmie.amazonaws.com" },
         "Action": "sts:AssumeRole",
         "Condition": {
             "StringEquals": {
             "sts:Externalid": "vmimport"
             }
         }
     }
  ]
}

  3. On your local machine, create a text file with the following content, and save it as vmimport-role-policy.json. Make sure to replace <BUCKET_NAME> on lines 16 and 17 with the name of the S3 bucket used in step 1.

    {
 "Version": "2012-10-17",
 "Statement": [
     {
         "Effect": "Allow",
         "Action": [
             "s3:CreateBucket",
             "s3:DeleteBucket",
             "s3:DeleteObject",
             "s3:GetBucketLocation",
             "s3:GetObject",
             "s3:ListBucket",
             "s3:PutObject"
         ],
         "Resource": [
             "arn:aws:s3:::<BUCKET_NAME>",
             "arn:aws:s3:::<BUCKET_NAME>/*"
         ]
     },
     {
         "Effect": "Allow",
         "Action": [
             "s3:ListAllMyBuckets",
             "iam:CreateRole",
             "iam:PutRolePolicy",
             "sts:AssumeRole",
             "ec2:CancelConversionTask",
             "ec2:CancelExportTask",
             "ec2:CreateImage",
             "ec2:CreateInstanceExportTask",
             "ec2:CreateTags",
             "ec2:DeleteTags",
             "ec2:ImportInstance",
             "ec2:ImportVolume",
             "ec2:StartInstances",
             "ec2:StopInstances",
             "ec2:TerminateInstances",
             "ec2:ImportImage",
             "ec2:ImportSnapshot",
             "ec2:CancelImportTask",
             "ec2:ModifySnapshotAttribute",
             "ec2:CopySnapshot",
             "ec2:RegisterImage",
             "ec2:Describe*"
         ],
         "Resource": "*"
     }
 ]
}

  4. Create the required role and policy. On your local machine, run the following commands:

    aws iam create-role --role-name vmimport --assume-role-policy-document file://vmimport-trust-policy.json
aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document file://vmimport-role-policy.json

  5. Give the vmimport role the necessary permissions. In the AWS Web Console, do the following:

    1. In IAM Management Console > Roles > search for vmimport.

    2. Click vmimport.

    3. Under Permissions, click Add Permissions > Attach Policies.

    4. attach the AmazonEC2FullAccess and AmazonS3FullAccess policies

With your account now properly configured, you can now import the Rocky Linux 9.3 AMI file.

Add Autodesk Rocky Linux 9.3 AMI to Your AWS Account

The following procedure explains how to upload and configure the Rocky Linux 9.3 AMI to your AWS account. You will use this base AMI to create the Flame Family, the Burn, and the project server AMIs.

Warning

Do not use aws_configure or store your credentials on the instance, as this would include your credentials in the final AMI.

  1. Download the ZIP file for the Rocky Linux 9.3 AMI file from Autodesk, available in the Amazon Machine image (AMI) section.

  2. Once dowloaded, unzip the adsk-baseami-rockylinux-93-rev001.vmdk.zip file. Unzipped, the AMI file is named adsk-baseami-rockylinux-93-rev001.vmdk.

  3. Upload the file adsk-baseami-rockylinux-93-rev001.vmdk to your S3 bucket. You created the bucket when you configured your account for import.

  4. On your local machine, create a text file with the following content and save it as containers.json. Make sure to edit these placeholders:

    • <DESCRIPTION> with a description of the AMI.

    • <BUCKET_NAME> with the name of your S3 bucket.

    • <IMAGE_FILE_NAME> with the file name of the image you uploaded, such as adsk-baseami-rockylinux-93-rev001.vmdk.

    [
 {
     "Description": "<DESCRIPTION>",
     "Format": "vmdk",
     "UserBucket": {
         "S3Bucket": "<BUCKET_NAME>",
         "S3Key": "<IMAGE_FILE_IMAGE>"
     }
 }
]

  5. Import the VM. On your local machine, enter the following command in a shell. Make sure to edit these placeholders:

    • <YOUR_AWS_REGION> with your AWS region identifier, such as us-east-1.

    • <YOUR_DESCRIPTION> with a description of the image.

    aws ec2 import-image --region <YOUR_AWS_REGION> --description "<YOUR_DESCRIPTION>" --disk-containers file://containers.json --role-name "vmimport"

  6. The import process can take a while; you can monitor its progress with: 

    aws ec2 describe-import-image-tasks

Once the import process completes, the new AMI is available under EC2 > AMIs. Use this AMI to create instances of Flame Family products, Burn nodes, or a project server.

Pages in this section

Was this information helpful?