Skip to content
LibreChat AI Platform & Data · LibreChat 0.8.8 Launch on AWS

Operations

This page covers the LibreChat service, what to back up, moving to another image, and support.

Security model

  • Loopback UI. LibreChat listens on 127.0.0.1:3080. You open it through Session Manager port forwarding. No inbound application rule is required.
  • Your database. Conversation state is in the MongoDB deployment you manage. The connection uses TLS with certificate and hostname verification, and SCRAM-SHA-256. This image does not ship a database server or a database account.
  • Owner account. You create the first owner after launch. Public registration and social login are disabled.
  • Instance identity. First boot creates the encryption and session identity once. /etc/librechat holds the original identity.env. Losing the encryption keys can make stored provider credentials unreadable.
  • Service user. The application runs as the non-login librechat user. Program files are read-only.
  • No static AWS keys. Bedrock calls use the instance role.

Service

sudo systemctl status librechat.service --no-pager
sudo journalctl -u librechat.service -n 100 --no-pager
sudo systemctl restart librechat.service

Read logs in your own session. Remove credentials and customer data before you share them. Keep the data in place while you resolve a failure.

An unconfigured status before the first sudo sushi-librechat configure is expected. After a restart, reread a verified turn with the command in Check a saved conversation. That reread does not send another model request.

Backups

Conversation state lives in your external MongoDB database. Take an application-consistent backup of that database. On the instance, back up these together with it:

  • /etc/librechat, including the original identity.env
  • /var/lib/librechat (uploads, images, application data, and logs)

Restore those components together and keep the existing identity. Replacing the identity, or restoring the database without the original encryption keys, can make stored provider credentials unreadable.

Also keep ~/librechat-results if you still need the saved-chat receipts.

Updates

A new Marketplace version is a new instance. Launch it, restore /etc/librechat and /var/lib/librechat together with a consistent copy of the same external database, and preserve the existing identity. Sign in and, if you have an earlier receipt, run the prior-result check before you treat the replacement as ready.

Do not delete /etc/librechat to force a new identity.

Support

Software Sushi provides AMI packaging and setup guidance. Email info@softwaresushi.com for installation questions. Include the Marketplace version, the Region, and what you ran. Omit the MongoDB URI, the owner password, and conversation text.

The published getting-started page offers a full refund of software charges for the first 48 hours after billing starts, if the product does not perform as described. To request it, email the same address with the EC2 instance ID and a description of the issue. EC2, EBS, and data transfer charges are outside that refund. External MongoDB and Bedrock charges are also separate from the software rate.

The software rate on the listing is USD 0.03 per running instance-hour. Support beyond installation questions needs a separate agreement. Upstream LibreChat support is not included. The offer uses the AWS Marketplace Standard EULA.

Last updated November 1, 2026 · Suggest an improvement