<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API Gateway on Technology Enlightened</title>
    <link>https://pprakash.me/tags/api-gateway/</link>
    <description>Recent content in API Gateway on Technology Enlightened</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>&amp;copy; &lt;a href=&#34;https://github.com/p-prakash/&#34;&gt;Prakash P&lt;/a&gt; 2015 - 2023</copyright>
    <lastBuildDate>Fri, 27 Nov 2015 09:57:13 +0000</lastBuildDate>
    <atom:link href="https://pprakash.me/tags/api-gateway/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automated cross account DNS management through CFN and API access through API gateway</title>
      <link>https://pprakash.me/tech/2015/11/27/automated-cross-account-dns-management-through-cfn-and-api-access-through-api-gateway/</link>
      <pubDate>Fri, 27 Nov 2015 09:57:13 +0000</pubDate>
      <guid>https://pprakash.me/tech/2015/11/27/automated-cross-account-dns-management-through-cfn-and-api-access-through-api-gateway/</guid>
      <description>&lt;p&gt;It’s a general best practice to manage all DNS entries in Route53 in a centralized AWS account. In that case it is difficult to automate the DNS record creation/deletion based on resources created in another AWS account using CloudFormation. CloudFormation doesn’t yet have the capability to create resources in a different AWS account.&lt;/p&gt;&#xA;&lt;p&gt;Combining IAM role delegation, AWS Lambda &amp;amp; CFN Custom resources provides us a solution. I have extended the same solution by exposing the Lambda function through API gateway which provides a powerful mechanism. The illustration give below explains the solution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
