title: Adding VPC Peering Routes in CloudFormation across different AWS Accounts
body: <p>Using this <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/peer-with-vpc-in-another-account.html" rel="nofollow noreferrer">AWS walkthrough</a>, I can successfully add a vpc peering connection between different aws accounts.</p>
  
  <p>The connection is accepted automagically because of the IAM role setup in the accepter account is given that permission and referenced in the requester account when requesting the connection.</p>
  
  <p>That's all fine and good, but without route table entries in both VPC's, this connection is meaningless.</p>
  
  <p>Looking at the second template in the example; the one that creates the <code>AWS::EC2::VPCPeeringConnection</code>, is there a way to add a route in the route table entry of the VPC created in the first template?</p>
  
  <p>I can of course pass the route table id to the second template, but I don't think this is enough.  I think there must be an additional trust relationship between the accounts that would allow this.</p>
  
  <p>Any idea on how to do that?</p>