Skip to main content

Amazon EC2: How much less userfriendly can you make it?

This morning I read about the new Amazone Elastic Compute Cloud service. It's basically a cluster of Xen VPSes, done right.

At least that's what I thought until I actually tried to use it.

Let's see:

  1. Sign up for AWS
  2. Sign up for S3
  3. Create certs
  4. Download tools
  5. Export 3 EC2 environment variables
  6. Oh, hell. Tools are in java. Switch to windows box since I don't have the patience to figure out installing Java 1.5 on debian right now.
  7. Repeat steps 4-5
  8. Export JAVA_HOME
  9. Run ec2-describe-images
  10. Exception in thread "main" java.lang.NoClassDefFoundError: com/amazon/aes/webservices/client/cmd/DescribeImages

Looks like I get to try to fix the classpath for them. How retro-cool can you get? It's just like 1999!

Bah. Next time, use Python, guys.

update:: Apparently they didn't even bother testing on windows and their script was just plain broken. Way to go.

Comments

Anonymous said…
Shrug. It took me less than twenty minutes - on a Windows machine - from first hearing about EC2 to having an instance up and running apache & mysql with one of my apps on it.
Anonymous said…
Er, if you're running Debian and you can't figure out how to install Java, perhaps you shouldn't be messing with something like EC2... Or Debian for that matter!
Anonymous said…
heh. I know this is over a year old, but yeah, if you can't figure out how to install java on debian (which is about as easy as it gets), then I dunno why you decided to tackle this.

It isn't like you need to know java to use these tools. Hell, I hate java(and love Python). But that's hidden from you, with these tools. Gotta think that more people with Windows will have java than python already anyway.

Seriously, what's hard about 'sudo apt-get install sun-java6-bin'?

Popular posts from this blog

The Missing Piece in AI Coding: Automated Context Discovery

I recently switched tasks from writing the ColBERT Live! library and related benchmarking tools to authoring BM25 search for Cassandra . I was able to implement the former almost entirely with "coding in English" via Aider . That is: I gave the LLM tasks, in English, and it generated diffs for me that Aider applied to my source files. This made me easily 5x more productive vs writing code by hand, even with AI autocomplete like Copilot. It felt amazing! (Take a minute to check out this short thread on a real-life session with Aider , if you've never tried it.) Coming back to Cassandra, by contrast, felt like swimming through molasses. Doing everything by hand is tedious when you know that an LLM could do it faster if you could just structure the problem correctly for it. It felt like writing assembly without a compiler -- a useful skill in narrow situations, but mostly not a good use of human intelligence today. The key difference in these two sce...

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...