Deploy NomadicML DriveMonitor within your own AWS Virtual Private Cloud (VPC).
012345678901
) that uniquely identifies an AWS account. You can find this in the AWS Management Console, typically in the top-right corner under your account name/menu.
The image above is illustrative. Your AWS console might look slightly different.customer.app.nomadicml.com
, yourcompany.drivemonitor-internal.com
) through which you will access your self-hosted DriveMonitor instance.customer.app.nomadicml.com
f78406j.app.nomadicml.com
abcde.app.nomadicml.com
yourproject-firebase-adminsdk-xxxxx-xxxxxxxxx.json
) will be downloaded.DriveMonitor-VPC-Server
.g6e.12xlarge
, p4d.24xlarge
, or similar high-end GPU instances. Please consult current AWS instance offerings for the best fit..pem
file will be downloaded. Store this file securely..pem
file:
0.0.0.0/0
if publicly accessible – secure appropriately)..pem
key file to SSH into the instance. The default username for Ubuntu-based AMIs is typically ubuntu
. If NomadicML provided a different default username for the AMI, please use that.
.env
file.env.template
) should be present. Copy it to create your environment configuration file.
.env
file using a terminal text editor like nano
or vim
:
DRIVEMONITOR_VPC_DOMAIN
: The domain you decided on in the “Prerequisites” section (e.g., customer.app.nomadicml.com
).FIREBASE_SERVICE_ACCOUNT_KEY_JSON_CONTENT
: Paste the entire content of the JSON file you downloaded from Firebase here (the one from “Generate new private key”). It should be a single line of JSON string. Alternatively, if the AMI is set up to read from a file path, you might securely transfer your Firebase JSON key file to the server (e.g., using scp
) and reference its path here (e.g., GOOGLE_APPLICATION_CREDENTIALS=/path/to/your-firebase-key.json
). Follow instructions provided with the AMI..env.template
or by NomadicML.nano
, press Ctrl+X
, then Y
, then Enter
).
make start
.
make
is not used, there might be a specific script:
tail -f /var/log/drivemonitor.log
or docker-compose logs -f
).
DRIVEMONITOR_VPC_DOMAIN
to point to the Elastic IP of your EC2 instance, you should be able to access your self-hosted DriveMonitor instance by navigating to your configured domain in a web browser (e.g., http://customer.app.nomadicml.com
or https://...
if SSL is configured).
That’s it! You are now ready to use DriveMonitor.
.pem
Key Security: Keep your .pem
key file secure. Anyone with this key can access your EC2 instance.