I could create a separate AmazonEC2Client to deal just with Amazon specific portion, but if there is a way to get the AmazonEC2Client from jclouds API, that would make the code a bit nicer -- one instead of two initialization paths.
Just to expand on Andrew Bayer's answer a bit: jclouds does not depend on the Amazon libraries, so there is no AmazonEc2Client "hidden" somewhere inside jclouds. jclouds talks directly to the EC2 HTTP API.
ap
