Migrate from AWS to Valebyte
Move from AWS Lightsail/EC2 to Valebyte: predictable flat pricing, no surprise data-egress bills, simpler control panel.
Why people leave AWS
Data egress at $0.09/GB destroys budgets
AWS charges $0.09/GB for outbound traffic to the internet. A 1 TB-traffic month adds $90 to your bill on top of the instance. SaaS apps with large media or backups are hit hardest.
Hidden costs: NAT, ALB, EIP, snapshots
A simple 'small VPS' setup quickly grows: $30 NAT Gateway, $20 ALB, $3.65 elastic IP if unattached, $0.05/GB-month for EBS snapshots. The bill rarely matches the calculator.
EC2 t3.small is $15.18 for 2 GB shared
Lightsail looks cheap ($3.50/512MB) but breaks at scale. EC2 prices are 2-3x higher than competitive cloud VPS for the same vCPU/RAM.
Vendor-specific lock-in
Once you wire up SQS, SNS, IAM roles, RDS, ALB, Route53 — migration involves rewriting infrastructure. Self-host the same patterns on Linux + Postgres + Caddy.
Complex permissions and console
IAM is powerful but requires hours to configure correctly. For most small/mid teams, this is friction without payoff. Valebyte is a one-key login.
Support paywall
AWS Basic support = forum and docs. Business support = $100/mo + 10% of bill. Many teams never get a human answer when something breaks.
AWS vs Valebyte: honest comparison
No marketing — actual differences. Including where they win.
| Feature | AWS | Valebyte |
|---|---|---|
| Cheapest VPS | Lightsail $3.50 — 512 MB / 30 GB / 1 TB cap | VPS-XS $7.59 — 2 GB / 20 GB NVMe / 10 Gbps unmetered |
| Equivalent of 2 GB / 1 vCPU | Lightsail $10 / EC2 t3.small ~$15.18 | VPS-XS $7.59 (dedicated vCPU) |
| Outbound traffic | $0.09/GB (free 100 GB Lightsail / 1 GB EC2) | 10 Gbps unmetered (no overage) |
| Snapshot pricing | $0.05/GB-month + cross-region transfer | Free (included) |
| Locations | 30+ regions, 100+ AZs | Multi-provider: FR, NL, DE, NO, JP, IN, US, ZA, AE, BR |
| Network attachments | NAT $30/mo, ALB $20+/mo, EIP $3.65/mo | All included (public IP, no per-attachment fees) |
| Database | RDS db.t4g.micro ~$15/mo + storage + I/O | Self-host Postgres/MySQL on your VPS, $0 extra |
| Object storage | S3 $0.023/GB + $0.005/1000 PUT + egress | BYO MinIO on VPS or Backblaze B2 ($6/TB) |
| Console + API | AWS Console + SDK (steep learning curve) | Web panel + REST API (simple) |
| Payment methods | Card, AWS credits | Stripe, Square, SEPA, USDT/BTC/ETH/TON, MIR/SBP |
Migration checklist: 12 steps
Total time — 1 hour (small VPS) to 4 hours (TB-scale DB). Zero-downtime possible — steps 4-6.
-
1
Snapshot or back up your existing servers
For Lightsail: Console → instance → 'Snapshots' tab → 'Create snapshot'. For EC2: Create AMI from instance, also snapshot attached EBS volumes. Both incur ongoing storage cost until deleted.
-
2
Export DNS records to a zone file
Route53 → Hosted zones → select zone → 'Export to CSV'. Convert CSV to BIND format with `dnscontrol` or import directly into Cloudflare DNS for free.
-
3
Lower DNS TTL to 300 seconds
Do this 24h before cutover. Visitors see new IP within 5 min instead of waiting hours for caches.
-
4
Order your Valebyte VPS or dedicated matching specs
Match RAM and vCPU; disk you can grow later. Pay your preferred way (card, SEPA, USDT/BTC, MIR/SBP).
-
5
Restore data via rsync over SSH
`rsync -avzP --delete /source/ root@new-server:/dest/` for files, configs, Docker volumes, and pre-dumped databases. Test first with `--dry-run`.
-
6
Migrate databases with logical dump
Postgres: `pg_dumpall | ssh new-server psql`. MySQL: `mysqldump --all-databases | ssh new-server mysql`. If on RDS: enable a 'Public access' temporarily, then `pg_dump` from your local. For Aurora: use `pg_dump --no-publications --no-subscriptions` to avoid replica errors.
-
7
Re-create users, SSH keys, sudoers
Don't copy `/etc/shadow` blindly across distros — use `useradd` and copy `~/.ssh/authorized_keys`. Verify sudoers with `visudo -c`.
-
8
Install your stack
Same Docker Compose, Ansible playbook, or k3s manifest works on Valebyte (Ubuntu 22/24, Debian 12, AlmaLinux 9 are available). No vendor-specific lock-in.
-
9
Re-create firewall rules
List your existing rules → recreate via `ufw` or `nftables` on Valebyte. Test all inbound services with `nmap` from outside before going live.
-
10
Update DNS A/AAAA records to new IPs
Wait for old TTL to expire (5 min if you lowered earlier). Watch traffic with `tcpdump` to confirm requests are arriving on the new server.
-
11
Run both servers in parallel for 48 hours
Don't shut down the old side immediately. Watch error rates, latency, customer complaints. If something breaks — flip DNS back instantly.
-
12
Cancel old service only after 7 days
Wait until you're sure nothing references old IPs (cron jobs, webhooks, hardcoded configs in third-party services).
Pick a plan that matches your AWS budget
All plans: 10 Gbps, dedicated IP, full root, KVM console
Frequently asked questions
Will AWS refund unused balance?
How fast is the actual cutover?
Can I run my Docker Compose stack on Valebyte?
Do you have an API?
Can I migrate without downtime?
What about IP-based licenses?
Leave AWS today
10 Gbps unmetered, multi-region, flexible payment (card, SEPA, crypto, MIR). VPS in 30 seconds.
Choose VPS