PrimeBot).https://testnet.binance.vision/api.⚠️ Note: Make sure you use the correct environment (Mainnet vs Testnet).
If you prefer a GUI over command-line tools (scp, sftp), you can connect to your EC2 instance using FileZilla with your PEM key file.
18.222.33.44)ubuntu (or your AMI default user).pem file from EC2 setupRefer to:
Once connected, use the left panel for local files and the right panel for EC2 files. Drag & drop to upload or download.
💡 Tip: Ensure your EC2 instance is running. If FileZilla rejects your key, set the PEM file to read-only.
If you connected successfully in the GUI (via the Connect button) but the bot does not start when you press Start Bot – or the GUI shows no activity even though the server is running – this likely means the trading service is not active.
✅ To fix this, restart the bot service manually:
sudo systemctl restart trading_botAlternatively, you can run the Auto Script and choose option 8 (Restart Bot).
This will restart the background process and re-sync the GUI connection.
There are two easy ways to find your server's public IP address:
When you run the Auto Script during EC2 setup, it writes connection details into the log file. Open the autoscript log and look for a line showing your public IPv4 address, for example:
Server public IP: 18.222.33.44In rare cases, the bot may not be able to sell an asset completely due to the order matching process on Binance. As a result, a very small remaining balance – commonly referred to as dust – may remain in your account.
If such dust remains, the bot will not be able to place a new buy order (and it also cannot sell the remaining amount, since it is below Binance’s minimum trade limit).
Although the bot includes an automatic process to detect and remove dust, in some situations – particularly when trading pairs with low liquidity or low volume – a small amount of dust may still persist in the bot’s internal state (estimated probability below 0.5%).
In version 5, you no longer need to configure technical parameters manually. We have integrated 5 pre-optimized Strategy Templates directly into the GUI. For the best balance between profit and risk, we highly recommend selecting the Balanced (Intermediate) template from the dropdown menu.
Thanks to v5's Independent Per-Pair Configuration, you aren't forced to use the "Balanced" setup for your entire portfolio. You can easily run a conservative "Automatic Accumulation" strategy on BTC/USDT, while simultaneously unleashing the "Quick Scalping" strategy on a volatile altcoin like SOL/USDT.
Unfortunately, if you have lost the .pem key file that was created when you launched your EC2 instance, you cannot recover it. AWS does not store or back up private keys for security reasons – the key file is only available once when the key pair is created.
When you create a key pair in AWS, the private key (.pem) is generated once and immediately downloaded. AWS never keeps a copy of it. Without that file, SSH or SFTP (FileZilla) access to the current instance will no longer work – unless you had a backup.
You can create a new key pair and attach it to your instance using one of the methods below.
.pem file securely.ssh -i new-key.pem ubuntu@<public-ip>ubuntu with ec2-user or your AMI’s default username.)*If your instance supports EC2 Instance Connect or has the SSM Agent enabled, you can log in directly from the AWS Console without the .pem file, then manually add a new public key to ~/.ssh/authorized_keys.
If you are using the AutoScript to manage or connect to your instance (as described in Quick Start GUI), you need to update your configuration before running it again:
.pem key file to trading-bot-key.pem (the default name expected by the script).Always back up your .pem key file securely – store it in an encrypted folder, password-protected cloud drive, or external device.
Once lost, AWS cannot recreate or resend it.
Prime Spot DCA Trading Bot is self-hosted – it runs on your own server (for example, on AWS EC2). You have full control over execution, data, and API keys. In contrast, exchange-integrated bots run entirely on the exchange’s infrastructure, meaning you depend on the exchange’s uptime, limits, and internal logic.
Prime Spot DCA allows deep strategy customization – supporting Independent Per-Pair Configuration (run entirely different setups on different coins simultaneously), technical indicators (RSI, MACD, ADX, Bollinger Bands), multi-TP and trailing TP, and advanced capital allocation logic. Furthermore, our Smart Safety Order Filter prevents the bot from blindly buying during a market crash (catching a falling knife). Exchange bots are usually simpler, focusing only on basic parameters with no indicator-based filtering.
Prime uses a one-time license purchase – no recurring subscription or platform fees. Most exchange or platform bots are either free but limited, or require monthly subscriptions or trading-volume-based fees.
Because Prime Spot DCA runs on your own server, you maintain complete independence: no data sharing with third parties, and no risk of exchange-side restrictions affecting your strategy. Exchange bots are tied to the platform – you can’t move them elsewhere or modify internal logic.
Prime Spot DCA includes an integrated backtesting system that lets you test and refine strategies using historical data before live trading. Most exchange DCA bots only offer simplified profit-simulation previews without full indicator-based backtest capability.
👉 In short, Prime Spot DCA Trading Bot gives you professional-grade flexibility, transparency, and ownership – while exchange-built bots focus on simplicity and ease of use for beginners.