AWS SDK Grails Plugin
Locked
AWS SDK Grails Plugin
 
|
Hi,
I'm ready to release AWS SDK Grails Plugin : The AWS SDK Plugin allows your Grails application to use the Amazon Web Services infrastructure services. The aim is to provide a lightweight amazonWebService Grails service wrapper around the official AWS SDK for Java. Username : benorama Documentation : http://benorama.github.com/aws-sdk-grails-plugin/guide/ It gives an easy access to the following AWS services API : - Amazon CloudFormation - Amazon CloudFront - Amazon CloudSearch - Amazon CloudWatch - Amazon DynamoDB - Amazon Elastic Compute Cloud (EC2) - Amazon Elastic MapReduce - Amazon ElastiCache - Amazon Relational Database Service (RDS) - Amazon Route 53 - Amazon Simple Storage Service (S3) - Amazon Simple Email Service (SES) - Amazon SimpleDB - Amazon Simple Notification Service (SNS) - Amazon Simple Queue Service (SQS) - Amazon Simple Workflow (SWF) - Auto Scaling - AWS Elastic Beanstalk - AWS Identity & Access Management (IAM) - AWS Import/Export - AWS Storage Gateway - Elastic Load Balancing There is another great AWS Grails plugin but it uses a different approach and different java lib: its aim is to provide an easy "groovy" access to SES (through a groovy DSL) and S3 (through methods injection), based on JetS3 java lib. If you just need basic SES or S3 features, you might give it a try. We decided to write our own AWS plugin because it did not meet our requirements as we wanted:t - to have direct access to all AWS SDK for Java features including all AWS services, with custom client Groovy configuration, - to only use AWS SDK for Java lib with a consistent way to access all AWS services (and not JetS3 java lib specific methods and a custom SES DSL), - to have 100% compatibility with future AWS SDK for Java, as it is just a simple lightweight wrapper around the official java clients. Thanks. Benoit
|
Re: AWS SDK Grails Plugin
|
Hi Ben,
This looks pretty nice! Tom On Wed, Jun 13, 2012 at 9:12 AM, Benoit HEDIARD <[hidden email]> wrote:
|
|
Génial! Will be checking this out. I currently code directly to the AWS SDK, which is fine, but I'm eager to try your plugin. A wrapper like this might be useful in groovy or as a gradle plugin too for devops scripting.
Luis On Wed, Jun 13, 2012 at 11:03 AM, thomas fuller <[hidden email]> wrote: Hi Ben, |
|
If you just want to access all services provided in the AWS SDK, you can use grails-aws, since sdk lib is there. I've looked into the plugin source code, and it relies in one class (https://github.com/benorama/aws-sdk-grails-plugin/blob/master/grails-app/services/grails/plugin/awssdk/AmazonWebService.groovy). Why not add this class to grails-aws and expose the services this way there?
It would help a lot, and let end-users that just need to access AWS services directly. This will allow users that would use both plugins to declare access keys just once.
I think we should try to use only one plugin instead of having a lot of plugins trying to do the same thing. BTW, Marco Vermeuelen is already adding AWS SQS support in the grails-aws.
What do you think? []s, 2012/6/13 Luis Arias <[hidden email]> Génial! Will be checking this out. I currently code directly to the AWS SDK, which is fine, but I'm eager to try your plugin. A wrapper like this might be useful in groovy or as a gradle plugin too for devops scripting. |
|
In reply to this post by Benoit HEDIARD
Hi Benoit
Looking good, I was actually thinking about doing this my self. Where is your dependency on aws-java-sdk defined ? E.g. http://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk/1.3.10 Thanks.
Jimi
|
Re: AWS SDK Grails Plugin
|
|
Hi Jimi, It is defined in BuildConfig.groovy L.26 dependencies {
Benoit Le 14 juin 2012 à 09:42, jroenberg a écrit :
|
Re: AWS SDK Grails Plugin
|
|
In reply to this post by lucastex
Hi Lucas, I understand your point. That's a great dilemma : to DSL or not to DSL ... ;) Once you have configured it and created the clients (this is what our plugin does for you), we found the AWS SDK for Java already very easy to use. We thought that it would we great to have 2 AWS grails plugins : - one "lightweight" AWS SDK for direct java APIs access (with minimal maintenance/docs/upgrade/test), which supports ALL AWS service from scratch, - one "heavyweight" AWS with a groovy DSL/method injections for a "groovyer" access to the APIs (with heavy maintenance/docs/upgrade/test), which supports SES/S3 right now. That's two very different approach/philosophy that might not be compatible in the same plugin. But I might be wrong. Lucas, I send you an email to discuss about that. Benoit Le 13 juin 2012 à 15:48, Lucas F. A. Teixeira a écrit :
|
Re: AWS SDK Grails Plugin
|
This post has NOT been accepted by the mailing list yet.
In reply to this post by lucastex
Lucas - Do you know the ETA for getting SQS support added to the Grails-AWS plugin?
JT
jts-blog.com |
|
In reply to this post by Benoit HEDIARD
Hi
Wondering what the latest is on the aws plugins? Been looking at using IAM roles and noticed that the aws-sdk has nice support for this which grabs the aws cres from the meta data. Also been a bit annoyed with jets3et for requiring list all my buckets privileges to get a bucket.... So in short I'm planning to migrate away from jets3t to the aws-sdk and curious about what the latest is news for the aws-sdk plugin (which I'm looking forward to using). Cheers, Micke
On 14 June 2012 09:27, Benoit HEDIARD <[hidden email]> wrote:
|
Re: AWS SDK Grails Plugin
|
|
Hi, I sent two emails to Lucas (aws plugin author), but I did not get any answers. The AWS SDK plugin is ready to be released. Is it possible to get it approved? FYI, I've rename the repository for aws-sdk plugin, it is located here : Documentation is located here : Grails.org username : benorama Thanks. Ben PS: Another plugin I've released is Facebook SDK (https://github.com/benorama/grails-facebook-sdk) Le 1 juil. 2012 à 20:21, Mikael Andersson a écrit : Hi |
|
|
Hi
I've got a feature request :) From what I've read the various clients will pick up the aws credentials from the IAM role associated with an instance when the default constructor is used. Not sure how to incorporate that into the plugin but it would be great to be able to simply configure it to use the IAM provided credentials. cheers On 1 July 2012 19:37, Benoit HEDIARD <[hidden email]> wrote:
|
Re: AWS SDK Grails Plugin
|
|
Sure, I'll do a release this week with this feature. If you do not define any credentials in your grails config, it will use the default constructor which will use the following credentials : - Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_KEY - Java System Properties - aws.accessKeyId and aws.secretKey - Instance profile credentials delivered through the Amazon EC2 metadata service If you have any future requests, you might want to use the Github Issue tracker : Thanks. Ben Le 1 juil. 2012 à 23:40, Mikael Andersson a écrit : Hi |
Re: AWS SDK Grails Plugin
Administrator
|
In reply to this post by Benoit HEDIARD
Approved
On Sun, Jul 1, 2012 at 8:37 PM, Benoit HEDIARD <[hidden email]> wrote: > Hi, > > I sent two emails to Lucas (aws plugin author), but I did not get any > answers. > > The AWS SDK plugin is ready to be released. > Is it possible to get it approved? > > FYI, I've rename the repository for aws-sdk plugin, it is located here : > https://github.com/benorama/grails-aws-sdk > > Documentation is located here : > http://benorama.github.com/grails-aws-sdk/guide/ > > Grails.org username : benorama > > Thanks. > > Ben > > PS: Another plugin I've released is Facebook SDK > (https://github.com/benorama/grails-facebook-sdk) > > Le 1 juil. 2012 à 20:21, Mikael Andersson a écrit : > > Hi > > Wondering what the latest is on the aws plugins? > > Been looking at using IAM roles and noticed that the aws-sdk has nice > support for this which grabs the aws cres from the meta data. Also been a > bit annoyed with jets3et for requiring list all my buckets privileges to get > a bucket.... > > So in short I'm planning to migrate away from jets3t to the aws-sdk and > curious about what the latest is news for the aws-sdk plugin (which I'm > looking forward to using). > > Cheers, > Micke > > On 14 June 2012 09:27, Benoit HEDIARD <[hidden email]> wrote: >> >> Hi Lucas, >> >> I understand your point. >> That's a great dilemma : to DSL or not to DSL ... ;) >> Once you have configured it and created the clients (this is what our >> plugin does for you), we found the AWS SDK for Java already very easy to >> use. >> >> We thought that it would we great to have 2 AWS grails plugins : >> - one "lightweight" AWS SDK for direct java APIs access (with minimal >> maintenance/docs/upgrade/test), which supports ALL AWS service from scratch, >> - one "heavyweight" AWS with a groovy DSL/method injections for a >> "groovyer" access to the APIs (with heavy maintenance/docs/upgrade/test), >> which supports SES/S3 right now. >> That's two very different approach/philosophy that might not be compatible >> in the same plugin. >> But I might be wrong. >> >> Lucas, I send you an email to discuss about that. >> >> Benoit >> >> Le 13 juin 2012 à 15:48, Lucas F. A. Teixeira a écrit : >> >> If you just want to access all services provided in the AWS SDK, you can >> use grails-aws, since sdk lib is there. >> >> I've looked into the plugin source code, and it relies in one class >> (https://github.com/benorama/aws-sdk-grails-plugin/blob/master/grails-app/services/grails/plugin/awssdk/AmazonWebService.groovy). >> Why not add this class to grails-aws and expose the services this way there? >> >> It would help a lot, and let end-users that just need to access AWS >> services directly. >> >> This will allow users that would use both plugins to declare access keys >> just once. >> >> I think we should try to use only one plugin instead of having a lot of >> plugins trying to do the same thing. >> BTW, Marco Vermeuelen is already adding AWS SQS support in the grails-aws. >> >> What do you think? >> >> []s, >> >> Lucas Teixeira >> >> >> >> 2012/6/13 Luis Arias <[hidden email]> >>> >>> Génial! Will be checking this out. I currently code directly to the AWS >>> SDK, which is fine, but I'm eager to try your plugin. A wrapper like this >>> might be useful in groovy or as a gradle plugin too for devops scripting. >>> >>> Luis >>> >>> On Wed, Jun 13, 2012 at 11:03 AM, thomas fuller <[hidden email]> >>> wrote: >>>> >>>> Hi Ben, >>>> >>>> This looks pretty nice! >>>> >>>> Tom >>>> >>>> >>>> On Wed, Jun 13, 2012 at 9:12 AM, Benoit HEDIARD <[hidden email]> >>>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I'm ready to release AWS SDK Grails Plugin : >>>>> The AWS SDK Plugin allows your Grails application to use the Amazon Web >>>>> Services infrastructure services. >>>>> The aim is to provide a lightweight amazonWebService Grails service >>>>> wrapper around the official AWS SDK for Java. >>>>> >>>>> Username : benorama >>>>> Source : https://github.com/benorama/aws-sdk-grails-plugin >>>>> Documentation : http://benorama.github.com/aws-sdk-grails-plugin/guide/ >>>>> >>>>> It gives an easy access to the following AWS services API : >>>>> - Amazon CloudFormation >>>>> - Amazon CloudFront >>>>> - Amazon CloudSearch >>>>> - Amazon CloudWatch >>>>> - Amazon DynamoDB >>>>> - Amazon Elastic Compute Cloud (EC2) >>>>> - Amazon Elastic MapReduce >>>>> - Amazon ElastiCache >>>>> - Amazon Relational Database Service (RDS) >>>>> - Amazon Route 53 >>>>> - Amazon Simple Storage Service (S3) >>>>> - Amazon Simple Email Service (SES) >>>>> - Amazon SimpleDB >>>>> - Amazon Simple Notification Service (SNS) >>>>> - Amazon Simple Queue Service (SQS) >>>>> - Amazon Simple Workflow (SWF) >>>>> - Auto Scaling >>>>> - AWS Elastic Beanstalk >>>>> - AWS Identity & Access Management (IAM) >>>>> - AWS Import/Export >>>>> - AWS Storage Gateway >>>>> - Elastic Load Balancing >>>>> >>>>> There is another great AWS Grails plugin but it uses a different >>>>> approach and different java lib: its aim is to provide an easy "groovy" >>>>> access to SES (through a groovy DSL) and S3 (through methods injection), >>>>> based on JetS3 java lib. >>>>> If you just need basic SES or S3 features, you might give it a try. >>>>> >>>>> We decided to write our own AWS plugin because it did not meet our >>>>> requirements as we wanted:t >>>>> - to have direct access to all AWS SDK for Java features including all >>>>> AWS services, with custom client Groovy configuration, >>>>> - to only use AWS SDK for Java lib with a consistent way to access all >>>>> AWS services (and not JetS3 java lib specific methods and a custom SES DSL), >>>>> - to have 100% compatibility with future AWS SDK for Java, as it is >>>>> just a simple lightweight wrapper around the official java clients. >>>>> >>>>> Thanks. >>>>> >>>>> Benoit >>>> >>>> >>> >> >> > > -- Graeme Rocher Grails Project Lead SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
«
Return to Grails - dev
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |