Thanks Scott. It didn't occur to me to try switching my instance to small,
do the install, and then switch back to micro. I'll give that a try.
Also, for some reason I thought the amd64 builds of Ubuntu were lacking in
some components. Maybe that's only true for client, but I definitely saw a
reco
On Mon, 25 Oct 2010, Davepar wrote:
> The workaround is only useful when you're setting up a new instance.
> It's useless for the instance I already invested a day setting up. It
> would be a really good idea to put a warning somewhere in the docs for
> micro instances. Once AWS starts handing out
Launch the instance as m1.small, then install java, and save as a different
ami.
>From then, you can launch the saved ami as t1.micro.
I must say its an ugly workaround, but it works.
On Sun, Oct 10, 2010 at 5:45 AM, Branden Makana
<634...@bugs.launchpad.net>wrote:
> Is there any workaround fo