
Once I had that down, I really started making progress. An example, and I fought for awhile figuring it out, is that a Collection in the Java SDK documentation translates to an Array of Objects in ColdFusion. There is a lot of language translation that has to happen in your brain to convert Java-speak to ColdFusion-speak. There is no documentation for a ColdFusion interface, but the Java SDK does have some extensive documentation. So, I abandoned that process and started working with the AWS Java SDK, it handles all of the Signature processing and lets me concentrate solely on the features that I want to implement. In fact, I never did get the API interface to Support Cases to work. Every time I started working with a new AWS feature (EC2, ELB, Support Cases, CloudWatch, etc.), I found that the implementation of Signatures and how the Signatures are processed in each area is different. I originally attempted to write a straight-up ColdFusion-only interface into the AWS API, but it proved to be very difficult. Although I am an Associate Certified AWS Solutions Architect, studying the documentation and working with the AWS console doesn't reveal some of the underlying features or requirements of their systems. It has been quite an experience and I have learned a ton of new things about the ins and outs and inner workings of AWS.

Over the past couple of months, I have been working on a portal for our Amazon Web Services Customers.
