<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud on Shadow Engineering</title>
    <link>https://shadow.engineering/tags/cloud/</link>
    <description>Recent content in Cloud on Shadow Engineering</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 </copyright>
    <lastBuildDate>Sat, 23 Apr 2022 11:30:03 +0000</lastBuildDate><atom:link href="https://shadow.engineering/tags/cloud/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Cloud Run Website with GCP</title>
      <link>https://shadow.engineering/posts/cloud_run_website_with_gcp/</link>
      <pubDate>Sat, 23 Apr 2022 11:30:03 +0000</pubDate>
      
      <guid>https://shadow.engineering/posts/cloud_run_website_with_gcp/</guid>
      <description>&lt;p&gt;As I outlined in &lt;a href=&#34;https://shadow.engineering/posts/iterations_of_this_site/&#34; title=&#34;Iterations of this Site&#34;&gt;Iterations of this Site&lt;/a&gt;, a time had come when I wanted to repurpose this domain, and use it to share some of the knowledge I had gained from experimentation and projects I had worked on.&lt;/p&gt;&#xA;&lt;p&gt;A common approach that a lot of people recommend is using a static site generator like &lt;a href=&#34;https://jekyllrb.com/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Jekyll&lt;/a&gt; or &lt;a href=&#34;https://gohugo.io/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Hugo&lt;/a&gt;, pushing that to a &lt;a href=&#34;https://pages.github.com/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;GitHub Pages&lt;/a&gt; repository and then using &lt;a href=&#34;https://workers.cloudflare.com/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Cloudflare Workers&lt;/a&gt; to mask that behind a domain name of your choosing.&lt;/p&gt;&#xA;&lt;p&gt;I really liked the approach, and it made some vast improvements over my previous methodology. But it would mean that a lot of the little easter eggs I had developed over the years would be lost.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Electric Blue - Lessons from a blue team securing Azure</title>
      <link>https://shadow.engineering/posts/electric_blue/</link>
      <pubDate>Sun, 07 Apr 2019 17:00:00 +1000</pubDate>
      
      <guid>https://shadow.engineering/posts/electric_blue/</guid>
      <description>&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/S-MZRZg-pGo?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&lt;p&gt;At the end of 2018, NAB built out it&amp;rsquo;s extensive cloud environment. As a security analyst who had not had a lot of exposure to cloud environments, it provided new challenges and lessons and I wanted to share that with the world. Thanks to Crikeycon and NAB for letting me share those lessons.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Slides:&lt;/strong&gt; &lt;a href=&#34;https://shadow.engineering/posts/electric_blue/electricblue.pdf&#34; &gt;PDF&lt;/a&gt; | &lt;a href=&#34;https://shadow.engineering/posts/electric_blue/electricblue.pptx&#34; &gt;PPXT&lt;/a&gt;&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
