Topic: Running bitcoind on Amazon AWS (EC2) help - page 2. (Read 3875 times)
Whoa .. please make sure you do not exceed the "free tier" limit for bandwidth. Cause then you are charged. Apparently its not all that "free". Check the limits or you might be surprised later.
You'll want your own EBS to store the blockchain and it will be persistent. Amazon has lots of information detailing it.
I actually did this last week. It took days, and I kept blowing away my bitcoind while tweaking things.
I eventually gave in and downloaded the torrent for the recent blocks, but even that took a long time to import, as Disk IO on the micro instances is very limited as well as CPU instances ... Note that the Micro instance is not guaranteed performance as it is their "free" tier"
I eventually went to a m1.large for the two day period to sync all blocks, and now seems to be working fine on the Micro instance once it caught up and I reverted.
kosta
I eventually gave in and downloaded the torrent for the recent blocks, but even that took a long time to import, as Disk IO on the micro instances is very limited as well as CPU instances ... Note that the Micro instance is not guaranteed performance as it is their "free" tier"
I eventually went to a m1.large for the two day period to sync all blocks, and now seems to be working fine on the Micro instance once it caught up and I reverted.
kosta
You may want to look at the ec2 ebs which is persistent. I use it for two of my servers (not bitcoin) an for 6 years now have been happy with its reliability.
As far as usage goes, I am not sure off the top of my head it has been so long.
As far as usage goes, I am not sure off the top of my head it has been so long.
thanks! looks like by default it is already running on EBS, it auto mounted 8 GB of space from EBS when the EC2 instance was created. Now just waiting for the block chain to catch up.
It is taking forever and already used up 3GB of space.
I wonder if this will be the major flaw of bitcoins, say 20 years from now, how the heck on earth will any new client able to catch up, it will take weeks and tons of space.
You may want to look at the ec2 ebs which is persistent. I use it for two of my servers (not bitcoin) an for 6 years now have been happy with its reliability.
As far as usage goes, I am not sure off the top of my head it has been so long.
As far as usage goes, I am not sure off the top of my head it has been so long.
Hi guys, total newbie to amazon's AWS EC2 instances, but am very familiar with linux. Have some questions if anyone can help, thanks!
I have setup a micro EC2 instance using amazon's free trial offer (installed amazon's ami linux), downloaded and have bitcoind running on the server. I can see in the log it's syncing up. Here are my questions:
1) From my understanding, EC2 instance is not perm, as soon as it shuts down everything is wiped. Which means as soon as it shuts down all the data from bitcoind is wiped and next time i have to resync from block 1. I must not be using the right tool (EC2), can someone point me in the right direction on what exactly i should be using to fix this? I just want a regular/vps linux server that doesn't wipe the data every time it goes down.
2) Bitcoind is doing massive amount of sync on the network, i can see the network spike up in amazon's monitoring tool, is there an easy way to tell how much in/out network data i have used vs the threshold before i get charged. I clicked on all their links/monitoring but can't figure out where they keep this info. I plan to leave this running in the background but don't want to get hit with a surprise bill a week later.
Thanks!
I have setup a micro EC2 instance using amazon's free trial offer (installed amazon's ami linux), downloaded and have bitcoind running on the server. I can see in the log it's syncing up. Here are my questions:
1) From my understanding, EC2 instance is not perm, as soon as it shuts down everything is wiped. Which means as soon as it shuts down all the data from bitcoind is wiped and next time i have to resync from block 1. I must not be using the right tool (EC2), can someone point me in the right direction on what exactly i should be using to fix this? I just want a regular/vps linux server that doesn't wipe the data every time it goes down.
2) Bitcoind is doing massive amount of sync on the network, i can see the network spike up in amazon's monitoring tool, is there an easy way to tell how much in/out network data i have used vs the threshold before i get charged. I clicked on all their links/monitoring but can't figure out where they keep this info. I plan to leave this running in the background but don't want to get hit with a surprise bill a week later.
Thanks!
Jump to: