<?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[Cloudaholics - Medium]]></title>
        <description><![CDATA[All things cloud computing - Medium]]></description>
        <link>https://medium.com/cloudaholics?source=rss----d497ec070e2a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Cloudaholics - Medium</title>
            <link>https://medium.com/cloudaholics?source=rss----d497ec070e2a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:51:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/cloudaholics" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Deeplens IAM Roles Cloudformation Template]]></title>
            <link>https://medium.com/cloudaholics/deeplens-iam-roles-cloudformation-template-bf632dbc6bb5?source=rss----d497ec070e2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf632dbc6bb5</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloudformation]]></category>
            <category><![CDATA[deeplens]]></category>
            <dc:creator><![CDATA[Derek Higgins]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 01:46:56 GMT</pubDate>
            <atom:updated>2018-01-07T01:43:34.756Z</atom:updated>
            <content:encoded><![CDATA[<p>If you where lucky enough to get a DeepLens at Re:Invent this year, you have to create several roles to get started on registering your device. To make it quicker and a little easier to get these setup I wrote a quick Cloudformation template that you can find here : <a href="https://github.com/cloudaholics/DeepLensIamRolesCloudFormation">https://github.com/cloudaholics/DeepLensIamRolesCloudFormation</a></p><p>Have fun building awesome apps with this new Device</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf632dbc6bb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudaholics/deeplens-iam-roles-cloudformation-template-bf632dbc6bb5">Deeplens IAM Roles Cloudformation Template</a> was originally published in <a href="https://medium.com/cloudaholics">Cloudaholics</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recovering ssh password on your AWS Deeplens]]></title>
            <link>https://medium.com/cloudaholics/recovering-ssh-password-on-your-aws-deeplens-fc4fea32af13?source=rss----d497ec070e2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc4fea32af13</guid>
            <category><![CDATA[aws-deeplens]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[deeplens]]></category>
            <dc:creator><![CDATA[Derek Higgins]]></dc:creator>
            <pubDate>Tue, 26 Dec 2017 05:01:59 GMT</pubDate>
            <atom:updated>2017-12-26T05:01:59.085Z</atom:updated>
            <content:encoded><![CDATA[<p>If you were like me and excited to to setup your deeplens, and then forgot your password to ssh into the device here are the steps to recover it.</p><p>what you will need:</p><ul><li>usb keyboard</li><li>micro hdmi cable</li><li>monitor with hdmi input</li></ul><p>then follow these steps ( if you have ever recovered your password on ubuntu this will look familiar):</p><ol><li>press ESC key until bios screen comes up</li><li>select continue and hit enter</li><li>select root shell and press enter</li><li>type in the following commands</li></ol><pre>mount -o remount,rw /<br>passwd aws_cam</pre><p>5. follow the prompts to reset the password for that user</p><p>6. pres ctrl+d</p><p>7. continue with booting the device or reboot</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc4fea32af13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudaholics/recovering-ssh-password-on-your-aws-deeplens-fc4fea32af13">Recovering ssh password on your AWS Deeplens</a> was originally published in <a href="https://medium.com/cloudaholics">Cloudaholics</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Re-registering your AWS Deeplens]]></title>
            <link>https://medium.com/cloudaholics/re-registering-your-aws-deeplens-3a2d323d40ac?source=rss----d497ec070e2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/3a2d323d40ac</guid>
            <category><![CDATA[aws-deeplens]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[deeplens]]></category>
            <dc:creator><![CDATA[Derek Higgins]]></dc:creator>
            <pubDate>Tue, 26 Dec 2017 04:49:19 GMT</pubDate>
            <atom:updated>2017-12-26T04:51:46.246Z</atom:updated>
            <content:encoded><![CDATA[<p>As I was playing with my new Deeplens and I got in a situation where I had to de-register and re-register my device. De-registering the deeplens is very easy, click the De-register device button in the console and confirm that you want to de-register…. done, super easy. When I went to try and re-register my device it got tricky and there was a clear lack of documentation on how to do this.</p><p>When I went to register the deeplens again I went through the normal process through the console, but this time the Wi-Fi network did not show up to connect to and install the new certificates aws provided. After doing some research and a lot of googling I found that I had to remove the awslens application and reinstall it for the Wi-Fi network to show up to install the new certificates.</p><p>So instead of rebuilding the entire system to reset it to factory defaults you just need to reinstall the awscam application. <strong>You will need to know the ssh password you setup when registered the deeplens the first time.</strong></p><p>Here are the steps I had to follow:</p><ol><li>Hook up your deepens to a keyboard and monitor or ssh into the device if you know the ip.</li><li>login and Launch a terminal, if you did not ssh into the camera</li><li>Run the following commands:</li></ol><pre>sudo systemctl stop greengrassd.service<br>sudo rm -rf /opt/awscam<br>sudo apt-get update<br>sudo apt-get install --reinstall awscam<br>sudo reboot</pre><p>4. After the device reboots the Wi-Fi network will show up like when you first registered the device. You should now be able to follow the standard process of registering the device like you did the first time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a2d323d40ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudaholics/re-registering-your-aws-deeplens-3a2d323d40ac">Re-registering your AWS Deeplens</a> was originally published in <a href="https://medium.com/cloudaholics">Cloudaholics</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using lambda@edge to add client security headers to your Cloudfront distributions]]></title>
            <link>https://medium.com/cloudaholics/using-lambda-edge-to-add-client-security-headers-to-your-cloudfront-distributions-a75972e181d2?source=rss----d497ec070e2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/a75972e181d2</guid>
            <category><![CDATA[cloudfr]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <dc:creator><![CDATA[Derek Higgins]]></dc:creator>
            <pubDate>Sat, 30 Sep 2017 19:13:02 GMT</pubDate>
            <atom:updated>2017-10-06T00:07:34.656Z</atom:updated>
            <content:encoded><![CDATA[<p>Lambda@edge was made generally available on July, 17 2017, and allows you to customize cloudfront requests and responses in multiple ways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*juCEEzea9Zkog3ULekpU-Q.png" /></figure><h4>Challenge</h4><p>S3 and AWS API Gateway Cloudfront origins do not provide http security headers in the response for the client.</p><h4>Solution Overview</h4><p>We will use lambda@edge to inject these security headers into the response to the client. we will be following the <a href="https://www.owasp.org/index.php/OWASP_Secure_Headers_Project">OWASP Secure Headers Project</a> for best practices on which headers to add and what to set them to. The headers we will focus on are:</p><ul><li>Strict-Transport-Security: max-age=86400 ; includeSubDomains</li><li>X-Frame-Options: sameorigin</li><li>X-Content-Type-Options: nosniff</li></ul><p>all the code for this tutorial can be found at <a href="https://github.com/cloudaholics/lambdaSecurityHeaders">https://github.com/cloudaholics/lambdaSecurityHeaders</a></p><p>Here is our lambda function:</p><p>‘use strict’;</p><p>exports.handler = (event, context, callback) =&gt; {<br> const response = event.Records[0].cf.response;<br> const headers = response.headers;<br> const secHeaders = [{<br> “key”:”Strict-Transport-Security”,<br> “value”:”max-age=86400; includeSubDomains”<br> },<br> {<br> “key”:”X-Frame-Options”,”value”:”sameorigin”<br> },{<br> “key”:”X-XSS-Protection”,”value”: “1; mode=block”<br> },<br> {<br> “key”:”X-Content-Type-Options”,”value”: “nosniff”<br> }<br>];<br>secHeaders.forEach(function(header) {<br> console.log(header)<br> headers[header.key.toLowerCase()]=[header]<br>});</p><p>callback(null, response);<br>};</p><p>Lets start with creating the lambda function in the console</p><ol><li>login to you aws management console</li><li>navigate to lambda</li><li>create a new “Blank” function</li><li>leave trigger empty for now, we will configure this through cloudfront</li><li>set the following values for the fields,</li></ol><ul><li>Name = CloudfrontSecurityHeaders</li><li>Description = Add security headers to cloud front distrobution</li><li>runtime = Node.js 6.10</li></ul><p>6. copy the code into the code setion</p><p>7. leave the handler as “index.handler”</p><p>8. select “Create new role from template(s)” for role</p><p>9. set the role name to “lambdaedge_cloudfront_security_headers”</p><p>10. select “Basic Lambda Edge permissions” for the role template</p><p>11. click next and then create function</p><p>When adding the lambda function to the cloudfront behavior use viewer-response as the event-type</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a75972e181d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudaholics/using-lambda-edge-to-add-client-security-headers-to-your-cloudfront-distributions-a75972e181d2">Using lambda@edge to add client security headers to your Cloudfront distributions</a> was originally published in <a href="https://medium.com/cloudaholics">Cloudaholics</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Highly available multi region S3 website Cloudfront distributions]]></title>
            <link>https://medium.com/cloudaholics/highly-available-multi-region-s3-website-cloudfront-distributions-29fe07195a3?source=rss----d497ec070e2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/29fe07195a3</guid>
            <category><![CDATA[amazon-s3]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloudfront]]></category>
            <dc:creator><![CDATA[Derek Higgins]]></dc:creator>
            <pubDate>Sat, 30 Sep 2017 18:47:50 GMT</pubDate>
            <atom:updated>2017-09-30T19:38:32.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*PYVL7IpCSSvOBo9rqM-6rw.png" /></figure><p>With the latest S3 outages more people are looking to make their S3 Cloudfront distributions more highly available. Which presents challenges due to Cloudfront not being designed to fail over when a origin is unavailable.</p><h4><strong>The Challenge</strong></h4><p>When S3 is having issues in a specific region like the recent outages in us-east-1 cloudfront cannot automatically fail over to your replica bucket in a secondary region. You also cannot use route53 dns fail over because S3 routing is based off of DNS and you cannot have multiple Cloudfront distributions with the same cname.</p><h4>Solution Overview</h4><p>Using a route53 health check on the primary S3 bucket website endpoint you can trigger a lambda function to swap out the origin in your cloudfront distribution to the secondary(replica) S3 bucket in another region.</p><p><strong>Note:</strong> this solution will not automatically fail back. This is by design because some of the issues with S3 in the past where intermittent until the system was stabilized</p><p><strong>Note 2:</strong> Once Code is available on Github the post will be updated</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHBAfIF1xkT8j4jctIK_aw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29fe07195a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudaholics/highly-available-multi-region-s3-website-cloudfront-distributions-29fe07195a3">Highly available multi region S3 website Cloudfront distributions</a> was originally published in <a href="https://medium.com/cloudaholics">Cloudaholics</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>