Eucalyptus 4.0.2 supports using AWS Java SDK 1.11.4 for Walrus but really 1.9.4
Here at Illinois Tech we~ I have just completed a successful semester of using HP Eucalyptus 4.0.2 Cloud Platform for all of our capstone and research projects. It has been a blessing as it has taken hardware requests and budgeting problems out of the IT groups hands and placed it into the students hands. They were able to rapidly deploy their services, load-balancers and any resources needed on their own.
Still in the process of upgrading to Eucalyptus 4.0.2 but it still works with S3cmd and the AWS Java API (as they intended it to).
This article is about Eucalyptus 4.0.2 – I still haven’t done the upgrade, 4.2.2 adds a few new features (looking at you Eucalyptus Architecture for UFS that I need to build in a test environment. I also need to upgrade my old HP DL 360s which have been work horses but the memory is only 4GB so that is asking for trouble.
This article is about getting the AWS Java SDK working with Eucalyptus 4.0.2. I was able to make this work… with conditions. The first issue is to review current information on hand. A quick search of the old Eucalyptus GitHub wiki gives some clues but only talks about ASW Java SDK version 1.3.x and Eucalyptus version 3.3.x. Of use for a few clues.
The next place to search is the Eucalyptus Users Google Group, which I recommend to visit if you have a Eucalyptus issue, very friendly people who love the product. I executed this search string: https://groups.google.com/a/eucalyptus.com/forum/#!searchin/euca-users/AWS$20Java$20SDK and a few interesting results came up. (Note one of the questions is my own…)
Credit goes to HP Eucalyptus employee, Steve Jones and user CoderSparks, who noticed that Walrus doesn’t support signature v4 in the AWS Java SDK – you need to default back to the version 2 signature – just like in the previous S3cmd article
I wanted to see for myself what the issue was so I tried to use the latest AWS Java SDK v1.11.4. Surprisingly everything worked, but one important feature. Let’s find out why.
My setup was:
- Windows 10 machine
- Netbeans 8.1
AWS Java SDK GitHub repo (contains the S3Sample file and Maven project build files)
- EDIT 07/13/16 - Clone this project: https://github.com/awslabs/aws-java-sample.git
I opened the sample/test code provided by Amazon, located in the https://github.com/aws/aws-sdk-java/blob/master/src/samples/AmazonS3/S3Sample.java file.
1) start by cloning the AWS Java SDK sample projects from AWSlab:
git clone https://github.com/awslabs/aws-java-sample.git
2) you can then open the project directly in NetBeans and it will import the entire build package (S3Sample.java) plus the Maven file (pom.xml) required to download all the .jar dependencies. Just hit the green RUN triangle and Maven will retrieve all of the JARs needed, even the AWS Java SDK.
3) Issues Encountered
- I encountered one small issue using AWS Java API 1.11.4 – this issue is referenced here by member CoderSparks. - though the questioner had a different error – I think the concept was the same:
4) What I Did Next
- Let me show you the initial code, my additions, and then explain it below. Modify the first few lines of code in the sample to reflect below.
Also don’t forget to create a credential file on the local system–don’t put creds in your actual code–too risky. In your home directory (Linux or Windows), create a directory named .aws with a file named credentials inside that file place the syntax below. These keys can be AWS account keys or HP Eucalyptus Account keys. The keys will come in your credentials zip file provided by your Eucalyptus Administrator, extract the zip file and the credentials listed below will be contained in a file named eucarc. In this story they are your account keys from our HP Eucalyptus system.
aws_access_key_id = YOURACCESSKEYHERE aws_secret_access_key = YOURSECRETKEYHERE
This is how the S3 connection object looks in the S3Sample.java provided in the Github link for the AWS JAVA SDK project.
Eucalyptus has different regions so to speak. So you need to comment out a few AWS specific lines and add an override so the code knows how to find your Walrus/OSG (Object Storage Gateway) URI.
With this set, the code will compile and run and connect to AWS Java SDK 1.11.4, and all of the JAR dependencies will be fetched by Apache Maven for you, easy setup no need to download any additional JARs or classpath.
From Whence Came That Error? I am glad you asked. I though it might be the same issue as the in the S3cmd article… Let’s look at the sample code and go item by item until we get to the error and squeeze its meaning out.
- Proper Connection being made to Eucalyptus OSG (Walrus)
- Proper code that creates a new bucket
- Proper code that creates uploads an new object to the previously created bucket
- Proper code that downloads that previously uploaded object
Error as follows from the exception handling in Java:
Downloading an object May 31, 2016 12:37:06 AM com.amazonaws.services.s3.AmazonS3Client getSignerByURI WARNING: Failed to parse the endpoint http://objectstorage.sat.iit.edu:8773/services/objectstorage, and skip re-signing the signer region java.lang.IllegalArgumentException: Invalid S3 URI: hostname does not appear to be a valid S3 endpoint: http://objectstorage.sat.iit.edu:8773/services/objectstorage
What could be causing this error? The connection is proper and 3/4ths of the code works! It is the signature problem mentioned above but also something else. The AWS Java SDK is too new and the way it handles downloading an object is not compatible. This means I had to roll versions back. If you roll back to AWS Java SDK 1.9.4 then you get 4 green check marks. So the solution is:
- Add the setSignature() method detailed above
- Change the POM.xml file value to pull AWS Java SDK 1.9.4 (no higher)
- Walrus problems are solved
Take care, Jeremy!