Managed Add-ons

Deploy and manage fully-managed database and service instances with automated backups, scaling, and monitoring.

Supported Add-on Types

Type	Versions	Cluster Support	Use Cases	Features
MongoDB	8.0, 7.0, 6.0	✅ Yes	Document databases, JSON storage	Auto-backups, replica sets, sharding
PostgreSQL	17, 16, 15	❌ No	Relational data, analytics, ACID compliance	Extensions, backups, full-text search
Greenplum	7.1.0, 7.0.0, 6.30.1	✅ Yes	MPP data warehouse, large-scale analytics	Distributed queries, petabyte-scale, PostgreSQL-compatible
Milvus	2.6.3, 2.5.19, 2.4.11	✅ Yes	Vector databases, AI embeddings, semantic search	Similarity search, indexing, distributed architecture
Redis	7.4, 7.2, 7.0	❌ No	Caching, sessions, real-time data	Persistence, pub/sub, data structures
Neo4j	5.26, 5.25, 5.24	❌ No	Graph databases, relationships, networks	Cypher queries, APOC procedures, graph algorithms
RabbitMQ	4.0, 3.13, 3.12	❌ No	Message queuing, async tasks, event streaming	Multiple protocols, routing, federation

Cluster Deployments

MongoDB, Milvus, and Greenplum support cluster mode for high availability and horizontal scaling. Select "Cluster" deployment mode during add-on creation to configure multi-node deployments.

How to Create an Add-on

Step 1: Navigate

• Go to Add-ons in main navigation
• Click Create Add-on

Step 2: Select Type and Version

• Choose database/service type (MongoDB, PostgreSQL, Greenplum, Milvus, Redis, Neo4j, RabbitMQ)
• Select version from the 3 most recent stable releases
• Review type-specific features and documentation

Step 2a: Choose Deployment Mode (MongoDB, Milvus, Greenplum only)

Single Node

• Best for development and testing
• Lower cost, simpler setup
• Single point of failure
• Suitable for non-critical workloads

Cluster (HA)

• Recommended for production workloads
• High availability with automatic failover
• Horizontal scaling capability
• 3-10 data nodes configurable
• MongoDB: Optional arbiter node
• Greenplum: Coordinator and segment nodes
• Milvus: Distributed architecture with etcd and MinIO

Step 3: Configure Add-on

Basic Configuration

• Label: Friendly name (e.g., "User Database", "Session Cache")
• Description: Purpose and notes
• Environment: Development or Production

Resource Tiers (MongoDB Example)

Tier	CPU	Memory	Disk	Replicas
Small	0.5	1GB	10GB	1
Medium	1	2GB	25GB	1
Large	2	4GB	50GB	3 (HA)
XLarge	4	8GB	100GB	3 (HA)

Backup Configuration

• Enable Backups: Automatic scheduled backups
• Schedule: Hourly, Daily, Weekly, Monthly, or Custom cron expression
• Retention: Number of backups to keep (default: 7)
• S3 Bucket: Optional custom S3 bucket for backup storage

Step 4: Deploy

1. Review configuration summary
2. Click Create Add-on
3. Monitor deployment status (typically 2-5 minutes)
4. Get connection credentials from add-on details page

Using Add-ons in Your Apps

Add-ons are automatically connected when selected during app deployment. Access connection details through STRONGLY_SERVICES:

# Python Example
import os
import json
from pymongo import MongoClient

# Parse STRONGLY_SERVICES
services = json.loads(os.environ.get('STRONGLY_SERVICES', '{}'))

# Get MongoDB add-on connection
mongodb_addon = services['addons']['addon-id']
client = MongoClient(mongodb_addon['connectionString'])
db = client[mongodb_addon['database']]

# Use the database
users = db.users.find({'active': True})

Add-on Management

Start/Stop

• Reduces costs when not in use
• Data persists when stopped
• Start time: 30-60 seconds

Backups

• Manual backup: Click "Backup Now"
• Automatic S3 backups (scheduled)
• View backup history
• Restore from any backup point
• Stored in AWS S3 for durability

Scaling

• Upgrade tier without downtime
• Increase disk space
• Add replicas for HA

Monitoring

• CPU and memory usage
• Disk utilization
• Connection count
• Query performance metrics

Backup & Restore

All add-ons support automated backups to AWS S3 with database-specific backup tools for data integrity.

Backup Methods by Database Type

Database	Backup Tool	Format	Features
MongoDB	mongodump	.archive	Full database dump, includes indexes
PostgreSQL	pg_dump	.sql	Full database dump, schema + data
Redis	redis-cli --rdb	.rdb	Point-in-time snapshot
Neo4j	neo4j-admin dump	.dump	Full graph database dump
RabbitMQ	rabbitmqctl export_definitions	.json	Exchanges, queues, bindings
Greenplum	pg_dump	.sql	MPP-aware backup
Milvus	milvus-backup	.tar.gz	Vector data + metadata

Manual Backups

1. Navigate to add-on details page
2. Click Backup Now button
3. Backup job starts immediately
4. Monitor backup progress in job logs
5. Backup stored in S3 bucket: s3://strongly-backups/backups/<addon-id>/<date>/

Scheduled Backups

Configure automatic backups during add-on creation or edit settings:

• Schedule: Hourly, Daily, Weekly, Monthly, or Custom cron
• Retention: Keep last N backups (default: 7)
• S3 Bucket: Custom bucket or default strongly-backups
• Naming: backup-YYYYMMDDHHMMSS.{ext}

Backup Storage & Organization

All backups are stored in AWS S3 with the following structure:

s3://strongly-backups/
  └── backups/
      └── <addon-id>/
          └── <YYYY-MM-DD>/
              ├── backup-20250126120000.archive  (MongoDB)
              ├── backup-20250126130000.sql      (PostgreSQL)
              └── backup-20250126140000.rdb      (Redis)

Durability

S3 provides 99.999999999% durability across multiple availability zones. Your backups are safe and highly available.

Restore from Backup

Restore add-on data from any backup point:

1. Navigate to add-on details page
2. Click Backups tab
3. Select backup from history list
4. Click Restore button
5. Confirm restoration (will stop add-on temporarily)
6. Restoration job downloads from S3 and restores data
7. Add-on automatically restarts with restored data

Warning

Restoring from backup will replace all current data. Create a backup of current state before restoring if needed.

Backup Best Practices

• Production workloads: Enable daily automated backups minimum
• Critical data: Use hourly backups with 7-14 day retention
• Before upgrades: Always create manual backup first
• Test restores: Periodically verify backups can be restored
• Multi-region: Consider copying backups to different region for DR
• Compliance: Adjust retention based on regulatory requirements

Important

Keep Development and Production add-ons separate. Never connect a production app to a development database.