title: Lambda trigger doesn't replicate to SQS source across accounts
body: <p>I'm trying to add an SQS as a source/trigger to a lambda.  I can do this just fine if both components reside within the same account.  When I add the trigger to the lambda, the lambda trigger configuration replicates over to the SQS queue to pair the two.</p>
  <p>When I try this same thing on my lambda when the SQS is remote in a different account the Lambda trigger is established, but when viewing the remote SQS it doesn't show a trigger configured.  This seems to result in the trigger not working on the lambda when a message is added to the queue.  The SQS policy on the remote queue is also giving permissions explicitly to the other account as well.</p>
  <p>Any thoughts?</p>