[Last week](https://hackernoon.com/getting-started-on-a-neo-smartcontract-d36927e4bf1f), we covered how to install a CLI to interface with the public NEO [blockchain](https://hackernoon.com/tagged/blockchain). However, we cannot develop our contract on this environment — it will cost us (~500 GAS or ~2.5k USD as of the writing of this article) to deploy here! Instead, it is good practice to deploy our own **private NEO** [**network**](https://hackernoon.com/tagged/network) and test the our smart contracts there. To do that, we need a server … where better to get one than **Amazon Web Services**! Lets get started!

**Step 1:** initiating an EC2 instance from AWS

Log into your [AWS account](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/), click on _Services_ \> _EC2 > Launch Instance_

![](https://hackernoon.com/hn-images/1*vjgQvvhDmZyKomT2mhDRLQ.png)

choose the _Amazon Linux 2 AMI_

Select the t2.micro _(free! if this is your first and only instance)_

![](https://hackernoon.com/hn-images/1*UYez3OiXUux29ABI2UQblA.png)

Click _review and launch > launch!_ You will then be met with the following popup:

![](https://hackernoon.com/hn-images/1*MFERA39c_q9dtmqLMDvo3w.png)

If this is your first instance, choose _Create a new key pair_ from the drop down. Give the new key pair a name > _Download Key Pair_. **Launch!**

**Step 2:** Preparing the keypair for SSH

If you have not already done so, [download putty here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).

We need to first transform your .pem file, into something putty can use (.ppk). Go to Windows Start, search _PuTTYgen._

![](https://hackernoon.com/hn-images/1*LVA_e8XDa3zfaAG3kSmodQ.png)

Once open, click _Load_ \> drop down for _All Files (\*.\*) > Choose myfirstkeypair.pem._

Click _Save private key_.

_Are you sure you want to save this key without a passphrase?_ **Yes**

**Step 3:** Find your Public instance’s IP

Your instance should be up and running by now! Go back to the AWS console, _Services > EC2._ Click on _Instances,_ you should see the following:

![](https://hackernoon.com/hn-images/1*GMyC4MSWFDKwt6ktMhYb1w.png)

make note of the **Public DNS (IPv4)** and **IPv4 Public IP.**

**Step 4:** SSH time!

Start up **PuTTY**. under **Category**, _Connection_ \> _SSH_ \> click _Auth._ Browse for the .ppk file you generated through PuTTYgen.

![](https://hackernoon.com/hn-images/1*VcH9Lj1iV-G_tfHKVSRLWA.png)

Next go back to _Session_. Under _Host Name_, put the **Public DNS** of your sever from **step 3**. Under _Saved Sessions_, give your server a name! Click _Save_!

![](https://hackernoon.com/hn-images/1*6GFwe66wCYT1lyLAXVUrqg.png)

Click Open! username: **ec2-user**

We will stop here for now. If you’re new to **Amazon Web Services**, it is seriously an industry changing tool that we’ve only scratched the surface of today. Launching a single micro instance falls under “free tier” and shouldn’t cost you a dime! Do be careful: _adding additional infrastructure (EBS volumes, increasing server sizes …) will incur cost!_

[**Nodis.io**](https://nodis.io) is a marketing platform for local business, generating engagement through small activities and rewarding users with cryptocurrency they can later spend on these stores. We know being a stand-alone business can be difficult — Nodis solves this by not only creating a community to help and engage, but represents that effort as spendable tokens!

Follow us on [Instagram](https://www.instagram.com/nodis.io/) and [Facebook](https://www.facebook.com/NodisGetNoticed/)!

**Next week’s guide:** private NEO network on AWS (part 2). Stay tuned!

Amazon

Facebook

Instagram

Too Long; Didn't Read

Get hands-on learning from ML experts on Coursera 

Building your private NEO network on AWS (part 1)

Too Long; Didn't Read

Companies Mentioned

Coin Mentioned

@dominicfung_58781

RELATED STORIES