<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[All things cloud by Kuldeep Chowhan - Medium]]></title>
        <description><![CDATA[All things cloud by Kuldeep Chowhan - Medium]]></description>
        <link>https://medium.com/all-things-cloud?source=rss----931708d3ed09---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>All things cloud by Kuldeep Chowhan - Medium</title>
            <link>https://medium.com/all-things-cloud?source=rss----931708d3ed09---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:26:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/all-things-cloud" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Incorporating a Startup: Delaware C-Corp, Atlas vs Clerky, and the Checklist That Saves You Later]]></title>
            <link>https://medium.com/all-things-cloud/incorporating-a-startup-delaware-c-corp-atlas-vs-clerky-and-the-checklist-that-saves-you-later-4564c2712924?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/4564c2712924</guid>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[stripe]]></category>
            <category><![CDATA[company-incorporation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Tue, 27 Jan 2026 18:36:17 GMT</pubDate>
            <atom:updated>2026-01-27T22:45:16.938Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Kuldeep Chowhan, technology executive and founder of a stealth startup; previously with Walmart and Expedia Group.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tXRwcJCAVRTGNWlacaF-Q.png" /><figcaption>Incorporating Your Startup</figcaption></figure><h3>Incorporation is not a trophy. It is an operational control.</h3><p>Most founders treat incorporation like a ceremonial step: “We formed a company. Cool. Next.”</p><p>That is how you end up with:</p><ul><li>equity that was “promised” but not actually issued,</li><li>an 83(b) deadline that quietly detonates later,</li><li>contracts signed by the wrong entity,</li><li>and compliance mail that looks official but is not.</li></ul><p>Incorporation is best understood as the moment you turn your startup from a loose collaboration into a legally consistent system. Think of it like setting up the base layer of your stack. Boring, foundational, and expensive to redo later.</p><p>This post is the playbook I wish every founder had before clicking “start company.”</p><p>(Quick note: this is not legal or tax advice. It is a founder-oriented operating guide. If you have edge cases, talk to a qualified attorney or tax pro.)</p><h3>Step 0: Should you incorporate right now?</h3><p>Incorporate now if any of these are true:</p><ul><li>You are taking outside investment soon (SAFE, note, priced round).</li><li>You are issuing equity to anyone (cofounders, early hires, advisors).</li><li>You are signing meaningful contracts (enterprise customers, manufacturing, long-term leases).</li><li>You want clean liability separation between you and the business.</li></ul><p>Wait (or at least slow down) if:</p><ul><li>You are still validating whether the idea should exist.</li><li>You have no revenue, no customers, no team, and no imminent fundraising.</li><li>You are doing a consulting-style business where an LLC might be the better fit.</li></ul><p>A practical rule: Incorporate when you need the company to own things (IP, contracts, equity) and when other people need to trust the structure.</p><h3>Step 1: Entity choice in one paragraph</h3><p>Venture-backed or venture-scale startups usually end up as a <strong>Delaware C-Corporation</strong> because investors expect it and the legal framework is predictable. Stripe Atlas explicitly positions itself around forming either a Delaware C-Corp or LLC, with the “startup default” often being the C-Corp path. (<a href="https://docs.stripe.com/atlas">Stripe Docs</a>)</p><p>LLCs can be great for cash-flow businesses and simpler ownership, but they get messy when you want standard venture financing, option plans, and lots of shareholders.</p><h3>Step 2: Delaware realities you should know (the recurring stuff)</h3><p>If you are a Delaware corporation, you have an annual rhythm:</p><ul><li><strong>Annual report and franchise tax are due by March 1</strong> for domestic corporations. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li><li>The <strong>annual report filing fee is $50</strong> for non-exempt domestic corporations. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li><li>Franchise tax has multiple calculation methods. Delaware lists <strong>minimum tax of $175</strong> under the Authorized Shares method, and <strong>$400 minimum</strong> under the Assumed Par Value Capital method. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li><li>Miss the deadline and Delaware can add penalties and interest (they list a $200 penalty for not filing the annual report on time and interest at 1.5% per month on unpaid tax). (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li></ul><p>Also, Delaware requires a <strong>registered agent</strong>. That is a real ongoing cost, not a one-time checkbox.</p><p>One more founder-saving tip: Delaware warns about <strong>deceptive solicitations</strong> that look official and ask for money to file “minutes” or “records.” Delaware calls out a specific deceptive mailer pattern on its franchise tax page. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</p><h3>Step 3: Atlas vs Clerky (the comparison founders actually need)</h3><p>There are many ways to incorporate. Two common founder-friendly paths are <strong>Stripe Atlas</strong> and <strong>Clerky</strong>.</p><h4>Stripe Atlas: the bundled “formation-to-operating” path</h4><p>Atlas pricing is <strong>$500 one-time</strong>, and Stripe lists what that includes: Delaware incorporation (with next-day expedited processing and state filing fees), EIN, founder equity issuance and share purchase, and 83(b) filing, plus templates and perks. (<a href="https://stripe.com/atlas">Stripe</a>)<br>Atlas also includes your <strong>first year of registered agent service</strong>, then lists <strong>$100 annually after your first year</strong> if you keep Atlas as your registered agent. (<a href="https://stripe.com/atlas">Stripe</a>)<br>Stripe also states clearly that Atlas is not a law firm and does not provide legal, tax, or accounting advice. (<a href="https://stripe.com/atlas">Stripe</a>)</p><p>Atlas tends to be strong when you want:</p><ul><li>speed,</li><li>fewer decisions,</li><li>a guided workflow that covers the formation basics cleanly.</li></ul><h3>Clerky: the modular startup legal paperwork workbench</h3><p>Clerky’s pricing page shows a <strong>Pay Per Use option at $427</strong> and a <strong>Company Lifetime Package at $819</strong>. (<a href="https://www.clerky.com/pricing">Clerky</a>)<br>Clerky also states they typically return the filed certificate of incorporation within <strong>2–3 business days</strong>. (<a href="https://www.clerky.com/pricing">Clerky</a>)<br>Their pricing details explicitly include Delaware expedited filing fees and the first-year registered agent fee, plus reminders. (<a href="https://www.clerky.com/pricing">Clerky</a>)</p><p>Clerky tends to be strong when:</p><ul><li>you want to “stay on rails” for startup-standard documents,</li><li>you value modularity for fundraising, hiring, and maintenance paperwork over time,</li><li>you want a system that feels like a startup legal ops toolkit.</li></ul><h3>Practical decision shortcut</h3><ul><li>Pick <strong>Atlas</strong> if you want a bundled experience: form the company, get EIN, issue founder equity, file 83(b), and move on. (<a href="https://stripe.com/atlas">Stripe</a>)</li><li>Pick <strong>Clerky</strong> if you want a modular legal-document workspace that you can keep using across more workflows. (<a href="https://www.clerky.com/pricing">Clerky</a>)</li></ul><h3>Step 4: The post-incorporation checklist (this is where founders get hurt)</h3><p>Incorporation creates the entity. It does not magically make your company “clean.” The cleanup is the work.</p><p>Here is the checklist I recommend treating as non-optional.</p><h3>A) Governance and foundational docs</h3><ul><li>Bylaws adopted (or operating agreement for LLC).</li><li>Initial board consent signed.</li><li>Officer appointments documented.</li><li>Stock ledger started (even if it is a simple cap table tool).</li></ul><h3>B) Founders’ equity issued correctly</h3><p>If you are a C-Corp, founders usually purchase restricted stock and the company issues it under board approval. Atlas explicitly includes founder equity issuance and share purchase as part of the flow. (<a href="https://stripe.com/atlas">Stripe</a>)</p><p>This matters because “we agreed 50/50 in a Google Doc” is not ownership.</p><h3>C) File 83(b) on time (seriously)</h3><p>If founders receive restricted stock (stock that vests over time), the 83(b) election is one of the most time-sensitive steps in early startup life.</p><p>The IRS states the election must be filed <strong>no later than 30 days after the transfer</strong>. (<a href="https://www.irs.gov/pub/irs-pdf/f15620.pdf?utm_source=chatgpt.com">IRS</a>)<br>Stripe’s Atlas support content also repeats the “within 30 calendar days” requirement in the startup context. (<a href="https://support.stripe.com/questions/atlas-filing-your-83%28b%29-election-using-auto-83%28b%29?utm_source=chatgpt.com">Stripe Support</a>)</p><p>Atlas advertises 83(b) election filing as included. (<a href="https://stripe.com/atlas">Stripe</a>)</p><p>Even if a service helps, you still own the risk. Make “83(b) done” a Day 1 priority, not a “later this week” task.</p><h3>D) IP assignment and invention paperwork</h3><ul><li>Founders assign relevant IP to the company.</li><li>Contractors sign invention assignment agreements.</li><li>If you used a dev shop or freelancer early, clean this up before fundraising.</li></ul><h3>E) Taxes, banking, and operational basics</h3><ul><li>EIN received (Atlas includes EIN acquisition in the workflow). (<a href="https://stripe.com/atlas">Stripe</a>)</li><li>Business bank account opened.</li><li>Bookkeeping started early enough to not hate yourself later.</li></ul><h3>F) Compliance calendar</h3><p>Put these on a recurring reminder:</p><ul><li>Delaware annual report and franchise tax deadline (March 1). (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li><li>Registered agent renewal cost.</li><li>Your “home state” obligations if you operate outside Delaware (foreign qualification often applies, and it is separate from Delaware formation).</li></ul><h3>Common incorporation mistakes, in plain language</h3><ol><li><strong>Incorporating too early<br></strong>You waste money and create compliance drag before you even know the business should exist.</li><li><strong>Not issuing equity properly<br></strong>This becomes painful when you add a cofounder, raise a SAFE, or sell the company.</li><li><strong>Missing the 83(b) window<br></strong>The IRS 30-day rule is strict. Treat it like a production outage. (<a href="https://www.irs.gov/pub/irs-pdf/f15620.pdf?utm_source=chatgpt.com">IRS</a>)</li><li><strong>Forgetting Delaware’s annual obligations<br></strong>March 1 sneaks up on founders every year. Delaware is not shy about penalties. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li><li><strong>Paying random “official-looking” mail<br></strong>Delaware literally warns you about deceptive solicitations. Assume anything that arrives by mail is guilty until proven innocent. (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li></ol><h3>A simple incorporation workflow that works</h3><p>Here’s a clean sequence that avoids most founder mistakes:</p><ol><li>Decide: Delaware C-Corp vs LLC (based on fundraising and equity plans). (<a href="https://docs.stripe.com/atlas">Stripe Docs</a>)</li><li>Choose your formation path: Atlas (bundled) or Clerky (modular). (<a href="https://stripe.com/atlas">Stripe</a>)</li><li>Incorporate and obtain EIN. (<a href="https://stripe.com/atlas">Stripe</a>)</li><li>Complete post-incorporation setup: board consent, founder equity issuance, IP assignment, cap table. (<a href="https://stripe.com/atlas">Stripe</a>)</li><li>File 83(b) within 30 days if applicable. (<a href="https://www.irs.gov/pub/irs-pdf/f15620.pdf?utm_source=chatgpt.com">IRS</a>)</li><li>Put Delaware compliance on autopilot (annual report and franchise tax by March 1). (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</li></ol><h3>What I would publish next in this series</h3><ul><li>Founder equity 101: restricted stock, vesting, cliffs, and what to pick when you have no idea</li><li>Cap tables without tears: how to avoid “spreadsheet cap table collapse”</li><li>SAFEs for founders: what actually matters in the terms</li></ul><p>Delaware franchise tax: why the default method can surprise you, and how to think about it (<a href="https://corp.delaware.gov/frtax/">Delaware Corporations Division</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4564c2712924" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/incorporating-a-startup-delaware-c-corp-atlas-vs-clerky-and-the-checklist-that-saves-you-later-4564c2712924">Incorporating a Startup: Delaware C-Corp, Atlas vs Clerky, and the Checklist That Saves You Later</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Lambda IAM Policy Templates]]></title>
            <link>https://medium.com/all-things-cloud/aws-lambda-iam-policy-templates-af3d9622ab25?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/af3d9622ab25</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kuldeep-chowhan]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Mon, 04 Jun 2018 04:20:00 GMT</pubDate>
            <atom:updated>2018-06-04T04:19:59.779Z</atom:updated>
            <content:encoded><![CDATA[<p>Reposting from <a href="https://docs.aws.amazon.com/lambda/latest/dg/policy-templates.html">https://docs.aws.amazon.com/lambda/latest/dg/policy-templates.html</a></p><p>When you create an AWS Lambda function in the console using one of the blueprints, Lambda allows you to create a role for your function from a list of Lambda policy templates. By selecting one of these templates, your Lambda function automatically creates the role with the requisite permissions attached to that policy.</p><p>The following lists the permissions that are applied to each policy template in the <strong>Policy templates</strong> list. The policy templates are named after the blueprints to which they correspond. Lambda will automatically populate the placeholder items (such as <em>region</em> and <em>accountID</em>) with the appropriate information. For more information on creating a Lambda function using policy templates, see <a href="https://docs.aws.amazon.com/lambda/latest/dg/get-started-create-function.html">Create a Simple Lambda Function</a>.</p><p>The following templates are automatically applied depending upon the type of Lambda function you are creating:</p><h3>Basic: ‘Basic Lambda Permissions’</h3><pre>{ &quot;Version&quot;:&quot;2012-10-17&quot;, &quot;Statement&quot;:[ { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:&quot;logs:CreateLogGroup&quot;, &quot;Resource&quot;:&quot;arn:aws:logs:<em>region</em>:<em>accountId</em>:*&quot; }, { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:[ &quot;logs:CreateLogStream&quot;, &quot;logs:PutLogEvents&quot; ], &quot;Resource&quot;:[ &quot;arn:aws:logs:<em>region</em>:<em>accountId</em>:log-group:[[logGroups]]:*&quot; ] } ] }</pre><h3>VPCAccess: ‘Lambda VPC Access Permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;ec2:CreateNetworkInterface&quot;, &quot;ec2:DeleteNetworkInterface&quot;, &quot;ec2:DescribeNetworkInterfaces&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>Kinesis: ‘Lambda Kinesis stream poller permissions’</h3><pre>{ &quot;Version&quot;:&quot;2012-10-17&quot;, &quot;Statement&quot;:[ { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:&quot;lambda:InvokeFunction&quot;, &quot;Resource&quot;:&quot;arn:aws:lambda:<em>region</em>:<em>accountId</em>:function:<em>functionName</em>*&quot; }, { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:&quot;kinesis:ListStreams&quot;, &quot;Resource&quot;:&quot;arn:aws:kinesis:<em>region</em>:<em>accountId</em>:stream/*&quot; }, { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:[ &quot;kinesis:DescribeStream&quot;, &quot;kinesis:GetRecords&quot;, &quot;kinesis:GetShardIterator&quot; ], &quot;Resource&quot;:&quot;arn:aws:kinesis:<em>region</em>:<em>accountId</em>: stream/<em>streamName</em>&quot; } ] }</pre><h3>DynamoDB: ‘Lambda DynamoDB stream poller permissions’</h3><pre>{ &quot;Version&quot;:&quot;2012-10-17&quot;, &quot;Statement&quot;:[ { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:&quot;lambda:InvokeFunction&quot;, &quot;Resource&quot;:&quot;arn:aws:lambda:<em>region</em>:<em>accountId</em>:function:<em>functionName</em>*&quot; }, { &quot;Effect&quot;:&quot;Allow&quot;, &quot;Action&quot;:[ &quot;dynamodb:DescribeStream&quot;, &quot;dynamodb:GetRecords&quot;, &quot;dynamodb:GetShardIterator&quot;, &quot;dynamodb:ListStreams&quot; ], &quot;Resource&quot;:&quot;arn:aws:dynamodb:<em>region</em>:<em>accountId</em>:table/<em>tableName</em>/stream/*&quot; } ] }</pre><h3>Edge: ‘Basic Edge Lambda permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;logs:CreateLogGroup&quot;, &quot;logs:CreateLogStream&quot;, &quot;logs:PutLogEvents&quot; ], &quot;Resource&quot;: [ &quot;arn:aws:logs:*:*:*&quot; ] } ] }</pre><h3>RedrivePolicySNS: ‘Dead letter queue SNS permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;sns:Publish&quot; ], &quot;Resource&quot;: &quot;arn:aws:sns:<em>region</em>:<em>accountId</em>:<em>topicName</em>&quot; } ] }</pre><h3>RedrivePolicySQS: ‘Dead letter queue SQS permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;sqs:SendMessage&quot; ], &quot;Resource&quot;: &quot;arn:aws:sqs:<em>region</em>:<em>accountId</em>:<em>queueName</em>&quot; } ] }</pre><p>The following templates are selected depending upon which blueprint you choose. You can also select them from the dropdown to add extra permissions:</p><h3>CloudFormation: ‘CloudFormation stack read-only permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;cloudformation:DescribeStacks&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>AMI: ‘AMI read-only permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;ec2:DescribeImages&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>KMS: ‘KMS decryption permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;kms:Decrypt&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>S3: ‘S3 object read-only permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;s3:GetObject&quot; ], &quot;Resource&quot;: &quot;arn:aws:s3:::*&quot; } ] }</pre><h3>Elasticsearch: ‘Elasticsearch permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;es:ESHttpPost&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>SES: ‘SES bounce permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;ses:SendBounce&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>TestHarness: ‘Test Harness permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;dynamodb:PutItem&quot; ], &quot;Resource&quot;: &quot;arn:aws:dynamodb:<em>region</em>:<em>accountId</em>:table/*&quot; }, { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;lambda:InvokeFunction&quot; ], &quot;Resource&quot;: &quot;arn:aws:lambda:<em>region</em>:<em>accountId</em>:function:*&quot; } ] }</pre><h3>Microservice: ‘Simple Microservice permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;dynamodb:DeleteItem&quot;, &quot;dynamodb:GetItem&quot;, &quot;dynamodb:PutItem&quot;, &quot;dynamodb:Scan&quot;, &quot;dynamodb:UpdateItem&quot; ], &quot;Resource&quot;: &quot;arn:aws:dynamodb:<em>region</em>:<em>accountId</em>:table/*&quot; } ] }</pre><h3>VPN: ‘VPN Connection Monitor permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;cloudwatch:PutMetricData&quot; ], &quot;Resource&quot;: &quot;*&quot; }, { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;ec2:DescribeRegions&quot;, &quot;ec2:DescribeVpnConnections&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>SQS: ‘SQS Poller permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;sqs:DeleteMessage&quot;, &quot;sqs:ReceiveMessage&quot; ], &quot;Resource&quot;: &quot;arn:aws:sqs:*&quot; }, { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;lambda:InvokeFunction&quot; ], &quot;Resource&quot;: &quot;arn:aws:lambda:<em>region</em>:<em>accountId</em>:function:<em>functionName</em>*&quot; } ] }</pre><h3>IoTButton: ‘AWS IoT Button permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;sns:ListSubscriptionsByTopic&quot;, &quot;sns:CreateTopic&quot;, &quot;sns:SetTopicAttributes&quot;, &quot;sns:Subscribe&quot;, &quot;sns:Publish&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>RekognitionNoDataAccess:’Amazon Rekognition no data permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;rekognition:CompareFaces&quot;, &quot;rekognition:DetectFaces&quot;, &quot;rekognition:DetectLabels&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>RekognitionReadOnlyAccess: ‘Amazon Rekognition read-only permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;rekognition:ListCollections&quot;, &quot;rekognition:ListFaces&quot;, &quot;rekognition:SearchFaces&quot;, &quot;rekognition:SearchFacesByImage&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><h3>RekognitionWriteOnlyAccess: ‘Amazon Rekognition write-only permissions’</h3><pre>{ &quot;Version&quot;: &quot;2012-10-17&quot;, &quot;Statement&quot;: [ { &quot;Effect&quot;: &quot;Allow&quot;, &quot;Action&quot;: [ &quot;rekognition:CreateCollection&quot;, &quot;rekognition:IndexFaces&quot; ], &quot;Resource&quot;: &quot;*&quot; } ] }</pre><p><em>Originally published at </em><a href="https://docs.aws.amazon.com/lambda/latest/dg/policy-templates.html"><em>docs.aws.amazon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af3d9622ab25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/aws-lambda-iam-policy-templates-af3d9622ab25">AWS Lambda IAM Policy Templates</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless App: AWS CloudTrail Log Analytics using Amazon Elasticsearch Service]]></title>
            <link>https://medium.com/all-things-cloud/serverless-app-aws-cloudtrail-log-analytics-using-amazon-elasticsearch-service-f4612b2103c1?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/f4612b2103c1</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Sun, 10 Dec 2017 07:21:13 GMT</pubDate>
            <atom:updated>2017-12-12T05:56:39.953Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I’m will talk about how you can build a Serverless application using <a href="https://github.com/awslabs/serverless-application-model">AWS Serverless Application Model</a> (SAM) to perform Log Analytics on AWS <a href="https://aws.amazon.com/cloudtrail/">CloudTrail</a> data using <a href="https://aws.amazon.com/elasticsearch-service/">Amazon Elasticsearch Service</a>. The AWS Serverless Application will help you analyze AWS CloudTrail Logs using Amazon Elasticsearch Service. The application creates CloudTrail trail, sets the log delivery to an s3 bucket that it creates and configures SNS delivery whenever the CloudTrail log file has been written to s3. The app also<br>creates an Amazon Elasticsearch Domain and creates an Amazon Lambda Function which gets triggered by the SNS message, get the s3 file location, read the contents from the s3 file and write the data to Elasticsearch for analytics.</p><p>I have referenced the below Github repo to write this blog post:</p><p><a href="https://github.com/ExpediaDotCom/cloudtrail-log-analytics">ExpediaDotCom/cloudtrail-log-analytics</a></p><p>Let’s learn about what is AWS CloudTrail, Elasticsearch, Amazon Elasticsearch Service, AWS Lambda and AWS SAM.</p><h4>What is AWS CloudTrail?</h4><p>AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your AWS infrastructure. CloudTrail provides event history of your AWS account activity, including actions taken through the AWS Management Console, AWS SDKs, command line tools, and other AWS services. This event history simplifies security analysis, resource change tracking, and troubleshooting.</p><p><a href="https://aws.amazon.com/cloudtrail/">API Logs - Secure Standardized Logging Service - AWS CloudTrail - AWS</a></p><h4>What is Elasticsearch?</h4><p>Elasticsearch is a distributed, RESTful search and analytics engine capable of solving a growing number of use cases. As the heart of the Elastic Stack, it centrally stores your data so you can discover the expected and uncover the unexpected.</p><p><a href="https://www.elastic.co/products/elasticsearch">Elasticsearch: RESTful, Distributed Search &amp; Analytics | Elastic</a></p><h4>What is Amazon Elasticsearch Service?</h4><p>Amazon Elasticsearch Service makes it easy to deploy, secure, operate, and scale Elasticsearch for log analytics, full text search, application monitoring, and more. Amazon Elasticsearch Service is a fully managed service that delivers Elasticsearch’s easy-to-use APIs and real-time analytics capabilities alongside the availability, scalability, and security that production workloads require.</p><p><a href="https://aws.amazon.com/elasticsearch-service/">Amazon Elasticsearch Service - Amazon Web Services</a></p><h4>What is AWS Lambda?</h4><p>AWS Lambda lets you run code without provisioning or managing servers. You pay only for the compute time you consume — there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service — all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.</p><p><a href="https://aws.amazon.com/lambda/">Serverless Function, FaaS Serverless - AWS Lambda - AWS</a></p><h4>What is AWS Serverless Application Model?</h4><p>AWS Serverless Application Model (AWS SAM) prescribes rules for expressing Serverless applications on AWS. The goal of AWS SAM is to define a standard application model for Serverless applications.</p><p><a href="https://github.com/awslabs/serverless-application-model">awslabs/serverless-application-model</a></p><p>Now let’s look at how we can build a Serverless App to perform Log Analytics on AWS CloudTrail data using Amazon Elasticsearch Service.</p><p>This is the architecture of the CloudTrail Log Analytics Serverless Application:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*dF8a4xzZuHydWjokM2Xpqw.png" /><figcaption>Architecture for Serverless Application: CloudTrail Log Analytics using Elasticsearch</figcaption></figure><p>AWS Serverless Application Model is a AWS <a href="https://aws.amazon.com/cloudformation/">Cloudformation</a> template. Before we look at the code for SAM template, let’s work on packaging our AWS Lambda.</p><p>On your workstation, create a working folder for building the Serverless Application.</p><h4>Create a file called index.py for the AWS Lambda:</h4><pre>&quot;&quot;&quot; This module reads the SNS message to get the S3 file location for cloudtrail<br> log and stores into Elasticsearch. &quot;&quot;&quot;<br><br>from __future__ import print_function<br>import json<br>import boto3<br>import logging<br>import datetime<br>import gzip<br>import urllib<br>import os<br>import traceback<br><br>from StringIO import StringIO<br>from exceptions import *<br><br># from awses.connection import AWSConnection<br>from elasticsearch import Elasticsearch, RequestsHttpConnection<br>from requests_aws4auth import AWS4Auth<br>                                <br>logger = logging.getLogger()<br>logger.setLevel(logging.INFO)<br><br>s3 = boto3.client(&#39;s3&#39;, region_name=os.environ[&#39;AWS_REGION&#39;])<br><br>awsauth = AWS4Auth(os.environ[&#39;AWS_ACCESS_KEY_ID&#39;], os.environ[&#39;AWS_SECRET_ACCESS_KEY&#39;], os.environ[&#39;AWS_REGION&#39;], &#39;es&#39;, session_token=os.environ[&#39;AWS_SESSION_TOKEN&#39;])<br>es = Elasticsearch(<br>    hosts=[{&#39;host&#39;: os.environ[&#39;es_host&#39;], &#39;port&#39;: 443}],<br>    http_auth=awsauth,<br>    use_ssl=True,<br>    verify_certs=True,<br>    connection_class=RequestsHttpConnection<br>)<br>    <br>def handler(event, context):<br>    logger.info(&#39;Event: &#39; + json.dumps(event, indent=2))<br><br>    s3Bucket = json.loads(event[&#39;Records&#39;][0][&#39;Sns&#39;][&#39;Message&#39;])[&#39;s3Bucket&#39;].encode(&#39;utf8&#39;)<br>    s3ObjectKey = urllib.unquote_plus(json.loads(event[&#39;Records&#39;][0][&#39;Sns&#39;][&#39;Message&#39;])[&#39;s3ObjectKey&#39;][0].encode(&#39;utf8&#39;))<br><br>    logger.info(&#39;S3 Bucket: &#39; + s3Bucket)<br>    logger.info(&#39;S3 Object Key: &#39; + s3ObjectKey)<br><br>    try:<br>        response = s3.get_object(Bucket=s3Bucket, Key=s3ObjectKey)<br>        content = gzip.GzipFile(fileobj=StringIO(response[&#39;Body&#39;].read())).read()<br><br>        for record in json.loads(content)[&#39;Records&#39;]:<br>            recordJson = json.dumps(record)<br>            logger.info(recordJson)<br>            indexName = &#39;ct-&#39; + datetime.datetime.now().strftime(&quot;%Y-%m-%d&quot;)<br>            res = es.index(index=indexName, doc_type=&#39;record&#39;, id=record[&#39;eventID&#39;], body=recordJson)<br>            logger.info(res)<br>        return True<br>    except Exception as e:<br>        logger.error(&#39;Something went wrong: &#39; + str(e))<br>        traceback.print_exc()<br>        return False</pre><h4>Create a file called requirements for the python packages that are needed:</h4><pre>elasticsearch&gt;=5.0.0,&lt;6.0.0<br>requests-aws4auth</pre><p>With the above requirements file created in your workspace, run the below command to install the required packages:</p><pre>python -m pip install -r requirements.txt -t ./</pre><p>Create a file called template.yaml that will store the code for AWS SAM:</p><pre>AWSTemplateFormatVersion: &#39;2010-09-09&#39;<br>Transform: &#39;AWS::Serverless-2016-10-31&#39;<br>Description: &gt;<br><br>    This SAM example creates the following resources:<br><br>      S3 Bucket: S3 Bucket to hold the CloudTrail Logs<br>      CloudTrail: Create CloudTrail trail for all regions and configures it to delivery logs to the above S3 Bucket<br>      SNS Topic: Configure SNS topic to receive notifications when the CloudTrail log file is created in s3<br>      Elasticsearch Domain: Create Elasticsearch Domain to hold the CloudTrail logs for advanced analytics<br>      IAM Role: Create IAM Role for Lambda Execution and assigns Read Only S3 permission<br>      Lambda Function:  Create Function which get&#39;s triggered when SNS receives notification, reads the contents from s3 and stores them in Elasticsearch Domain<br>Outputs:<br><br>    S3Bucket:<br>      Description: &quot;S3 Bucket Name where CloudTrail Logs are delivered&quot;<br>      Value: !Ref S3Bucket<br>    LambdaFunction:<br>      Description: &quot;Lambda Function that reads CloudTrail logs and stores them into Elasticsearch Domain&quot;<br>      Value: !GetAtt Function.Arn<br>    ElasticsearchUrl:<br>      Description: &quot;Elasticsearch Domain Endpoint that you can use to access the CloudTrail logs and analyze them&quot;<br>      Value: !GetAtt ElasticsearchDomain.DomainEndpoint<br>Resources:<br>  SNSTopic:<br>    Type: AWS::SNS::Topic<br>  SNSTopicPolicy: <br>    Type: &quot;AWS::SNS::TopicPolicy&quot;<br>    Properties: <br>      Topics: <br>        - Ref: &quot;SNSTopic&quot;<br>      PolicyDocument: <br>        Version: &quot;2008-10-17&quot;<br>        Statement: <br>          - <br>            Sid: &quot;AWSCloudTrailSNSPolicy&quot;<br>            Effect: &quot;Allow&quot;<br>            Principal: <br>              Service: &quot;cloudtrail.amazonaws.com&quot;<br>            Resource: &quot;*&quot;<br>            Action: &quot;SNS:Publish&quot;<br>  S3Bucket:<br>    Type: AWS::S3::Bucket<br>  S3BucketPolicy: <br>    Type: &quot;AWS::S3::BucketPolicy&quot;<br>    Properties: <br>      Bucket: <br>        Ref: S3Bucket<br>      PolicyDocument: <br>        Version: &quot;2012-10-17&quot;<br>        Statement: <br>          - <br>            Sid: &quot;AWSCloudTrailAclCheck&quot;<br>            Effect: &quot;Allow&quot;<br>            Principal: <br>              Service: &quot;cloudtrail.amazonaws.com&quot;<br>            Action: &quot;s3:GetBucketAcl&quot;<br>            Resource: <br>              !Sub |-<br>                arn:aws:s3:::${S3Bucket}<br>          - <br>            Sid: &quot;AWSCloudTrailWrite&quot;<br>            Effect: &quot;Allow&quot;<br>            Principal: <br>              Service: &quot;cloudtrail.amazonaws.com&quot;<br>            Action: &quot;s3:PutObject&quot;<br>            Resource:<br>              !Sub |-<br>                arn:aws:s3:::${S3Bucket}/AWSLogs/${AWS::AccountId}/*<br>            Condition: <br>              StringEquals:<br>                s3:x-amz-acl: &quot;bucket-owner-full-control&quot;<br>  CloudTrail:<br>    Type: AWS::CloudTrail::Trail<br>    DependsOn:<br>      - SNSTopicPolicy<br>      - S3BucketPolicy<br>    Properties: <br>        S3BucketName: <br>          Ref: S3Bucket<br>        SnsTopicName: <br>          Fn::GetAtt: <br>            - SNSTopic<br>            - TopicName<br>        IsLogging: true<br>        EnableLogFileValidation: true<br>        IncludeGlobalServiceEvents: true<br>        IsMultiRegionTrail: true<br>  FunctionIAMRole:<br>    Type: &quot;AWS::IAM::Role&quot;<br>    Properties:<br>        Path: &quot;/&quot;<br>        ManagedPolicyArns:<br>            - &quot;arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole&quot;<br>            - &quot;arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess&quot;<br>        AssumeRolePolicyDocument:<br>          Version: &quot;2012-10-17&quot;<br>          Statement:<br>            -<br>              Sid: &quot;AllowLambdaServiceToAssumeRole&quot;<br>              Effect: &quot;Allow&quot;<br>              Action: <br>                - &quot;sts:AssumeRole&quot;<br>              Principal:<br>                Service: <br>                  - &quot;lambda.amazonaws.com&quot;<br>  ElasticsearchDomain: <br>    Type: AWS::Elasticsearch::Domain<br>    DependsOn:<br>      - FunctionIAMRole<br>    Properties:<br>      DomainName: &quot;cloudtrail-log-analytics&quot;<br>      ElasticsearchClusterConfig: <br>        InstanceCount: &quot;2&quot;<br>      EBSOptions: <br>        EBSEnabled: true<br>        Iops: 0<br>        VolumeSize: 20<br>        VolumeType: &quot;gp2&quot;<br>      AccessPolicies: <br>        Version: &quot;2012-10-17&quot;<br>        Statement: <br>          - <br>            Sid: &quot;AllowFunctionIAMRoleESHTTPFullAccess&quot;<br>            Effect: &quot;Allow&quot;<br>            Principal: <br>              AWS: !GetAtt FunctionIAMRole.Arn<br>            Action: &quot;es:ESHttp*&quot;<br>            Resource:<br>              !Sub |-<br>                arn:aws:es:${AWS::Region}:${AWS::AccountId}:domain/cloudtrail-log-analytics/*<br>          - <br>            Sid: &quot;AllowFullAccesstoKibanaForEveryone&quot;<br>            Effect: &quot;Allow&quot;<br>            Principal: <br>              AWS: &quot;*&quot;<br>            Action: &quot;es:*&quot;<br>            Resource:<br>              !Sub |-<br>                arn:aws:es:${AWS::Region}:${AWS::AccountId}:domain/cloudtrail-log-analytics/_plugin/kibana<br>      ElasticsearchVersion: &quot;5.5&quot;<br>  Function:<br>    Type: &#39;AWS::Serverless::Function&#39;<br>    DependsOn:<br>      - ElasticsearchDomain<br>      - FunctionIAMRole<br>    Properties:<br>      Handler: index.handler<br>      Runtime: python2.7<br>      CodeUri: ./<br>      Role: !GetAtt FunctionIAMRole.Arn<br>      Events:<br>        SNSEvent:<br>          Type: SNS<br>          Properties:<br>            Topic: !Ref SNSTopic<br>      Environment:<br>        Variables:<br>          es_host:<br>            Fn::GetAtt: <br>              - ElasticsearchDomain<br>              - DomainEndpoint</pre><h4>Packing Artifacts and uploading them to s3:</h4><p>Run the following command to upload your artifacts to S3 and output a packaged template that can be readily deployed to CloudFormation.</p><pre>aws cloudformation package \<br>    --template-file template.yaml \<br>    --s3-bucket bucket-name \<br>    --output-template-file serverless-output.yaml</pre><h4>Deploying this AWS SAM to AWS CloudFormation:</h4><p>You can use aws cloudformation deploy CLI command to deploy the SAM template. Under-the-hood it creates and executes a changeset and waits until the deployment completes. It also prints debugging hints when the deployment fails. Run the following command to deploy the packaged template to a stack called cloudtrail-log-analytics:</p><pre>aws cloudformation deploy \<br>    --template-file serverless-output.yaml \<br>    --stack-name cloudtrail-log-analytics \<br>    --capabilities CAPABILITY_IAM</pre><p>Refer to the <a href="http://docs.aws.amazon.com/cli/latest/reference/cloudformation/deploy/index.html">documentation</a> for more details.</p><blockquote>I recommend reading about Elasticsearch Service Access Policies using the <a href="http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-createupdatedomains.html#es-createdomain-configure-access-policies">documentation</a> and modify the Access policy of the Elasticsearch domain to further fine tune the access policy.</blockquote><p>Once the Serverless application is deployed in your AWS account, It will automatically store the AWS CloudTrail data into Amazon Elasticsearch Service as soon as the log is delivered to s3. With the data in Elasticsearch, you can use Kibana to visualize the data in Elasticsearch and create the dashboards that you need on the AWS CloudTrail data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4612b2103c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/serverless-app-aws-cloudtrail-log-analytics-using-amazon-elasticsearch-service-f4612b2103c1">Serverless App: AWS CloudTrail Log Analytics using Amazon Elasticsearch Service</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chaos Engineering using Amazon EC2 Systems Manager]]></title>
            <link>https://medium.com/all-things-cloud/chaos-engineering-using-amazon-ec2-systems-manager-f0c9eee81dd3?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/f0c9eee81dd3</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[chao]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Tue, 25 Apr 2017 17:48:25 GMT</pubDate>
            <atom:updated>2017-04-25T17:48:24.613Z</atom:updated>
            <content:encoded><![CDATA[<h3>Background</h3><p>I have been looking at tools on how can chaos be introduced into applications (Chaos Engineering) so that I can test whether applications are resilient. As I was exploring different tools, I explored the idea of why can’t I leverage Amazon EC2 Systems Manager suite of tools that are already available in AWS to introduce chaos for the applications.</p><h4>What Is Amazon EC2 Systems Manager?</h4><p>Amazon EC2 Systems Manager is a collection of capabilities that helps you automate management tasks such as collecting system inventory, applying operating system patches, automating the creation of Amazon Machine Images (AMIs), and configuring operating systems and applications at scale. Systems Manager lets you remotely and securely manage the configuration of your managed instances.</p><p>More Info at: <a href="http://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html">http://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html</a></p><p>With this idea in mind, I started to look at all the different ways that I can introduce chaos and look at what tools can I use that EC2 already has instead of building my own tool.</p><p>These are the tools that are part of Amazon Systems Manager that I picked to perform Chaos Engineering</p><ol><li>SSM Document</li><li>Run Command</li></ol><h4>What is SSM Document?</h4><p>An Amazon EC2 Systems Manager Document defines the actions that Systems Manager performs on your managed instances. Systems Manager includes more than a dozen pre-configured documents that you can use by specifying parameters at runtime. Documents use JavaScript Object Notation (JSON), and they include steps and parameters that you specify. Steps execute in sequential order.</p><p>More info at: : <a href="http://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-ssm-docs.html">http://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-ssm-docs.html</a></p><h4>What is Run Command?</h4><p>Systems Manager Run Command lets you remotely and securely manage the configuration of your managed instances. A <em>managed instance</em> is any Amazon EC2 instance or on-premises machine in your hybrid environment that has been configured for Systems Manager. Run Command enables you to automate common administrative tasks and perform ad hoc configuration changes at scale. You can use Run Command from the EC2 console, the AWS Command Line Interface, Windows PowerShell, or the AWS SDKs.</p><p>More info at: <a href="https://aws.amazon.com/ec2/run-command/">https://aws.amazon.com/ec2/run-command/</a></p><h3>Setup Walkthrough</h3><p>Let’s walkthrough the setup that is required for us to run the Chaos Engineering Experiment</p><h4>Setting Up Systems Manager</h4><p>To get started with Amazon EC2 Systems Manager, verify prerequisites, configure AWS Identity and Access Management (IAM) roles, and install the SSM Agent on managed instances.</p><p>This document talks about how to configure the IAM roles and the installation steps for SSM Agent: <a href="http://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-setting-up.html">http://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-setting-up.html</a></p><p>Using the above the steps, install the SSM Agent on Amazon Linux EC2 instances on which you want to perform the Chaos Experiment.</p><h4>Create SSM Document</h4><p>We will create a SSM Document to run our different Chaos Engineering experiments. Let’s start with creating one document to Blackhole an instance on a specified port for a specified amount of time. I will follow up with additional blog posts with different SSM Document templates to perform different Chaos Engineering experiments.</p><p>This page talks about how you can create a SSM Document: <a href="http://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-doc.html">http://docs.aws.amazon.com/systems-manager/latest/userguide/create-ssm-doc.html</a></p><p>For our use case of Blackhole a port on an instance, you will create the Document using the below information:</p><p><strong>Name:</strong> Chaos-Blackhole</p><p><strong>Document Type:</strong> Command</p><p><strong>Content:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/209bf1c669a4dd5aa8ac53ecc666c8a2/href">https://medium.com/media/209bf1c669a4dd5aa8ac53ecc666c8a2/href</a></iframe><p>As you can see above, I using aws:runShellScript action to execute commands on the instance to Blackhole a port on the instance. Let’s walkthrough the commands that I’m using.</p><p>iptables -A INPUT -p tcp — destination-port {{ port }} -j DROP</p><p>Adds a iptables rule to drop the packets on the specified port</p><p>sleep {{ duration }}</p><p>Waits for the specified duration</p><p>iptables -D INPUT -p tcp — destination-port {{ port }} -j DROP</p><p>Deletes the iptable rule to drop the packets on the specified port</p><blockquote>Port and Duration are both parameters to the Document and these parameters are filled with values when the Run Command is executed.</blockquote><h3>Run Chaos Engineering Experiment</h3><p>Now that the Systems Manager Agent is installed on an EC2 instance and SSM Document is created it is time to run our Chaos Engineering Experiment, let’s look at how to run the Chaos Blackhole experiment. For our experiment we will install nginx on an EC2 instance which has SSM Agent installed and will run our Chaos Experiment to Blackhole port 80 which nginx uses on the instance. When the experiment is running, we should be unable to access nginx on that instance via browser on port 80. If we are unable to access the port 80 on the instance via browser then it means that the experiment is successful.</p><h4>Preparing EC2 instance for our Chaos Engineering Experiment</h4><ol><li>SSH to the instance on which you have installed the SSM Agent</li><li>Install nginx by running the command yum install nginx -y</li><li>Start nginx by running the command service nginx restart</li><li>Verify that nginx is running on the instance by running curl <a href="http://localhost/">http://localhost</a> and see if you get response back</li></ol><h4>Running the experiment</h4><p>Now that the EC2 instance has nginx running on port 80, we can run our Chaos Blackhole experiment and see if our experiment succeeds. For this walkthrough I’m using AWS Management console, however all the steps that I have mentioned in the document can be run using AWS CLI or AWS SDK.</p><ul><li>Navigate to AWS Console and select EC2 service from the list of services. In the EC2 dashboard, select <strong>Run Command</strong> from the menu on the left hand side</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*nPGgAUmNCLKx4AlhhLAgdg.png" /><figcaption>Run Command</figcaption></figure><ul><li>In the commands window, click on Run a command button</li><li>In the Run a command window, filter the available commands to Owned by me and select Chaos-Blackhole document</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*U0g9avLn7QwZ_KKm4nAEZA.png" /><figcaption>Selecting Chaos-Blackhole Document from the list</figcaption></figure><ul><li>From the Target instances select the instance on which you have configured SSM Agent</li><li>Enter 80 as port number to blackhole</li><li>Enter 30 seconds as the duration to blackhole</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*2X2jWqzcAORgxJuxHa9_qA.png" /></figure><ul><li>After you have filled in these details you can click on the Run button in the bottom to start our experiment</li><li>Before the experiment I was able to access nginx via the browser</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ADD4oum_IrfVZqoSHRGqXw.png" /></figure><ul><li>During the experiment, when i tried to hit the ip of the EC2 instance from the browser, it stop responding and the wheel kept spinning</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Hs4yve2OMqQTeIWeWBg6Ag.png" /><figcaption>Nginx was not accessible during the execution of the run command</figcaption></figure><ul><li>Once the Run command execution is complete, I was able to access nginx via browser without any issues</li><li>You can also look at the status of the Run command in the Command list window</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*OP4K7I6ueIZeVGH2gXVkaw.png" /><figcaption>Run Command Execution</figcaption></figure><ul><li>By leveraging EC2 Systems Manager I was able to successfully run Chaos Engineering Experiment of Blackhole a port on an instance.</li></ul><h3>Next Steps</h3><p>In the subsequent blog posts, I will provide examples on other Chaos Experiments that you can run on your EC2 instances to see how resilient your applications are.</p><p>Feel free to provide feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0c9eee81dd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/chaos-engineering-using-amazon-ec2-systems-manager-f0c9eee81dd3">Chaos Engineering using Amazon EC2 Systems Manager</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gone in 60 milliseconds: Protect your AWS Lambda]]></title>
            <link>https://medium.com/all-things-cloud/gone-in-60-milliseconds-protect-your-aws-lambda-3fd96a950eea?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/3fd96a950eea</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Tue, 03 Jan 2017 14:35:42 GMT</pubDate>
            <atom:updated>2017-01-04T01:55:37.069Z</atom:updated>
            <content:encoded><![CDATA[<p>More and more businesses are moving from monolithic servers and turning to event-driven microservices powered by cloud function providers like AWS Lambda aka Serverless Computing. So, how can they be hacked if they only exists for <em>60 milliseconds</em>?</p><p>I came across a talk about hacking AWS Lambda which will show novel attack vectors using cloud event sources, exploits in common Serverless patterns and frameworks, abuse of undocumented features in AWS Lambda for persistent malware injection, identifying valuable targets for pilfering, and, of course, how to exfiltrate juicy data out of a secure Virtual Private Cloud.</p><p><a href="https://media.ccc.de/v/33c3-7865-gone_in_60_milliseconds">Gone in 60 Milliseconds</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAAIkNbPwTRM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAAIkNbPwTRM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAAIkNbPwTRM%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d8143c3dcfc1e9ba7ebfd6c93efd9bee/href">https://medium.com/media/d8143c3dcfc1e9ba7ebfd6c93efd9bee/href</a></iframe><p>Even though the talk is about hacking AWS Lambda, it does provide insights on how you can protect your AWS Lambda based on the methods hackers are trying to exploit AWS Lambda.</p><p>My takeaways:</p><ol><li>Serverless or not — writing secure code is very important</li><li>Ensure that only required (least) permissions are granted to the IAM role used by your AWS Lambda</li><li>Protect your API Gateway with a key</li></ol><p>Add your takeaways in comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fd96a950eea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/gone-in-60-milliseconds-protect-your-aws-lambda-3fd96a950eea">Gone in 60 milliseconds: Protect your AWS Lambda</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS X-Ray: Distributed Tracing in minutes]]></title>
            <link>https://medium.com/all-things-cloud/aws-x-ray-distributed-tracing-in-minutes-849c4070cd97?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/849c4070cd97</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Sun, 11 Dec 2016 02:15:11 GMT</pubDate>
            <atom:updated>2016-12-11T02:26:01.402Z</atom:updated>
            <content:encoded><![CDATA[<p>AWS X-Ray helps developers analyze and debug production, distributed applications, such as those built using a microservices architecture. With X-Ray, you can understand how your application and its underlying services are performing to identify and troubleshoot the root cause of performance issues and errors. X-Ray provides an end-to-end view of requests as they travel through your application, and shows a map of your application’s underlying components. You can use X-Ray to analyze both applications in development and in production, from simple three-tier applications to complex microservices applications consisting of thousands of services.</p><h4>How does X-Ray work?</h4><p>X-Ray captures trace data from code running on EC2 instances (including ECS containers), <a href="https://aws.amazon.com/elasticbeanstalk/">AWS Elastic Beanstalk</a>, <a href="http://aws.amazon.com/apigateway">Amazon API Gateway</a>, and more. It implements follow-the-thread tracing by adding an HTTP header (including a unique ID) to requests that do not already have one, and passing the header along to additional tiers of request handlers. The data collected at each point is called a segment, and is stored as a chunk of JSON data. A segment represents a unit of work, and includes request and response timing, along with optional sub-segments that represent smaller work units (down to lines of code, if you supply the proper instrumentation). A statistically meaningful sample of the segments are routed to X-Ray (a daemon process handles this on EC2 instances and inside of containers) where it is assembled into <strong>traces</strong> (groups of segments that share a common ID). The traces are segments are further processed to create <strong>service maps</strong> that visually depict the relationship of services to each other.</p><h4>Supported programing languages</h4><p>You can instrument the following programming languages using X-Ray:</p><ul><li>Node.js</li><li>Java</li><li>C# .Net</li></ul><h4>Walkthrough</h4><p>I will walkthrough how you can instrument your existing Node.js application with AWS X-Ray to capture http calls and all AWS SDK calls. I will also walkthrough how to setup X-Ray daemon in a docker image so that it can capture the data and send to AWS X-Ray</p><h4>Instrument and run your application</h4><p>The AWS X-Ray SDK for Node.js provides middleware that you can use to instrument incoming HTTP requests. This walkthrough uses Express.</p><ul><li>Add <strong><em>aws-xray-sdk</em></strong> to your package.json using npm</li></ul><pre>npm install --save aws-xray-sdk</pre><ul><li>In your application initialize the x-ray SDK and use it prior to declaring your routes by calling openSegment()</li></ul><pre>// Initialize X-ray SDK<br>const XRay = require(&#39;aws-xray-sdk&#39;);</pre><pre>// Initialize an instance of Express<br>const app = express();</pre><pre>// Start capturing the calls in the applications<br>app.use(XRay.express.openSegment());</pre><ul><li>After the all the routes have been defined, stop capturing the calls in your application by calling the closeSegment()</li></ul><pre>app.use(&#39;/&#39;, routes);</pre><pre>app.use(XRay.express.closeSegment());</pre><ul><li>You can instruct X-Ray to capture all http/https wrapping captureHTTPs around http package</li></ul><pre>const http = require(&#39;http&#39;);<br>XRay.captureHTTPs(http);</pre><ul><li>You can instruct X-Ray to capture all AWS SDK calls by wrapping captureAWS around aws-sdk package</li></ul><pre>const AWS = captureAWS(require(&#39;aws-sdk&#39;));</pre><ul><li>If you are running in AWS either on ECS (EC2 Container Service) or EC2 instance, X-ray can capture the ECS container ID or EC2 instance data. You can capture it by enabling X-Ray plugin</li></ul><pre>const XRay = require(&#39;aws-xray-sdk&#39;);</pre><pre>// Enable EC2 plugin<br>XRay.config([AWSXRay.plugins.EC2]);</pre><pre>// Enable ECS plugin<br>XRay.config([AWSXRay.plugins.ECS]);</pre><p>This is all the work that is needed on the application side to start instrumenting the application using X-Ray.</p><p>The below page has lot more examples on how you can configure your Node.js application to instrument further:</p><p><a href="https://www.npmjs.com/package/aws-xray-sdk">aws-xray-sdk</a></p><p>Let’s walkthrough what needs to be done so that you can capture the traces and send to AWS X-Ray</p><h4>Run the AWS X-Ray Daemon</h4><p>The AWS X-Ray SDK does not send trace data directly to AWS X-Ray. To avoid calling the service every time your application serves a request, the SDK sends the trace data to a daemon, which collects segments for multiple requests and uploads in batches. Run the daemon alongside your application.</p><p>Let’s walkthrough what you need to do to setup and run the x-ray daemon in a docker image.</p><ul><li>Add the below instructions to your Dockerfile</li></ul><pre># Download the x-ray daemon from s3<br>RUN curl https://s3.dualstack.us-west-2.amazonaws.com/aws-xray-assets.us-west-2/xray-daemon/aws-xray-daemon-linux-1.x.zip -o ./aws-xray-daemon-linux-1.x.zip</pre><pre># unzip the archive file<br>RUN unzip -o aws-xray-daemon-linux-1.x.zip -d .</pre><ul><li>As you need to run the daemon as a background process, I suggest you add running the x-ray daemon in background process in the Docker entrypoint script</li><li>Add the below instructions to your docker entrypoint script</li></ul><pre>xray -f /var/log/xray.log &amp;</pre><ul><li>Now build the docker image and push the image to your docker registry so that ECS can pick up your service</li></ul><h4>X-Ray Console</h4><p>X-Ray is still in preview, make sure you sign up for preview so that AWS can send you the link to X-Ray console when they have selected to participate in the preview.</p><p>Once you have access to the console you can navigate to the X-Ray console in that region.</p><p>e.g: For us-west-2 <a href="https://us-west-2.console.aws.amazon.com/xray">https://us-west-2.console.aws.amazon.com/xray</a> will be the console.</p><p>Once you are in the console you can view your service in the Service Map section.</p><p><strong>Service Map</strong> will look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*vdbcxZgtRkBESeRdFE8QQA.png" /><figcaption>AWS X-Ray Service Map in the console</figcaption></figure><p>Selecting a particular Service will lead you to <strong>Traces</strong> section or you can directly go to the Traces section</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*FMGkUveyBIR0xGyNp6hMlw.png" /><figcaption>AWS X-Ray Traces in the console</figcaption></figure><p>After spending 15 minutes, I have distributed tracing for my Node.js application.</p><p>You can find more information about AWS X-Ray at:</p><ul><li><a href="https://aws.amazon.com/xray/">Debug Tool - AWS X-Ray - AWS</a></li><li><a href="https://aws.amazon.com/blogs/aws/aws-x-ray-see-inside-of-your-distributed-application/">AWS X-Ray - See Inside of Your Distributed Application | AWS Blog</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=849c4070cd97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/aws-x-ray-distributed-tracing-in-minutes-849c4070cd97">AWS X-Ray: Distributed Tracing in minutes</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Container Predictions: 2017]]></title>
            <link>https://medium.com/all-things-cloud/container-predictions-2017-fc43d4c9bec6?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc43d4c9bec6</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Sat, 10 Dec 2016 02:58:44 GMT</pubDate>
            <atom:updated>2017-02-17T01:59:53.241Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2016 we did see Containers adoption increase across lot of companies, with that continued momentum I see the below things happen in 2017.</p><h4><strong>Rise of managed Docker Clouds</strong></h4><p>Managed Docker Clouds like <a href="https://aws.amazon.com/ecs/">Amazon EC2 Container Service</a>, and <a href="https://cloud.google.com/container-engine/">Automated Container Management on Google Cloud Platform</a> adoption will continue to rise to be more managed with end to end cluster management and orchestration solutions. Sure, you can use open source Docker cluster management solutions of Apache Mesos and Kubernetes, however there is lot of time and energy that is being spent managing Docker Clusters and as more more workloads become dockerized the main of managing these clusters increases as well.</p><h4><strong>ServerLess on Containers</strong></h4><p>As more and more workload move towards ServerLess, I expect the more and more platforms come out next year which will enable running ServerLess application to be run on Container clusters.</p><h4><strong>Rise of Security solutions for Containers</strong></h4><p>Security for containers is one of the key areas of concern and I expect lot of security solutions come out next year to solve these concerns. Security vulnerabilities, network security and signing of the images are some of the key areas where I expect tools to evolve next year.</p><h4><strong>Open Source Container Cluster War</strong></h4><p>I expect Kubernetes to be clear winner next year among the 3 open source (Kubernetes, Mesos and Docker Swarm) container cluster managements solutions</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc43d4c9bec6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/container-predictions-2017-fc43d4c9bec6">Container Predictions: 2017</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Organizations, Now in Preview]]></title>
            <link>https://medium.com/all-things-cloud/aws-organizations-now-in-preview-6c1223a05a54?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/6c1223a05a54</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 09:08:37 GMT</pubDate>
            <atom:updated>2016-11-30T09:08:37.300Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>AWS Organizations makes it easier for IT teams to manage multiple AWS accounts. You can use Organizations to create groups of AWS accounts, and then apply policies to these groups to help centrally manage security and automation settings.</blockquote><p>Organizations helps improve security by helping to control which AWS services can be accessed by users in individual AWS accounts. If Organizations specifies tighter controls than the <a href="https://aws.amazon.com/iam/">AWS Identity and Access Management (IAM)</a> policies for the account, then users will be held to the more restrictive Organizations policy. Organizations enables you to automate new account creation by using APIs to create and add new accounts to a group. Organizations also includes the features of <a href="http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html">Consolidated Billing</a>, automatically linking accounts in your organization so they are paid for using a single payment method.</p><p>With Organizations, you can more easily manage your AWS accounts at scale by application, environment, team, or any other grouping that makes sense for your business.</p><p>To learn more visit the <a href="https://aws.amazon.com/organizations/">AWS Organizations home page</a> and sign up for the AWS Organizations Preview today.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8VKMrkKXu2w%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8VKMrkKXu2w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8VKMrkKXu2w%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b8815d97a27a8903f573528c1906e93/href">https://medium.com/media/4b8815d97a27a8903f573528c1906e93/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c1223a05a54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/aws-organizations-now-in-preview-6c1223a05a54">AWS Organizations, Now in Preview</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Database Migration Service]]></title>
            <link>https://medium.com/all-things-cloud/aws-database-migration-service-87cca2810e7a?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/87cca2810e7a</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[big-data]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 03:21:04 GMT</pubDate>
            <atom:updated>2016-03-21T03:21:04.077Z</atom:updated>
            <content:encoded><![CDATA[<p>AWS Database Migration Service</p><p>AWS made Database Migration Service generally available last week. With the service you can migrate any database to AWS with zero downtime, you can migrate between different databases platforms.</p><p><a href="https://aws.amazon.com/dms">AWS Database Migration Service</a></p><p>You can also see my quote about the service on the same page.</p><p><a href="http://aws.amazon.com/dms/testimonials/">AWS Database Migration Service Customer Testimonials</a></p><blockquote>Expedia, Inc. is one of the world’s leading travel companies, helping millions of travelers per month easily plan and book travel. “We are in the process of migrating some databases to Amazon Aurora,” said Kuldeep Chowhan, Principal Engineer, Expedia, Inc. “The ease by which we can do this using the AWS Database Migration Service has simplified this process for us and enabled us to accelerate our migration efforts. The ability to closely monitor the process, the detailed logging feature, and the support we received from AWS have given us a great deal of confidence in a successful migration.”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87cca2810e7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/aws-database-migration-service-87cca2810e7a">AWS Database Migration Service</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Docker Cloud]]></title>
            <link>https://medium.com/all-things-cloud/announcing-docker-cloud-98e891203190?source=rss----931708d3ed09---4</link>
            <guid isPermaLink="false">https://medium.com/p/98e891203190</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Kuldeep Chowhan]]></dc:creator>
            <pubDate>Wed, 02 Mar 2016 06:26:50 GMT</pubDate>
            <atom:updated>2016-03-02T06:26:50.146Z</atom:updated>
            <content:encoded><![CDATA[<p>Today Docker announced Docker Cloud which is the name of the new cloud service by Docker that expands on the features of Tutum, brings a tighter integration with Docker Hub, and provides new updates and fixes.</p><p>In many ways, <a href="http://cloud.docker.com/">Docker Cloud</a> is the manifestation of the generally available Tutum that users have been clamoring for, but Docker Cloud is much more than that. Over the past few months our team has been hard at work building native integration with Docker Hub, Docker ID (the new shared account system across all Docker services), <a href="https://docs.docker.com/docker-hub/official_repos/">Docker official repositories</a>, commercially supported Docker Engine (CS Engine), and adding a <a href="http://forums.docker.com/">new forum</a> for all Docker Cloud discussions.</p><p><a href="http://cloud.docker.com/">Docker Cloud</a> is where developers and IT ops meet to build, ship and run any application, anywhere.</p><p>More details at: <a href="https://blog.docker.com/2016/03/announcing-docker-cloud/">https://blog.docker.com/2016/03/announcing-docker-cloud/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98e891203190" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-things-cloud/announcing-docker-cloud-98e891203190">Announcing Docker Cloud</a> was originally published in <a href="https://medium.com/all-things-cloud">All things cloud by Kuldeep Chowhan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>