Comet MLOps Platform on AWS

Overview¶

The Comet MLOps Platform on AWS Marketplace provides our fastest, simplest deployment for self-managed infrastructure and is free for a single user. If you haven't already, get your free license token here.

The AMI includes the following configuration:

• Comet already running - no installation required
• Ubuntu 22.04 LTS base image
• 1TB storage disk, with enough space for an all-in-one deployment

Setup ¶

EC2 Instance Launch¶

The EC2 instance can be launched either directly from the marketplace subscription or via the EC2 console; the subscription launch is simpler, whereas the EC2 console can provide more visibility on the configuration parameters to select. Considerations for the important instance configuration items can be found below.

Instance type:

For optimal performance and reliability, we recommend using at least the EC2 instance type m6i.4xlarge, which is the default selection from the marketplace product. Several other types are also available to meet the needs of lower cost or higher performance on a larger workload; while m5 instance types are available, m6i types are recommended:

• t3.xlarge
• t3.2xlarge
• m6i.xlarge
• m6i.2xlarge
• m6i.8xlarge
• m6i.12xlarge
• m6i.16xlarge

Networking:

The AMI product has specified a recommended set of security group rules for allowing the necessary traffic to the instance. These by default allow from anywhere (0.0.0.0/0) on the following ports:

• HTTP/80
• HTTPS/443
• SSH/22

The marketplace subscription launch includes an option to create a new security group with these rules for the instance. If launching directly from the EC2 console, be sure to configure a security group that will allow the HTTP/HTTPS traffic to Comet, as well as SSH connectivity to the instance, unless it is configured for access via another mechanism such as SSM. More on connecting to the instance can be found in the SSH key section below.

In the simplest configuration, Comet can be accessed over the network on the IP address of the EC2 instance. Keep this in mind when selecting a subnet for your instance, as it will determine whether or not the instance can receive a public IP and be accessed over the internet, or must be accessed only from within the VPC in which it resides.

Another common and supported networking configuration for Comet is to use a load balancer in front of the EC2 instance. On AWS infrastructure, Comet requires an Application Load Balancer.

SSH key:

Unless using another mechanism for remote access to your EC2 instance, be sure to specify an SSH key at instance launch, and be sure that you have access to the key file. If the instance is launched without a key or with a key that you do not have access to, you may be left with no way to connect to the instance.

Comet configuration ¶

When connecting to your instance via SSH, be sure to use the username ubuntu in the command. For example:

ssh -i "yourkey.pem" ubuntu@ec2-X-X-X-X.compute-1.amazonaws.com

License token:

The newly running installation of Comet will not have a license token and will not be accessible until it is initialized. To configure Comet with your license token, run the following, with <licensetoken> replaced by your token string:

cometctl init --license-token <licensetoken>

Configuration update:

The last required step in the Comet setup is to run a configuration update command via the cometctl utility:

cometctl aio update-config

The configuration file contains a variable called comet_base_domain, which should be set with the IP address of the EC2 instance or a DNS hostname that will resolve to the instance IP address.

More information can be found for the available cometctl commands by running with the help flag:

cometctl -h

cometctl aio -h

Next steps¶

See verify installation for getting started with the Comet deployment.