<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[RSS Feed]]></title><description><![CDATA[RSS Feed]]></description><link>http://direct.ecency.com</link><image><url>http://direct.ecency.com/logo512.png</url><title>RSS Feed</title><link>http://direct.ecency.com</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 06 May 2026 15:30:19 GMT</lastBuildDate><atom:link href="http://direct.ecency.com/created/cloud-formation/rss.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Why Cloudformation template is preferred over boto3 to provision infrastructure in AWS?]]></title><description><![CDATA[1. Zero cost. There is no cost for using the CloudFormation template to provision resources. On the other hand, if the resources are provisioned using boto3 in lambda, execution does cost money. Even if]]></description><link>http://direct.ecency.com/cloud/@amirdhagopal/why-cloudformation-template-is-preferred-over-boto3-to-provision-infrastructure-in-aws</link><guid isPermaLink="true">http://direct.ecency.com/cloud/@amirdhagopal/why-cloudformation-template-is-preferred-over-boto3-to-provision-infrastructure-in-aws</guid><category><![CDATA[cloud]]></category><dc:creator><![CDATA[amirdhagopal]]></dc:creator><pubDate>Thu, 26 Dec 2019 14:15:18 GMT</pubDate></item></channel></rss>