Running a Code on Amazon Web Services (AWS)


With the introduction of web licenses, it is now possible to run FLAC3D and 3DEC on a remote, potentially virtual computer (i.e., in the cloud). Web licenses will also be available for future releases of the other Itasca programs. The two most popular cloud services are currently Amazon Web Services (AWS) and Microsoft Azure. This document describes how to set up and use FLAC3D on AWS.

Amazon Elastic Compute Cloud (Amazon EC2) provides scalable computing capacity in the Amazon Web Services (AWS) cloud. You can use Amazon EC2 to launch as many or as few virtual computers as you need. Amazon EC2 enables you to scale up or down to handle changes in requirements, reducing your need to forecast computing needs. More information on Amazon EC2 is available on Amazon’s web site.

The content of this document is broken into the following major topics.

Set Up Accounts


See Tasks that require root user credentials on the Amazon web site for details on Root account functions.

AWS assumes that the resources will be used by a company with more than one person. Therefore, it is best to first set up a Root account and then one or more sub-accounts called IAM s (Identity and Access Management). Operations for setting up FLAC3D to run on AWS can be done with an IAM account. Viewing billing information and other account-holder administrative tasks require root access.

Root Account

Follow these steps to set up a Root account.

  1. Open

  2. Follow the online instructions. You will need to enter credit card information to sign up.

IAM Account

With a Root account established, it is recommended to set up an IAM account per user. A company with several employees using AWS will likely set up multiple IAM accounts under one Root. The following instructions describe how to set up a first IAM account.

  1. If not already logged in, go, click Sign In to the Console and log in as the Root user.

  2. Go to the IAM Console (

  3. In the navigation pane, under Access management, choose Users and then choose Add user.

  4. For User Name, enter Administrator.

  5. Select the check box next to AWS Management Console access. Then select Custom password, and then enter a new password for the account in the text box.

  6. (Optional) By default, AWS requires the new user to create a new password when first signing in. Clear the check box next to Require password reset to allow the new user to reset their password after they sign in.

  7. Choose Next: Permissions.

  8. Under Set permissions, choose Add user to group.

  9. Choose Create group.

  10. In the Create group dialog box, for Group name enter Administrators.

  11. Choose Filter policies, and then select AWS managed - job function to filter the table contents.

  12. In the policy list, select the check box for Administrator Access. Then choose Create group.

  13. Back in the list of groups, select the check box for your new group. If necessary, choose Refresh to see the group in the list.

  14. Choose Next: Tags.

  15. (Optional) Add metadata to the user by attaching tags as key-value pairs. For more information about using tags in IAM, see Tagging IAM Entities in the IAM User Guide.

  16. Choose Next: Review to see the list of group memberships to be added to the new user. When ready to proceed, choose Create user.

  17. The Add User screen is shown with a link for logging in with the IAM credentials. Write down this link or email it by clicking the Send email link.

  18. Now click the Sign In to the Console button, select the drop down menu next to the root name, and Sign Out.

  19. Click the link from Step 17 and enter the IAM username (“Administrator”) and password.

Key Pairs

AWS uses public-key cryptography to secure the login information. The user specifies the name of the key pair when launching an instance, then provides the private key to obtain the administrator password for the current Windows instance to allow logging in via Windows Remote Desktop (RDP). Set up a key pair following these steps. This task is performed once only.

  1. Sign in to the IAM user account by clicking on the link from the previous section, or else go to, click Sign In to the Console and log in as an IAM user.

  2. Open the Amazon EC2 console at

  3. In the navigation pane under Network & Security, choose Key Pairs.

  4. Choose Create key pair.

  5. For Name, enter a descriptive name for the key pair. Amazon EC2 associates the public key with the name specified as the key name. A key name can include up to 255 ASCII characters. It cannot include leading or trailing spaces.


    By default, this is set to PuTTY format. If key pair with a .ppk extension is accidentally created, see this article to convert it to a .pem file.

  6. For File format, choose the format in which to save the private key. To save the private key in a format that can be used with OpenSSH, choose pem.

  7. Choose Create key pair.

  8. The private key file is automatically downloaded by the browser. The base file name is the name specified as the name of the key pair, and the file name extension is determined by the file format chosen. Save the private key file in a safe place.

Security Groups (Optional)

Set up a Security Group that restricts access to instances to given IP addresses. To create a security group with the least privilege, follow these steps.

  1. Open the Amazon EC2 console at

  2. In the navigation pane under Network & Security, choose Security Groups.

  3. Choose Create security group.

  4. In the Basic details section, do the following.

    1. Enter a name for the new security group and a description. Use a name that is easy to remember, such as the account user name, followed by _SG_, plus the Region name. For example, me_SG_uswest2.

    2. In the VPC list, select the default VPC for the Region.

  5. In the Inbound rules section, create the following rules (choose Add rule for each new rule).

    1. Choose HTTP from the Type list, and make sure that Source is set to Anywhere (

    2. Choose HTTPS from the Type list, and make sure that Source is set to Anywhere (

    3. Choose RDP from the Type list. In the Source box, choose My IP to automatically populate the field with the public IPv4 address of the local computer. (On a network that allocates addresses in a range, specify the entire range, such as

  6. Choose Create security group.

For more information, see Amazon EC2 security groups for Windows instances.


Once set up, it is possible to launch one or more instances. An instance is simply a remote computer with Windows installed that can be accessed with Windows Remote Desktop (RDP).

Launching An Instance

  1. In the EC2 Console, go to Instances – Instances. Click the button to Launch Instance.

  2. Select Microsoft Windows Server 2019 Base.

    1. If a machine image is set up (see the section below, Amazon Machine Images (AMI)), click on My AMIs to select the existing image.

  3. Choose an Instance Type (see the table i Recommended Instance Types below for reference). Click Next: Configure Instance Details.

  4. Configure Instance Details. Leave these as default values. Click Next: Add Storage.

  5. Add Storage. This is done to increase the storage capacity of the root drive. It is also possible to add one or more additional virtual drives (see EBS Storage). Click Next: Add Tags.

  6. Add Tags. This is optional and can be skipped. Click Next: Configure Security Group.

  7. Configure Security Group. Choose Select an existing security group. For the security group, choose the security group set up in the steps above to restrict the users of this instance to certain IP addresses. Otherwise, just choose Default. Click Review and Launch. Click Launch.

  8. Choose the key pair from the dropdown menu and click the box to acknowledge access to the pem file. Click Launch Instances.

  9. On the Launch Status screen, click the View Instances button at the bottom-right corner.

  10. The instance is now listed in a table. When the Instance State is running, and the Status Checks say 2/2 checks …, select the instance and click the Connect button.

  1. Click Get Password. Click Choose File and navigate to the key file (.pem extension). Click Decrypt password. When the password appears, click just to the right of it to copy the password to the clipboard.

  2. Click Download Remote Desktop File. Open the file, click Connect, paste in the password and click OK. Click Yes to ignore the certificate warning.

More detailed instructions are on Amazon’s web site.

Stopping An Instance

Closing the Remote Desktop session will not stop the instance. To terminate the instance, go to the console, click on the running instance, and choose Actions -> Instance State -> Terminate. To keep the instance for later, but not incur charges, choose Stop instead of Terminate.


Short term storage can use the root drive that is automatically set up when the instance is created. This drive disappears when the instance is terminated. But to use the same data across instances, EBS Storage (medium term storage of moderate sized files) or S3 storage (longer term storage of larger files) will be desirable. Details of these two options are described below.

EBS Storage

Amazon Elastic Block Store (Amazon EBS) provides storage volumes for use with EC2 instances. These are essentially like hard drives that can persist independently of an instance, so the same EBS for different instances (in the same region) may be used.

Initialize EBS Storage


See Amazon documentation for instructions on creating an EBS volume outside of creating an instance. Make sure to choose the same Availability Zone as the instance. It will not necessarily be the default.

The easiest way to create a volume is during creation of a new instance (see “Launching An Instance” above) . After starting the instance, follow these steps to use the volume.

  1. On the Windows logo, right-click and choose Disk Management.

  2. The program should now ask whether to initialize Disk 1. Click OK. If this does not occur, right-click in the left panel for Disk 1 and select Initialize.

  3. The disk should automatically be online as shown in the left panel. If this is not the case, right-click on the left panel and select Online.

  4. Now, right-click on the right panel and select New Simple Volume… . Complete the wizard.


Mount Storage Volume On A Different Instance

Once a volume is created as above, it can be mounted on a different instance. This is an easy way to share data between instances (note that it cannot be mounted on two instances at the same time).

To mount an existing EBS volume on a new instance, follow these steps.

  1. In the EC2 console, in the navigation pane, choose Elastic Block Store, Volumes.

  2. Select an available volume. If the volume is already mounted to an instance, choose Actions, Detach Volume and then Actions, Attach Volume. If not, choose Actions, Attach Volume.

  3. For Instance, start typing the name or ID of the instance. Select the instance from the list of options (only instances that are in the same Availability Zone as the volume are displayed).

  4. For Device, keep the suggested device name.

  5. Choose Attach.

  6. Connect to the current instance and bring the volume online as described above (WARNING: Do not initialize the volume if it has data on it).

Detaching Storage Volume

If the instance is to be terminated, detach the EBS volume. Follow these steps before logging out of the current instance.

  1. While logged in, start the Disk Management utility.

  2. Right-click the disk (for example, right-click Disk 1) and then choose Offline. Wait for the disk status to change to Offline before opening the Amazon EC2 console.

  3. In the EC2 console, in the navigation pane, choose Volumes.

  4. Select a volume and choose Actions, Detach Volume. Click Yes, Detach.


A detached volume persists after logging out. Charges continue to accrue for use of the volume until it is deleted. Persistent EBS storage volumes are useful for short term storage during a project. For long-term storage, moving data to S3 storage is recommended (see S3 below). After moving, the EBS volume may be deleted.

Deleting EBS Storage Volume

To delete the volume, In the EC2 console, in the navigation pane, choose Volumes. Select a volume and choose Actions, Delete Volume. Click Yes, Delete.

S3 Storage

Amazon Simple Storage Service (Amazon S3) is a storage service that costs significantly less than EBS (see i Storage Pricing below). This is a viable method for storing large files (such as FLAC3D save files) for long time periods.

On creation an AWS account is automatically signed up for all services in AWS, including Amazon S3. However, charges only accrue for services used.

It is possible to move files into and out of S3 storage using the S3 console. Instructions can be found on the Amazon web site. There are also many third-party programs that will make data transfer to S3 much easier. We recommend the Cyberduck program. Instructions for setting up and using Cyberduck are given below.

Access Key

To use Cyberduck, an AWS account access key is needed. Access keys consist of two parts: an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access key (for example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY). Like a user name and password, both the access key ID and secret access key are required to authenticate requests. Manage access keys with the same vigilance as is used for username and password.

Follow these steps to get the access key.

  1. Log in as an IAM user (see above).

  2. Go to the IAM Console.

  3. In the navigation bar on the upper right, choose the user name (Administrator), then choose My Security Credentials.

  4. Under Access keys for CLI, SDK, & API access, choose Create Access Key.

  5. Record the access key and the secret access key. The access key may be (re)retrieved later. But this is the only time the secret key may be obtained.

  6. To see the access key in the future, go to the IAM Console. Under Access management on the left, select Users. Select the name (Administrator) and then select Security credentials.

Find more information on access keys on the Amazon web site.

Using Cyberduck To Access S3 Storage

To use Cyberduck, follow these steps.

  1. Download the Windows version from the Cyberduck website. Install it on the local computer.

  2. Open the Cyberduck program and click the Open Connection button.

  3. From the drop-down menu, select Amazon S3.

  4. Enter the Access Key and Secret Access Key. Click Connect.


    Folders in S3 are known as buckets. Bucket names must be universally unique, therefore the operation might fail if the name is already taken by someone else (e.g., it is safe to assume any common name like “media” or “images” is unavailable).

  5. Click Action – Create Folder. Enter the name of a folder and select the appropriate region. Click Create.

  6. Click the Upload button to upload file and folders. Click Action – Download to download files and folders.

  7. Start an AWS EC2 instance and follow the same steps except install it on the remote computer.

Storage Pricing

General Purpose SSD (gp2) EBS Volumes are $0.10 per GB per month, charged per hour. Standard S3 storage is $0.023/Gb per month. See for more information.

Full pricing details for EBS storage and S3 storage are available on the Amazon web site.

Amazon Machine Images (AMI)

Once software is installed and projects set up, it may be desirable to make an image of the instance. Down the line the image can be restarted rather than a new instance, which eliminates the need to install software and drives each time. An image may include one or more EBS volumes.

Creating An AMI

  1. To create an AMI, start with an instance and install all necessary software (e.g., FLAC3D, Cyberduck, etc.) and add EBS storage drives as needed.

  2. IMPORTANT – by default, when creating an AMI from an instance, each new instance created from this AMI will require the same Administrator password as the original instance. To prevent this from happening, follow these steps:

    1. In the open instance, in the Windows search bar, search for EC2Launch.

    2. Under Administrator Password, select Random.

    3. Click Shutdown with Sysprep and wait for the instance to become Stopped.

  3. From the EC2 console, choose Instances and select the instance. When the Instance State shows Stopped, choose Actions, Image, and Create Image.

  4. Specify a unique name for the image and an optional description (up to 255 characters).

  5. Click Create Image. By default, Amazon EC2 shuts down the instance, takes snapshots of any attached volumes, creates and registers the AMI, and then reboots the instance. Choose No reboot to prevent the instance from shutting down. Warning: When choosing No reboot, AWS cannot guarantee the file system integrity of the created image.

  6. While the AMI is being created, choose AMIs in the navigation pane to view its status (change the dropdown menu to show Owned by me). Initially, this is pending. After a few minutes, the status should change to available.

To launch a new instance based on the AMI, in the console go to Images – AMIs, select the AMI, and choose Launch.

Note there is a small charge to maintain an AMI. To delete an AMI, in the Console go to Images – AMIs, elect the AMI and choose Actions – Deregister.

For more details on creating and using AMIs see the Amazon web site.

Costs And Billing

To view current incurred costs, log in as the Root user. To view accumulated spending, click on the username at the top of the console page and select My Billing Dashboard.

Table 1: Recommended Instance Types

VM Type



FLAC3D Speed

3DEC speed*



















































$ 4.25







$ 8.51







$ 17.04







$ 33.98






$ 76.47






$ 101.95






$ 152.93







$ 13.34







$ 26.69







$ 40.03






$ 80.06






$ 160.13

*3DEC speed depends on number of zones, contacts, and subcontacts. Numbers listed are for a specific test.

Costs reported above correct as of September 30, 2020. Visit the Amazon web site to get current pricing information.

Note that new AWS accounts may start with CPU limits. See the current limits by going to the EC2 console, selecting Limits from the left panel, and then clicking Calculate CPU Limits. One can also request a limit increase from the calculator.