Prerequisites
- An account on the target cloud with permission to launch VM instances (no special IAM roles are required by this product unless stated below — IAM required: none).
- An SSH key pair registered in the target cloud (all access is key-only; password SSH is disabled).
- Instance size ≥ 4 vCPU (pricing floor; 8 vCPU recommended).
- No internet access or external dependency is required at deploy time — the image is self-contained.
AWS
- Subscribe and launch.
Expected result `etcdctl put smoke ok && etcdctl get smoke` round-trips. - For network clients: enable TLS + auth (etcd supports cert and role/user auth), change --listen-client-urls/--advertise-client-urls in the unit, then open 2379 to your subnet only. Never expose etcd without auth — it will happily serve your secrets to anyone.
Expected result Remote etcdctl with certs works; anonymous requests are refused.
Validate
etcdctl endpoint health → 127.0.0.1:2379 is healthy
First boot: Build-time member state is wiped at capture; a fresh member initializes on your first boot.
Secure it
- Restrict SSH (22) to your own IP range in the cloud firewall/security group.
- Open application ports only per the ports table — closed-by-default is deliberate.
- Volume encryption: use your cloud's native volume encryption (enabled by default on most accounts); the image adds no proprietary encryption layer.
Costs & quotas
Software is billed by the marketplace at the listed rate; infrastructure (VM, storage, egress) is billed
by your cloud at its standard rates. The recommended size fits default service quotas in most accounts —
if you scale out, review your cloud's quota console before launch.
Next: configuration · troubleshooting · security notes
DC Associates Group