The AWS SDK for PHP is now very complete, functional, and supported where it was not 3 years ago when I started this module. What do think about turning this module into a Drupal wrapper for that library?

As a wrapper we would provided libraries integration, a base permission, and account related info management like for keys etc. We could build sub-modules for any required base API level code needed for any specific service. I would still recommend we keep the implementation level code to external but dependent modules.

Thoughts?

Comments

geerlingguy’s picture

Maybe consider merging this project with AWS SDK for PHP? Though that project is newer, it is already in use by 10x as many sites...

There's also the Creeper module for AWS SDK support. I don't see any reason why we have so many modules that do the same thing... See: #1125984: Suppercede creeper project with awssdk.

boombatower’s picture

subscribe

dragonwize’s picture

Sounds good to me. Since there is a little unknown use in this module, for now I will just post a note on the project page. Though it does seem bad to have this namespace go to waste.

geerlingguy’s picture

Yeah :(

I really wish there were some way of merging names, as this seems to happen with almost every API in existence :-/

yas’s picture

I checked awssdk module and AWS SDK for PHP, then I realized as follows:

  • AWS SDK for PHP by Amazon
    • MVC: "Controller".
    • Provides functions of full access to AWS including CloudFormation, CloudFront, CloudWatch, EC2, Elastic Bean Stalk, Elastic Load Balancing, Elastic MapReduece, Identity and Access Management, RDS, S3, SimpleDB, SES, SNS, SQS.
  • awssdk module
    • MVC: "View" for only configuration. No "Model" for AWS.
    • Requires to write something like "View" as UI and additionally "Model" as database schema for your Drupal site if you would like to show something on Drupal site from AWS.
    • Provides *.module for administer configurations (credentials) in order to use AWS SDK for PHP (by Amazon) on your Drupal site.
    • Requires to download AWS SDK for PHP by Amazon from AWS separately, however awssdk provides drush.make,
    • Used for only 7.x sites. (However it should be no problem rather in the future)
  • Amazon Web Services API (This module)
    • MVC: Provides "View" as UI library and "Model" (database schema) for your Drupal site. aws module consists of two parts:
      1. aws module as a library of "View" and "Model"
      2. [ aws/aws_ec2_api + REST Client ] modules as Controller.
    • [ aws/aws_ec2_api + REST Client ] module is corresponding to [ awssdk + AWS SDK for PHP ].
    • Provides administer configurations (credentials) in order to use AWS
    • Requires to download REST Client separately
    • Used for only 6.x sites

I think we can take an approach to use awssdk for our next development for D7 by not using both REST Client and aws_ec2_api... aws_ec2_lib module for UI and DB is still necessary.

boombatower’s picture

If anything another module or this one should be built to simply house the database stuff on top of awssdk (module). The awssdk module's goal is simply to provide drupal integration (ie. configuration and libraries) so you can use it directly in Drupal using the standard libraries interface. We could include the database stuff in a submodule as it seems to simply be a deeper integration, but someone would need to write a patch.

wizonesolutions’s picture

Maybe a 7.x branch should be created for this because it's currently categorized as 6.x, but there is no 6.x version of awssdk.

wizonesolutions’s picture

Yikes...after looking at the code of this module (which I thought used the Amazon SDK), I fully support merging it with AWSSDK and backporting. I'm going to look at AWSSDK and see if backporting that is feasible actually...

yas’s picture

Yes, please look at awssdk module.

wizonesolutions’s picture

I plan to make a simple Drupal 6 port: http://drupal.org/project/1333762. I post it here in case anyone wants to collaborate.

wizonesolutions’s picture

An update that my work will be with the standalone FPS library instead, since it's not in the AWS SDK :( - I'm going to try to get it into AWSSDK anyway, but otherwise will release it as its own integration module.

davisben’s picture

Issue summary: View changes
Status: Active » Closed (outdated)