Offering to co-maintain Amazon Web Services

7.x does need a maintainer but the current plans are to change to be dependent on the AWS SDK for PHP. What are you plans for the migration?

That is the point. There is no "migration" or "integration". The original goal of this module was to be what the AWS SDK module is but that was before that library came around and was full featured. Now that it is and maintained as the official AWS PHP library it is best to use that module for that. That means this modules goal and features will change to something else. As there is a lot that can be done on top of the API, there is much to choose from but I think we should be clear on redefining its goal so that we are able to stay on track and make appropriate decisions.

@dragonwise,

I understand it is best to use AWS PHP library. My suggestion is that we will take the following steps: 1) First we finish the "migration" from 6.x to 7.x based on the current code, then 2) we will do an "integration" with AWS SDK which is wrapping official AWS PHP library.

In step 2, I think we will work on removing aws_ec2_api.* by replacing AWS PHP SDK.

I don't understand, what would be left in this module if we replace the AWS api with the official api? The purpose and goal of this module was to be an AWS SDK for Drupal but we have that now so the purpose needs to be redefined and completely rewritten to match that purpose. Since this is a hard break it is much better done without migrating old code that will completely dumped in both code and function. Its better to send users to the new module during major Drupal upgraded migration than to do it during a smaller module version migration.

I am closing this issue, as there haven't been follow-up actions as per Taking over unsupported (abandoned) projects (which isn't just about unsupported or abandoned projects).