Aerospike Community Edition

Prerequisites

You need an active Azure subscription, an SSH key pair, and a VNet with a subnet in the target region.

Standard_B2s (2 vCPU / 4 GiB RAM) is a good starting size.

Configure the network security group (NSG) to allow inbound 22/tcp from your management network. No inbound application ports are needed, because you reach Aerospike over an SSH tunnel.

Step 1 - Deploy from the Azure Marketplace

Sign in to the Azure Portal, choose Create a resource, search the Marketplace for Aerospike Community Edition by SecureAnyCloud, and select Create.

On the Basics tab, pick your subscription, resource group, region and size. Under Administrator account, choose SSH public key and paste your key. Under Inbound port rules, allow SSH (22) only.

Select Review + create, then Create.

Step 2 - Deploy from the Azure CLI

Accept the Marketplace terms once, then create the VM:

# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn sac1647283583153:aerospike-ubuntu-24-04:default:latest
az vm create \
  --resource-group <your-rg> \
  --name aerospike \
  --image sac1647283583153:aerospike-ubuntu-24-04:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --ssh-key-values ~/.ssh/id_ed25519.pub \
  --vnet-name <your-vnet> --subnet <your-subnet> \
  --public-ip-sku Standard

Step 3 - Connect to your VM

Connect to the VM over SSH as the administrator user you created:

ssh azureuser@<vm-public-ip>

Step 4 - Confirm Aerospike is installed and running

Check the server version, the service state and the node status:

asd --version systemctl is-active aerospike asinfo -h 127.0.0.1 -v status

The output shows the Community Edition build, an active service and a node that reports ok:

Aerospike Community Edition build 8.1.2.3 active ok

Step 5 - Inspect the node, cluster and namespace

asadm is the Aerospike admin console. Print the network view, which shows one node and a cluster size of 1, and the namespace object counts:

asadm -h 127.0.0.1 -e "info network; info namespace object"

~~~ network ~~~ Node| Node ID| IP| Build|Migrations|Cluster Size|Principal |Uptime localhost:3000|*BB9587F27482200|127.0.0.1:3000|C-8.1.2.3| 0.000 | 1|BB9587F27482200|00:00:48 ~~~ namespace object ~~~ Namespace| Node|Repl Factor|Total Records test |localhost:3000| 1| 0.000

The C- build prefix confirms Community Edition. Cluster Size 1 confirms a healthy single-node cluster, and test is the ready namespace.

Step 6 - Store and retrieve data with aql

aql is the Aerospike query tool. List the namespaces, insert a record into the test namespace, then read it back:

aql -h 127.0.0.1 -c "SHOW NAMESPACES" aql -h 127.0.0.1 -c "INSERT INTO test.demo (PK, user, city) VALUES ('u1', 'ada', 'london')" aql -h 127.0.0.1 -c "SELECT * FROM test.demo WHERE PK='u1'"

+------------+ | namespaces | +------------+ | "test" | +------------+ OK, 1 record affected. +------+-------+----------+ | PK | user | city | +------+-------+----------+ | "u1" | "ada" | "london" | +------+-------+----------+ 1 row in set (0.001 secs)

The record comes back exactly as you stored it, which confirms the database is storing and serving data.

Step 7 - Connect remotely over an SSH tunnel

Aerospike listens on 127.0.0.1:3000 only and is not exposed publicly. This is the secure default, because Community Edition has no authentication.

To reach it from your workstation, open an SSH tunnel. Then point a local Aerospike client, or the tools, at 127.0.0.1:3000:

# On your workstation:
ssh -L 3000:127.0.0.1:3000 azureuser@<vm-public-ip>
# In another terminal, with local aerospike-tools: asinfo -h 127.0.0.1 -p 3000 -v namespaces

test

The per-VM connection details are written on first boot to a root-only file. Read it as root:

sudo cat /root/aerospike-connection.txt

For production remote access without a tunnel, bind Aerospike to a private NIC on a locked-down subnet, or run your client applications inside the same VNet. Never expose port 3000 to the internet, because Community Edition has no authentication or transport encryption.

Maintenance

• Persistence. The test namespace persists to /opt/aerospike/data/test.dat on the dedicated data disk. The keyspace survives reboots, and you can resize the volume independently.
• Configuration. Edit /etc/aerospike/aerospike.conf, for example the namespace storage size, additional namespaces or replication-factor, then run sudo systemctl restart aerospike.
• Health. asinfo -v status returns ok on a healthy node, and asadm -e info shows the cluster and namespace at a glance. Logs are in the journal (journalctl -u aerospike).
• Security patches. Unattended upgrades remain enabled, so the OS continues to receive security updates automatically.
• Upgrading to Enterprise. Community Edition has no authentication, authorization or TLS. For those features, cross-datacenter replication or strong consistency, evaluate Aerospike Enterprise, a separate commercial product from Aerospike.

Source code

Aerospike Community Edition is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). This image ships the stock, unmodified upstream server. All SecureAnyCloud configuration is external, in /etc/aerospike/aerospike.conf.

The corresponding source for the server in this image is available at github.com/aerospike/aerospike-server (release 8.1.2.3).

Support

SecureAnyCloud provides 24/7 expert support for this image. Contact sales@secureanycloud.com.

Aerospike is a trademark of Aerospike, Inc. This image ships Aerospike Community Edition and is provided by SecureAnyCloud; it is not affiliated with or endorsed by Aerospike, Inc.

Deploy on Azure

Launch Aerospike Community Edition on Ubuntu 24.04 LTS on Azure with 24/7 support from SecureAnyCloud.

View this image

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com