3.1.2. AWS Requirements

3.1.2.1. Requirements

Here are the requirements for running Omniverse Isaac Sim on Amazon Web Services (AWS):

  1. An AWS account that is able to launch an EC2 instance with RTX GPU support.

  2. An AWS EC2 Instance with the following specifications:

    • Instance Type: g4dn.2xlarge or higher

    • AMI: IsaacSim-Ubuntu-18.04-GPU-2022-05-31

3.1.2.2. Setup

Follow these steps below to launch an AWS EC2 instance:

  1. Create your Key Pair PEM file by following the eight steps in this Key Pair Guide.

    Note

    Follow these steps to prevent permission errors when trying to SSH into the AWS instance:

    • On Linux, remember to use chmod 400 yourkey.pem as instructed in the link above.

    • On Windows, right-click the yourkey.pem file and select Properties:

      1. Go to the Security tab and click Advanced.

      2. Click Disable inheritance.

      3. Set ownership of the file to the current user and give full permissions to only that user.

  2. From your AWS EC2 Console, click Launch Instance, select Community AMIs, search for “IsaacSim-Ubuntu-18.04-GPU-2022-05-31”, and select it.

    Note

    This AMI may not be visible to Hong Kong, Africa Cape Town, Middle East Bahrain, and Milan zones.

    Select AMI
  3. Scroll down and pick a GPU instance (g4dn.2xlarge or higher). Click Next: Configure Instance Details at the bottom right corner.

    ../_images/isaac_main_gpu_instance.png
  4. Make sure Auto-assign Public IP is enabled.

    ../_images/isaac_main_auto_assign_ip.png
  5. Click Add Storage at the bottom right. Set the Root volume size to 100GB or more.

    Note

    Isaac Sim can operate on an Instance with 30GB, but you may run out of space when running the Python Samples.

    ../_images/isaac_main_storage.png
  6. Click Next: Add Tags, then Next: Configure Security Group. Click Add Rule, select All traffic and My IP so the Livestream Clients and Visual Studio Code can see the IP address for this instance. If you are running a Livestream Client on another workstation, select the Custom source and enter the external IP address of that workstation.

    ../_images/isaac_main_all_traffic.png
  7. Click Review and Launch, then Launch. Point to your existing PEM key or create a new PEM key; creating a new PEM key will save the key in your browser Download folder). Select Acknowledge.

    Click Launch Instance, which will produce a link (e.g. i-0edc9523b2fff2e44). Click the instance link.

    ../_images/isaac_main_launch.png

    Note

    If you see “You have requested more vCPU capacity than your current vCPU limit”, you might need to stop your running instances to free up vCPU usage and try again.

  8. Click Connect next to the Launch Instance button.

    ../_images/isaac_main_connect_aws.png
  9. Follow these steps to SSH into the AWS instance:

    1. As shown above, on Linux or Windows, run this command from where your PEM key folder is. Replace ubuntu@ec2-52-53-177-94.us-west-1.compute.amazonaws.com with your instance:

    $ ssh -i "yourkey.pem" ubuntu@ec2-52-53-177-94.us-west-1.compute.amazonaws.com
    
    1. On Windows, you can also use Putty to SSH:

      Convert your PEM key to a Putty key. See Connecting to Your Linux Instance from Windows Using PuTTY for more details.

      Put your instance name above in the host name:

      ../_images/isaac_main_host_name_putty.png

      Select SSH/Auth, point Browse to your converted Putty key, then click Open and Yes. You should be able to SSH into the AWS instance now.

      ../_images/isaac_main_auth.png
  10. Proceed to Container Deployment.