groovy grape gripes

I’ve “had it up to here” with trying to get groovy grapes to pull an artifact from a local artifactory repo with custom credentials.  Can’t find the artifact?  Let me wait 10 minutes before exiting with the stack trace!  Need logon credentials?  Well now we have to use the separate ~/.groovy/grapeConfig.xml to specify that!  Why can’t it also be in the grapes annotation?  Like in a build.gradle closure block?  And when it is configured correctly (via it can’t find it, even though its found in the build.gradle closure!   AAARRRRRGGGG!!!!!!


Connecting to Amazon EC2 – Part Duex

3 years have passed and i’m playing around with cloud VMs again.  A little more experienced, a little more chin on the hair.  But still, connecting to a new instance seems tough.  This time, a public DNS was not created with the new instance.  I created a forum support request:  Hopefully the issue can be resolved.  Will update this post with results….


  1. The public DNS and IP are interchangeable, but that doesn’t exist in their documentation.
  2. Once you create an instance with a keypair, it sticks.  If you lose your keypair file, your lose complete access to your instance. I sure hope there are other options aside from blowing away your instance with the lost keypair file 8(


Connecting to an Amazon EC2 Instanct

Here is my attempt to learn Amazon EC2.  First things first:  Create a VM in Amazon’s EC2 cloud:

  1. Go to
  2. Create AWS account.  Run through Sign Up. Give credit card.  Ect.
  3. In EC2 dashboard, click Launch Instance
  4. Choose “Basic 32-bit Amazon Linux AMI 2011.02.1 Beta” Micro Instance, since its free for 1 year.
  5. Done.  Thats it.  The AMI instance “Basic 32-bit Amazon Linux AMI 2011.02.1 Beta” was created for me.  Easy!  +1 for easy.

Okay, now how do I use it?  Hmm…  Right click instance, select “Connect”:

Connect Help

Connect Help

I’m using Windows, so PuTTY is my only option.  But its not working with .pem key i created….

I posted a thread ( in their EC2 forum and got a really fast response.  +1 for fast response.  After some back and forth discussion, i discovered how to connect:

  1. Configure your security settings to allow port 22 (SSH) access to the VM.
  2. Convert the .pem key to a .ppk key (
  3. Thats it, now I can SSH in via PuTTY!

So, while the connection information wasn’t strait forward, I was still able to connect.