AMI.

Installing/Using AWS EC2 AMI

We offer a turnkey solution in the form of a AMI on the AWS Marketplace. Search for "BitFlux" in EC2 -> AMI Catalog -> AWS Marketplace AMIs

Launch the AMI:

  • Select the BitFlux AMI from AWS Marketplace and choose a compatible instance type (e.g., t3a.nano, vendor recommended).
  • Configure the instance as you would a standard Ubuntu Server 24.04 LTS AMI.

Connect to the Instance:

  • Default SSH username: ubuntu.
  • Use SSH to connect: ssh ubuntu@<instance-public-ip>.
  • Ensure your key pair is configured during launch.

Security Group Configuration:

  • Inbound: Open TCP port 22 (SSH) to 0.0.0.0/0 for SSH access. For security, restrict to your trusted IP range (e.g., 192.168.1.0/24).
  • Outbound: At a minimum, allow TCP port 8883 (MQTT over TLS) to 0.0.0.0/0 to enable bitfluxd to connect to the BitFlux cloud service via AWS IoT MQTT. If cloud connectivity is disabled (see below), this is not required.
  • Note: These settings align with standard Ubuntu AMIs, with port 8883 added for BitFlux.

Configure and Use BitFlux Features:

  • The bitfluxd daemon is pre-installed and runs automatically, optimizing RAM usage (30–50% savings).
  • Check bitfluxd status: systemctl status bitfluxd.
  • View logs: journalctl -u bitfluxd.
  • To disable cloud connectivity (e.g., no telemetry), create /etc/bitflux/config/.noconnect by running: sudo touch /etc/bitflux/config/.noconnect.

Monitoring and Health Checks:

  • Monitor RAM usage: cat /proc/meminfo or use free -m.
  • Verify bitfluxd is active: systemctl is-active bitfluxd
  • Use the BitFlux MCP server bitflux_mcp to query telemetry (e.g., memory stats) via the BitFlux cloud service.

Post-Launch Configuration:

  • To update bitfluxd and the bitflux kernel use apt as normal: sudo apt update && sudo apt upgrade
  • For advanced monitoring, integrate with your DevOps tools using the MCP server.