camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Ford (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.
Date Fri, 25 Mar 2011 17:41:06 GMT


Mark Ford commented on CAMEL-3476:

I don't think you need two sets of credentials. Assume that User-1 creates the topic. If User-2
wishes to subscribe to the topic, then they need to create the route with the appropriate
URI that includes the ARN of the topic. The newly created SQS queue will be owned by User-2
and not require the credentials for User-1. The permissions on the newly created queue are
configured to allow the messages from the topic ARN to arrive.

*Note: I have not tested with multiple AWS accounts.*

One assumption is that the topic setup by User-1 is configured to allow User-2 to subscribe.
This may be done a number of ways through the admin console. I could see where it would be
nice for the component to configure the topic permissions during the creation of the topic.
Perhaps this is something the producer could do.

In either case, I don't see needing multiple credentials here.

> Contribute camel-sns component to the new camel-aws component.
> --------------------------------------------------------------
>                 Key: CAMEL-3476
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>    Affects Versions: 2.6.0
>            Reporter: Mark Ford
>            Assignee: Christian Müller
>            Priority: Minor
>             Fix For: 2.8.0
>         Attachments: camel-aws-3476.txt, patchfile.txt, patchfile.txt
> CAMEL-3468 contributes a new component for interacting with the Amazon SQS service. The
camel-sns component allows users to publish/subscribe to topics on Amazon's Simple Notification
> This code is currently hosted as a google code project here:
> I'll coordinate with Tracy (developer of camel-aws) in the creation of the patch.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message