title: AWS RDS event subscription with lambda in another account
body: <p>I am trying to get lambda in another account to get it invoked by RDS instance event notifications. 
  RDS event subscription is set to invoke SNS topic which triggers lambda in other account.</p>
  
  <p>I have setup an entire stack using cloudformation. Things I achieved so far are</p>
  
  <ol>
  <li>RDS events are able to invoke SNS topic, I have tested it using creating email subscription to SNS topic</li>
  <li>SNS topic is able to trigger lambda in another account. I have tested it using publish messages in SNS topic. I can see that is flowing through in cloudwatch logs.</li>
  </ol>
  
  <p>Part I am not able to get working is, RDS events triggering SNS and then Lamba in other account. Its very strage as individual bits are working fine but not end to end. Other observation is status of the SNS subscription in RDS events is shown as Active and I can see subscription log in lambda but nothing happens after I reboot RDS instance to test.</p>
  
  <p>Also, I see this bizzare behaviour that subscription status is set to Null.</p>
  
  <p><a href="https://i.stack.imgur.com/wLU8r.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/wLU8r.png" alt="enter image description here"></a></p>
  
  <p>I followed below links for reference
  <a href="https://jimmythompson.co.uk/blog/sns-and-lambda/" rel="nofollow noreferrer">https://jimmythompson.co.uk/blog/sns-and-lambda/</a>
  <a href="https://medium.com/pablo-perez/infrastructure-as-a-code-should-not-be-imperative-43d9a64e3998" rel="nofollow noreferrer">https://medium.com/pablo-perez/infrastructure-as-a-code-should-not-be-imperative-43d9a64e3998</a></p>
  
  <p>Is there something I am missing? Any help is much appreciated.</p>