Overview

Elastic Stack turns logs and metrics into searchable, visual, and actionable data. On Cloudzy, Elasticsearch, Kibana, Logstash, and Filebeat arrive preinstalled on Ubuntu Server 24.04 with sane defaults, so you can start ingesting data right away. Dedicated EPYC vCPUs, DDR5 RAM, pure NVMe storage, and a 10 Gbps uplink keep indexing fast and dashboards snappy. Flexible hourly billing supports quick staging clusters and scale testing, while long-term plans fit production rollouts.

Description

This image ships the full Elastic Stack for search, analytics, and log processing. Services are managed by systemd and prewired to talk to each other out of the box. Your initial superuser is created on first boot, and the credential is saved on the server for safe retrieval.

• Services included Elasticsearch, Kibana, Logstash, Filebeat

• Credentials: username elastic, password stored at /root/.cloudzy-creds

• Key ports: Kibana 5601, Elasticsearch HTTP 9200, Elasticsearch internal transport 127.0.0.1:9300

• Important directories:
  • Config: /etc/{service}/

  • Data: /var/lib/{service}/

  • Logs: /var/log/{service}/

  • Binaries: /usr/share/{service}/bin/

  • Plugins (Elasticsearch and Kibana): /usr/share/{elasticsearch|kibana}/plugins/

Access the Web Interface

Here is the day one path from power on to your first dashboard. Use the IP directly for initial access, then add DNS later if you prefer.

1. Kibana
   Open your browser to http://<server-ip>:5601. Log in with elastic and the password in /root/.cloudzy-creds. From the Kibana home, add your first data view and explore Discover or Dashboards.

2. Elasticsearch API
   Test the node with:

Cluster transport runs on 127.0.0.1:9300 for local interprocess communication.

1. Beats and Logstash
   Filebeat and Logstash run as services. Point Filebeat at your app logs and pipe structured inputs through Logstash pipelines as needed.

Useful service commands:

Advanced Features

This is the practical mix that keeps indexing steady, queries quick, and upgrades safe. It fits small single-node analytics and scales up vertically for heavier loads without reimaging.

• Dedicated vCPUs and DDR5 RAM for consistent query concurrency and faster shard merges

• Pure NVMe storage for high IOPS on segments, translogs, and snapshots

• 10 Gbps network port for bursty ingest and multi-user Kibana sessions

• Snapshots and fast rollback via panel snapshots for safer upgrades and plugin trials

• Hourly billing for throwaway staging nodes; keep only what you use
  A single reboot applies any resize; no data migration, no DNS edits.

Ease of Use

Cloudzy’s dashboard handles power, resizing, snapshots, and region moves. You can deploy in minutes, connect to Kibana on port 5601, and start shipping logs. Use the static IP immediately or attach a domain later once you are satisfied with the setup.

Performance Focus

Better telemetry helps real sites load faster. By collecting Nginx or application logs through Filebeat and visualizing traffic patterns in Kibana, you can spot slow endpoints and reduce TTFB on public pages. Fast NVMe I/O plus a 10 Gbps uplink keeps ingest smooth during traffic spikes, so your analytics view stays responsive while you tune Core Web Vitals.

Full Website Control

You have root access for cluster tuning, firewall rules, and plugin management. KVM isolation keeps your kernel and processes separate from neighbor workloads, and dedicated IPs reduce CAPTCHA friction for admin UIs.

• Manage services with systemctl and inspect logs under /var/log/{service}/

• Store configs in /etc/{service}/ and keep data under /var/lib/{service}/

• Install plugins by placing them in /usr/share/{elasticsearch|kibana}/plugins/ then restarting the service

• Secure access by allowing only your IP to 5601 and 9200 or by placing an authenticating reverse proxy in front

Powerful Tools

You get the core stack out of the box, plus clean hooks for hardening, monitoring, and backups. Everything is tuned for predictable memory and disk usage on this image.

• Preinstalled: Elasticsearch, Kibana, Logstash, Filebeat on Ubuntu Server 24.04

• Optional hardening and monitoring add ons such as Fail2Ban and node_exporter

• Snapshot recipes to object storage like S3 or GCS

• Cron templates for index lifecycle maintenance and log pruning

• Example Logstash pipelines for common inputs

Global Reach

Pick the closest data center for faster ingest and quicker dashboards. Cloudzy operates multiple points of presence across three continents.

• North America: New York City, Dallas, Miami, Utah, Las Vegas

• Europe: London, Amsterdam, Frankfurt, Zurich

• Asia Pacific: Singapore

All locations offer a 10 Gbps uplink and a 99.95 percent uptime SLA. The only variable is distance to your users or data sources.

Application Details

Version: Not Specified

OS: Ubuntu Server 24.04

Minimum RAM: 8 GB

IP Types: IPv6, IPv4

Deploy Elastic Stack Now: spin up a ready-to-use ELK plus Filebeat node and start ingesting data in minutes.

Important: Configuration & Domain Responsibilities

You get full SSH/root access on every OCA. That power also means your changes can break the app. Please read this before tweaking configs.

• You manage the domain. We don’t sell or host domains/DNS. If the app needs a domain, you must point your domain to the server (A/AAAA/CNAME and MX/TXT if relevant). SSL issuance and many dashboards depend on this being correct.

• Changing the domain/hostname after installation isn’t trivial. Many OCAs write the domain into configs (.env, reverse proxy, app URLs). If you change it, also update:
  • Reverse proxy (Nginx/Caddy) and TLS certificates

  • App “external URL”/base URL and callback/webhook URLs

  • Any hard-coded links in the app or add-ons

• Credentials matter. Renaming the default admin, rotating passwords, or changing service ports without updating the app config can lock you out or stop services. Keep credentials safe and in sync across the app, proxy, and any integrations.

• Nameserver changes can cause downtime. Moving your domain to new nameservers or editing NS records triggers propagation delays. Plan changes, lower TTL ahead of time, and verify A/AAAA records before switching.

• Firewall/port edits can break access. If you change SSH, HTTP/HTTPS, RDP, or app ports, update firewalls (UFW/CSF/security groups) and reverse-proxy rules accordingly.

• Email (SMTP) ports are restricted by default. Outbound mail ports (e.g., 25/465/587) may be closed to prevent abuse. If your OCA must send email, request SMTP access. from support or use a transactional email provider (SendGrid/Mailgun/SES) via API or approved SMTP.

• Email & allowlists. If the app sends mail or receives webhooks, changing IPs/hostnames may affect deliverability or allowlists. Update SPF/DKIM/DMARC and any IP allowlists.

• Before any big change: take a snapshot. Use the panel’s snapshot/backup first. If a plugin, update, or config edit backfires, you can roll back in minutes.

• Support scope. We provide the server and the preinstalled OCA image. Ongoing application-level configuration (domains, DNS, app settings, plugins, custom code) is the user’s responsibility.

Quick rule of thumb: if you touch domain, ports, passwords, hostnames, or proxy/SSL configs, expect to update the app’s settings too, and snapshot first.