How to Mine Cryptocurrencies on AWS Ubuntu Server Using Minergate!
What Is MinerGate? MinerGate is an open mining pool where people use their computers to add hashing power to that of thousands of other miners. The user interface is openly downloadable and allows people to quickly start mining Ethereuem, Bitcoin, and a selection of other altcoins. It helps to break down the usual complexities found in mining.
MinerGate allows anyone to grab the program and run it on his or her computer. Large, powerful units can, of course, add more power, but smaller, amateur miners can use a normal PC or laptop. They can even run the smartphone application if they’re so inclined. It sounds great, but realistically, the lesser your device, the less you can earn. A phone is nearly pointless in terms of hashing power. The average laptop will put a little more starch in your pants, and it can make it fun to get involved, but returns will still be limited. Of course, it all depends on the coin you mine as well.
While MinerGate is quick and simple to use, there are complex algorithms running in the background. In just a few clicks, it exploits the maximum capability out of your hardware based on how much you want to dedicate. You don’t need to get involved in any of this with a program like MinerGate; simply let it do the hard work while you while away the day on low-processing tasks.
The MinerGate team will reward you based on how much input you are committing. If you’re looking to boost your passive income, then it’s a neat solution. You can put your computer to work while you aren’t using the hardware.
There are lots of other mining pools around, but many require a little more knowledge to run and can only mine one cryptocurrency. MinerGate has the distinct advantage of working from both the CPU and GPU to mine multiple cryptos for maximum profit. For example, you can run both Ethereum and Monero mining simultaneously.
Steps to Mine Cryptocurrencies on AWS Ubuntu Server
- If applicable, follow the steps in Create a Free Account.
- In the AWS Management Console, open the Amazon EC2 Dashboard by clicking the EC2 icon in the upper-left of the console.
- In the region selector in the navigation bar, select the region that is geographically closest to you. All resources required to run your instance must be created in the same region.
- Follow the steps in Create a Key Pair. If you plan to connect to your Linux instance from Windows, be sure to follow the instructions in the section titled (Optional) To prepare to connect to a Linux instance from Windows using PuTTy. Save the resulting .ppk file to the same folder as the .pem file that you downloaded.
- In the console navigation pane, click EC2 Dashboard. In the Create Instance section of the console, click Launch Instance.
- On the Step 1 page, find the first Ubuntu Server in the list of Amazon Machine Images (AMIs) and click the corresponding Selectbutton.
- On the Step 2: Choose an Instance Type page, accept the default General Purpose t2.micro instance type, and then click Next: Configure Instance Details.
- On the Step 3: Configure Instance Details page, most of the default selections should be fine. Change or confirm the following:
• Number of Instances – 1 (default).
• Purchasing option – Request Spot Instances unchecked (default).
• Network – A network other than Launch into EC2-Classic.
• Subnet – Select a subnet in the same region that you created a key pair.
• Auto-assign Public IP – Select Enable.
• IAM role – None (default).
• Shutdown behavior – Stop (default).
• Enable termination protection – Check Protect against accidental termination.
• Monitoring – Enable CloudWatch detailed monitoring unchecked (default).
• Tenancy – Shared tenancy (muti-tenant hardware) (default).
• Accept the default values listed in the Network interfaces section.
- At the bottom-right of the page, click Next: Add Storage and apply the following options in Step 4: Add Storage:
• Size (GiB) – 20
• Volume Type – General Purpose (SSD)
• Delete on Termination – Unchecked
- At the bottom-right of the page, click Next: Tag Instance and apply the following options in Step 5: Tag Instance:
• Enter a Name for Key and corresponding text for Value; for example, set Key = Name and Value = Ubuntu test.
- At the bottom-right of the page, click Next: Configure Security Group and apply the following options in Step 6: Configure Security Group:
• Assign a security group – Enable the option Create a new security group.
• Security group name – Enter a descriptive value for the security group; for example, TrustySG.
• Description – Either leave the default value or enter a description, such as Security Group for Ubuntu Trusty.
- Create the following security rules:
• SSH (should be listed by default):
a) Type – SSH
b) Protocol – TCP
c) Port Range – 22
d) Source – My IP
• RDP (click Add Rule and select RDP from the list):
a) Type – RDP
b) Protocol – TCP
c) Port Range – 3389
d) Source – My IP
- At the bottom-right of the page, click Review and Launch. At the bottom-right of Step 7: Review Instance Launch, click Launch.
- From the Select an existing key pair or create a new key pair dialog box, select the key pair you created in step 4 from the Select a key pair dropdown, check the acknowledgement box, and click Launch Instances.
- On the Launch Status page, in the section Your instance is now launching, click the instance ID (i-xxxxxxxx).
- As soon as Status Checks complete successfully and Instance State status is running, connect to your instance using one of the methods described in Connect to Your Linux Instance.
- To avoid unnecessary charges, stop your instance when you are not using it. If you qualify for Free Tier, make sure you understand the pricing guidelines. When you are completely finished using your instance, complete the steps described in Clean Up Your Instance and Volume to help ensure that you do not incur unnecessary charges.
You can’t connect to your instance unless you launched it with a key pair for which you have the .pem file and you launched it with a security group that allows SSH access. If you can’t connect to your instance, see Troubleshooting Connecting to Your Instance
To connect to your Linux instance using a web browser
You must have Java installed and enabled in the browser. If you don’t have Java already, you can contact your system administrator to get it installed, or follow the steps outlined in the following pages: Install Java
and Enable Java in your web browser
From the Amazon EC2 console, choose Instances in the navigation pane.
Select the instance, and then choose Connect.
Choose A Java SSH client directly from my browser (Java required).
Amazon EC2 automatically detects the public DNS name of your instance and populatesPublic DNS for you. It also detects the key pair that you specified when you launched the instance. Complete the following, and then choose Launch SSH Client.
In User name, enter
In Private key path, enter the fully qualified path to your private key (
.pem) file, including the key pair name.
(Optional) Choose Store in browser cache to store the location of the private key in your browser cache. This enables Amazon EC2 to detect the location of the private key in subsequent browser sessions, until you clear your browser’s cache.
If necessary, choose Yes to trust the certificate, and choose Run to run the MindTerm client.
If this is your first time running MindTerm, a series of dialog boxes asks you to accept the license agreement, confirm setup for your home directory, and confirm setup of the known hosts directory. Confirm these settings.
A dialog prompts you to add the host to your set of known hosts. If you do not want to store the host key information on your local computer, choose No.
A window opens and you are connected to your instance.
If you chose No in the previous step, you’ll see the following message, which is expected:
Verification of server key disabled in this session.
Download Putty Key Gen:
Install Minergate on Ubuntu Server; Run Below Command to Install
sudo apt-get update && wget https://minergate.com/download/deb-cli -O minergate-cli.deb && sudo dpkg -i minergate-cli.deb;
Change “-xmr 32” to Other Cryptocurrency Symbol and the 32 is CPUs Count