Andrew Gaul mentioned this before, but it is worthwhile calling out that our AWS support is at least partially broken for all recent jclouds versions.
In May of 2012, Amazon announced a new way to sign requests, which implies use of a stronger signature, version 4. Andrew Gaul opened an issue on this for S3, which I've recently repurposed for all AWS. https://issues.apache.org/jira/browse/JCLOUDS-480 This Signature V4 announcement went with a policy of new regions only supporting that. Since we never implemented that, it is now creeping up as AuthorizationExpections connecting to Frankfurt. https://issues.apache.org/jira/browse/JCLOUDS-777 This was complicated by some other bugs in our neglected AWS codebase, including the impossibility to filter out regions due to two latent bugs. https://issues.apache.org/jira/browse/JCLOUDS-774 <- fixed https://issues.apache.org/jira/browse/JCLOUDS-781 <- not yet I'm working on all of these issues, but in the future, we really need to be more proactive. Running the AWSEC2TemplateBuilderLiveTest would have picked this up the minute the frankfurt region came online. This test creates no resources, so doesn't cost anything to run. I am working on that test to make it easier to maintain as well. It used to be the case that we executed live tests on major releases, in hidsight, we'd have had more heads-up on this issue if we did that. It is important for jclouds long-term survival to have more than one person keeping the aws-ec2 fire burning; it is our most important compute cloud provider. Relying on me to paratroop in every 2 years and fix everything is not the answer. -A
