<?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[Stories by Earl Gay on Medium]]></title>
        <description><![CDATA[Stories by Earl Gay on Medium]]></description>
        <link>https://medium.com/@earlg3?source=rss-eabbaa1967dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sMP5dCozou5H7azO.jpg</url>
            <title>Stories by Earl Gay on Medium</title>
            <link>https://medium.com/@earlg3?source=rss-eabbaa1967dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:19:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@earlg3/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Google Cloud Architect Exam Study Materials — Updates for 2019 Re-certification]]></title>
            <link>https://medium.com/@earlg3/google-cloud-architect-exam-study-materials-updates-for-2019-re-certification-c4894d3a82e7?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4894d3a82e7</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[gcp-certification]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 14:54:06 GMT</pubDate>
            <atom:updated>2019-07-24T14:54:06.022Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google Cloud Architect Exam Study Materials — Updates for 2019 Re-certification</h3><p>Two years after my initial certification for the <a href="https://cloud.google.com/certification/cloud-architect"><strong>Google Cloud Professional Cloud Architect Certification</strong></a>, it became time to re-certify as the cert is valid for only two-years. Many notification emails will come to your email well in advance of the expiration date giving plenty of heads up — with my notification also came a discount code, so be on the possible look out for that.</p><p>I covered my original preparation notes in a previous post, <a href="https://medium.com/@earlg3/google-cloud-architect-exam-study-materials-5ab327b62bc8"><strong>Google Cloud Architect Exam Study Materials (July, 2017)</strong></a>, and those notes are still solid prep material, but I did extend my preparation for this re-certification, which I wanted to share in this update.</p><h3>Latest Exam Guide &amp; Practice Exam</h3><p>Firstly, make sure to check out the most up-to-date <a href="https://cloud.google.com/certification/guides/professional-cloud-architect/"><strong>official Exam Guide</strong></a>. Read the Case Studies in the guide, these will likely be the same ones you’ll use in your exam.</p><p>There is even a<strong> </strong><a href="https://cloud.google.com/certification/practice-exam/cloud-architect"><strong>Practice Exam</strong></a> now (this didn’t exist when the exam first came out). You can optionally go ahead and try the Practice Exam to see how you fair, or wait til you’ve done some studying first — just keep in mind the questions are static and do not change each time you take the practice exam. The practice exam questions are really good, and are exactly like what is on the exam, so it’s good practice.</p><h3>New &amp; Expanded Prep Materials</h3><p>Secondly, the amount of preparation material since 2017 has greatly increased: hooray!</p><ul><li><a href="http://linuxacademy.com/"><strong>Linux Academy</strong> </a>has a ton of new GCP content, including a course designed specifically for this certification: <a href="https://linuxacademy.com/google-cloud-platform/training/course/name/google-cloud-certified-professional-cloud-architect">Google Cloud Certified Professional Cloud Architect Course by Matthew Ulasien</a>. <em>(I have to say this is not just one of the best GCP courses, but one of the best courses I’ve ever taken. I love the format and content, and they give you a great PDF to use in your studies.)</em></li><li><a href="https://www.youtube.com/playlist?list=PLIivdWyY5sqIXvUGVrFuZibCUdKVzEoUw"><strong>Google Cloud Next 2019 </strong>— All Session Videos</a> (<em>Don’t feel required to watch everything, but if there’s an area you think you could use some polish, find a session on it.</em>)</li><li><a href="https://www.youtube.com/playlist?list=PLBgogxgQVM9v0xG0QTFQ5PTbNrj8uGSS-"><strong>Google Cloud Next 2018 </strong>— All Session Videos</a> <em>(While 2018 is over a year old, and lots of changes happen in a year in the Cloud, I think you’ll be pretty safe referencing the content in these videos for any questions on the test — if you want to know the most up-to-date for general knowledge, make sure you check out the 2019 videos, though.)</em></li><li><a href="http://coursera.org/"><strong>Coursera</strong></a> now has a specific <a href="https://www.coursera.org/learn/preparing-cloud-professional-cloud-architect-exam?">Professional Cloud Architect course</a>, as well. I personally prefer two of the Specializations, though: <a href="https://www.coursera.org/specializations/gcp-architecture">Architecting with Google Cloud Platform Specialization</a> &amp; <a href="https://www.coursera.org/specializations/architecting-google-kubernetes-engine">Architecting with Google Kubernetes Engine</a> (<em>Kubernetes is important for the test, but the Kubernetes specialization may be overkill — however, I think it’s a really good specialization.</em>) There are a lot of great Coursera courses on GCP, and the <a href="https://www.qwiklabs.com/">Qwiklabs</a> built in to the courses are spectacular for helping you learn.</li><li><a href="http://acloud.guru/"><strong>ACloud.Guru</strong> </a>also has several GCP courses now, including exam prep for the <a href="https://acloud.guru/learn/gcp-certified-associate-cloud-engineer">Associate Cloud Engineer</a> and the <a href="https://acloud.guru/learn/gcp-certified-professional-cloud-architect">Certified Professional Architect</a>. The two courses kind of build on each, though can probably be treated independently. The ACE course also sends you over to their Kubernetes course, too.</li><li><a href="https://grumpygrace.dev/posts/gcp-flowcharts/"><strong>GCP Flowcharts</strong></a> from <a href="https://grumpygrace.dev/">GrumpyGrace.dev</a> are a collection of decision trees on when to pick what service/option that have been collected from throughout the official Google Cloud documentation. These are a great resource to help you know when to pick what as an Architect.</li></ul><p><em>Disclaimer: All of these recommendations are my personal opinion, and these are not advertisements or sponsored recommendations — I have, however, become employed by Google since my last guide was made, for full disclosure.</em></p><h3>Additional Services &amp; Solutions to Know</h3><p>I included a list of official documentation in the original guide, but these solutions also came up in my re-cert prep, so be sure to know these as well:</p><ul><li>Cloud Dataprep: <a href="https://cloud.google.com/dataprep/docs/">https://cloud.google.com/dataprep/docs/</a></li><li>Cloud Shell: <a href="https://cloud.google.com/shell/docs/">https://cloud.google.com/shell/docs/</a></li><li>Cloud Source Repository: <a href="https://cloud.google.com/source-repositories/docs/">https://cloud.google.com/source-repositories/docs/</a></li><li>Transfer Appliance: <a href="https://cloud.google.com/transfer-appliance/docs/2.0/">https://cloud.google.com/transfer-appliance/docs/2.0/</a></li><li><a href="https://git-scm.com/book/en/v1/Getting-Started-Git-Basics">Git</a>, <a href="https://www.spinnaker.io/concepts/">Spinnaker</a>, &amp; <a href="https://jenkins.io/doc/">Jenkins</a> (know at a very high level what these do and their basic terms)</li></ul><h3>Exam Tips &amp; Tricks</h3><p>Lastly, here are some other tips that may be useful:</p><ol><li>Know how to lifecycle data in all of the storage options (database, object, etc.) both from the UI and the CLI.</li><li>Understand when to use Cloud Dataproc and when to use Cloud Dataflow.</li><li>Know Cloud connectivity options like Cloud VPN, Cloud Interconnect, and others, and when to use them and not use them.</li><li>Look for little things in the wording of the question or answer that would invalidate an otherwise correct answer (e.g. if it’s possibly best option but they called a VPN a <em>Virtual Parallel Network</em> instead of a <em>Virtual Private Network</em>).</li><li>Understand how security rules flow up and down whether it’s IAM or Bucket Policies, etc.</li><li>For each service, be sure to understand whether it’s Global, Regional, or Zonal and how that impacts the architecture.</li><li>For areas that have lots of options (e.g. databases), know what the limits are of those databases that would push you towards a different option (e.g. Cloud Spanner versus Cloud SQL).</li><li>Know how to get data into GCP, and when to use what option.</li></ol><h3>Good Luck!</h3><p>After studying, head over to WebAssessor and <a href="https://www.webassessor.com/googlecloud/">register</a>! Keep in mind, you can reschedule up to 72 hours in advance if you need. As far as the exam itself, you receive your Pass or Fail immediately, though you do not receive any details on how much you passed or failed by, or which areas you did well in — it’s a simple Pass or Fail. But, if you’ve studied the above and spent time with GCP, you should have no problems acing it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4894d3a82e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft’s Serverless Glue: Azure Functions]]></title>
            <link>https://medium.com/@earlg3/microsofts-serverless-glue-azure-functions-bce68c4fdba5?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bce68c4fdba5</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[azure-functions]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Mon, 30 Apr 2018 00:51:06 GMT</pubDate>
            <atom:updated>2018-04-30T14:37:22.278Z</atom:updated>
            <content:encoded><![CDATA[<p>Combining Events ( ⚡) and Code (&lt;/&gt;) is the story behind Azure Function’s purpose and logo. Similar to AWS Lambda or Google Cloud Functions, Azure Functions is Microsoft Azure’s Functions-as-a-Service (FaaS) offering, but the logo is just the tip of the iceberg of Azure Functions’ awesomeness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*tR25lCPFIaU1wiliaLI0Xg.jpeg" /><figcaption>The Azure Functions Logo</figcaption></figure><p>Azure Functions’ architecture is actually fairly unique compared to its’ counterparts, and with that comes some unique benefits. As the evolution of Azure’s Web Apps and Web Jobs, Azure Functions inherit much of the functionality: Continuous Integration, Kudu, Authentication, Certificates, Custom Domains, etc.; that means it has a lot of great, mature features in the platform. There are also two options from an OS perspective: Windows and Linux (Preview).</p><p>While it may spawn debates on serverlessness in the latter option, Azure Functions has two types of “Hosting Plans”: Consumption (based on usage, which is traditionally what you think when you think FaaS) and App Service (where you can leverage servers in an App Service plan). While arguably less “serverless,” the App Service plan provides predictable costing and is a model not available with AWS Lambda or Google Cloud Functions.</p><p>Azure Functions is also <a href="https://github.com/Azure/Azure-Functions">open source</a> (there are links to the component repositories inside this parent repository), though I don’t know of any forks or implementations of the codebase outside of Microsoft’s usage. The FaaS solutions from Google and Amazon are not open source, though they do have some open source components within them; <a href="https://console.bluemix.net/openwhisk/">IBM’s Cloud Functions</a> is based on the open source <a href="https://openwhisk.apache.org/">Apache OpenWhisk project</a>.</p><p>Azure Functions are grouped into “Function Apps” which then house multiple functions themselves inside them. The interface and topology is much different from how AWS Lambda and Google Cloud Functions appear; while speculation on my part, I suspect this is based on Azure Function’s architecture built on the back of the Windows platform whereas the others were built on the back of Linux platforms. With that said, I don’t think the difference is particular worse or better, just different and may take someone used to the other FaaS offerings a second to get their bearings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*Rux6Vrkv_v499lXDgNiK-A.png" /><figcaption>Azure Functions exist under the Compute section of the Azure Portal</figcaption></figure><p>Azure Functions supports a fairly wide range of <a href="https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings#supported-bindings">triggers </a>and <a href="https://docs.microsoft.com/en-us/azure/azure-functions/supported-languages">languages</a>. From the trigger perspective, Azure Functions supports: Blob Storage, HTTP, Azure Cosmos DB, Timer, Webhook, Queue Storage, Service Bus Queue / Topic, Event Hub, Event Grid, External File. From a language perspective, Azure Functions supports: C#, F#, Javascript, as well as the following “Experimental” languages: TypeScript, PHP, PowerShell, Python, Bash; experimental languages are noted by Microsoft to not scale well and not support all bindings. Despite that large language list, if you like examples from Microsoft’s online documentation, I hope you like C#!</p><p>Joking aside, JavaScript has full-featured support and we’ll run through creating a quick example function with an HTTP Trigger using JavaScript and the <a href="https://github.com/Azure/azure-functions-core-tools">Azure Functions Core Tools</a> (as opposed to the Azure Portal, which is fairly straightforward).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*f6Je2Pnin5VUbkb2BDbVEA.png" /><figcaption>Azure Functions Core Tools CLI</figcaption></figure><p><strong>Prerequisites / Assumptions: </strong>These steps are performed using Windows / PowerShell (<em>there are </em><a href="https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions"><em>some differences between the 1.x and 2.x Azure Functions runtimes</em></a><em>, but for the purpose of this we will be using 1.x as it is the only supported production version)</em>. Please also ensure <a href="https://nodejs.org/en/download/">NodeJS 8.x/npm</a> are installed, as well as <a href="https://code.visualstudio.com/">Visual Studio Code</a>. Install the <a href="https://www.microsoft.com/net/learn/get-started/windows#windowscmd">.NET Core SDK </a>to enable debugging the Function in VS Code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JO7D3LP2MFIiqP28Iayvw.png" /><figcaption>We’ll create, test, debug, and publish an Azure Function locally!</figcaption></figure><ol><li>Launch PowerShell (as Admin to install the tools) and execute: npm install azure-functions-core-tools -g. Launch a new non-privileged PowerShell terminal after installation completes.</li><li>Type func and the help/usage should be displayed.</li><li>Type func azure account list which, if not already logged in, will open a browser window to prompt for Azure credentials. It will then list subscriptions (which can be changed with func azure account set if needed).</li><li>Initialize a new local Functions project with func init azure-func-app1. This will create a new git-enabled directory called azure-func-app1 with skeleton files: <strong>.gitignore</strong> (determines which files and directories for git to ignore), <strong>host.json</strong> (metadata file contains global configuration options that affect all functions for a function app), <strong>local.settings.json</strong> ( stores app settings, connection strings, and settings for Azure Functions Core Tools), <strong>launch.json</strong> (debugging configuration information for VS Code).</li><li>Enter into the function app direction: cd azure-func-app1.</li><li>Create a new function: func function create. Select: <strong>JavaScript </strong>as language, <strong>HTTP</strong> <strong>trigger</strong> as trigger, <strong>HttpTriggerJS </strong>as name. It will create the following within a child directory named after the chosen function name: <strong>index.js</strong> (function handler code), <strong>sample.dat</strong> (sample for the trigger), <strong>function.json</strong> (defines the function bindings and other configuration settings).</li><li>From here, it’s easier to edit the code within VS Code. Launch a VS Code session with: code . — from there you can either edit the function by modifying the index.js or just leave it as the sample code which will respond with “Hello &lt;name&gt;”. (<strong>Side note</strong>: <em>In the sample code that it uses </em><em>context.log() instead of </em><em>console.log as may be expected in other FaaS solutions. </em><em>console.log() will not work as you expect due to the architecture of Azure Functions</em>.)</li><li>Back in PowerShell inside the <em>azure-func-app1</em> directory, run func host start --debug vscodeand when the Windows Security Alert pops up, select <em>Allow access</em> to allow the server to run. The server should launch and show the trigger running on: <a href="http://localhost:7071/api/HttpTriggerJs">http://localhost:7071/api/HttpTriggerJs</a> as well as the Debugger listening on [::]:5858.</li><li>Browse to <a href="http://localhost:7071/api/HttpTriggerJs">http://localhost:7071/api/HttpTriggerJs</a> and you should receive a response to “<em>Please pass a name on the query string or in the request body</em>”.</li><li>Browse to <a href="http://localhost:7071/api/HttpTriggerJs?name=Earl">http://localhost:7071/api/HttpTriggerJs?name=Earl</a> and should receive a response of “<em>Hello Earl</em>”.</li><li>Switch to the PowerShell window running the local server. Logs of interaction and execution are scrolled through this window and can help with troubleshooting.</li><li>Try editing <em>index.js</em> and saving it (e.g. add a comma after Hello in the response). Reload your request in your web browser and it should now show the new response. Note that you didn’t have to relaunch your local server, but just save the file and it auto-updates the local function — this speeds up development process.</li><li>Within the VS Code window that was launched, let’s use the debugger. Select <em>Debug </em>from the left menu (or press Ctrl+Shift+D). Ensure “<em>Attach to Azure Functions</em>” is within the drop down and then select the green play button to Start Debugging.</li><li>Add a breakpoint on line 4 by right-clicking the space to the left of the line number and clicking “<em>Add Breakpoint</em>” — a red dot should appear. Now, browse to <a href="http://localhost:7071/api/HttpTriggerJs?name=Earl">http://localhost:7071/api/HttpTriggerJs?name=Earl</a> again. The debugger should catch the request and break where selected. Let’s check out the “<em>req</em>” variable that will be checked in this if statement: expand <em>req </em>→ <em>query </em>→ <em>name </em>and it should be set to “Earl” as expected.</li><li>Press the green play button at the top of the window (or press F5) to continue through the function; the response should now appear in the browser window. This debugging integration also speeds up the development process! (<strong>Side note:</strong> <em>Debugging in VS Code only works for Javascript; to debug C#, use Visual Studio.</em>)</li><li>Deploy a shell Function App through the portal or whatever means desired. To do so via the Portal, browse to Create a Resource → Compute → Function App. Enter a globally unique App Name (e.g. name-azfn-app1), select the Subscription that was selected at the command line by Azure Functions Core Tools, and either configure the rest or leave it as defaults. It takes a few seconds to a minute to deploy.</li><li>Once the Function App is deployed within Azure, publish the local Function App to it with: func azure functionapp publish name-azfn-app1.</li><li>Browse to the Azure Portal and the HttpTriggerJS function should be deployed. Select the function and click “&lt;/&gt; Get Function URL” at the top next to “Run”. The URL should look like <a href="https://name-azfn-app1.azurewebsites.net/api/HttpTriggerJs?code=XXXX">https://name-azfn-app1.azurewebsites.net/api/HttpTriggerJs?code=XXXX</a>. Try running it with and without “&amp;name=Earl” on the end of the URL and it should behave the same as the local function.</li></ol><p>Tada! You’ve now gone through the process of creating an Azure Function locally, testing it, debugging it, and deploying it to Production!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVnLnNlu52XuvpHfB3in-Q.png" /><figcaption>Debugging an Azure Function inside Visual Studio Code</figcaption></figure><p>For more information on Azure Functions, check out:</p><ul><li>Microsoft’s <a href="https://docs.microsoft.com/en-us/azure/azure-functions/">Azure Functions Documentation</a></li><li>PluralSight’s <a href="https://www.pluralsight.com/courses/azure-functions-fundamentals">Azure Functions Fundamentals Course</a></li><li>Udemy’s <a href="https://www.udemy.com/getting-started-with-azure-functions/">Getting Started with Azure Functions Course</a></li><li>PluralSight’s <a href="https://www.pluralsight.com/courses/play-by-play-build-serverless-node-web-api">Build a Serverless Node Web API with Azure Functions Course</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bce68c4fdba5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Functions: Scheduled Trigger]]></title>
            <link>https://medium.com/@earlg3/google-cloud-functions-scheduled-trigger-915b5fb8310f?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/915b5fb8310f</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[google-app-engine]]></category>
            <category><![CDATA[google-cloud-functions]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Sun, 11 Feb 2018 22:22:17 GMT</pubDate>
            <atom:updated>2018-02-11T22:22:17.463Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://cloud.google.com/functions/">Google Cloud Functions</a>, at the time of writing, has the <a href="https://cloud.google.com/functions/docs/concepts/events-triggers">following native triggers</a>:</p><ul><li><strong>HTTP </strong>— invoke functions directly via HTTP requests</li><li><strong>Google Cloud Storage</strong> — invoke functions as a result of object change notification</li><li><strong>Google Cloud Pub/Sub</strong> — invoke functions from a Pub/Sub message</li></ul><p>Additional <a href="https://firebase.google.com/docs/functions/#key_capabilities">triggers are available via Firebase</a>, as well:</p><ul><li><strong>Cloud Firestore</strong></li><li><strong>Realtime Database</strong></li><li><strong>Firebase Authentication</strong></li><li><strong>Google Analytics for Firebase</strong></li><li><strong>Crashlytics</strong></li></ul><p>But, sometimes it is desirable to have Google Cloud Functions executed on a schedule versus waiting to execute in response to one of the aforementioned events. For example, AWS Lambda has <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/RunLambdaSchedule.html">CloudWatch Events triggers</a> to allow for Lambda functions to be executed on a schedule. By default, there is no direct scheduled trigger event builtin for Google Cloud Functions, though.</p><p>On the bright-side, there are workarounds for this documented by Google:</p><ul><li><a href="https://firebase.googleblog.com/2017/03/how-to-schedule-cron-jobs-with-cloud.html">How to Schedule (Cron) Jobs with Google Cloud Functions for Firebase</a> (Uses Pub/Sub as the intermediate event.)</li><li><a href="https://cloud.google.com/solutions/reliable-task-scheduling-compute-engine">Reliable Task Scheduling on Google Compute Engine</a> (Technically for GCE, but translatable.)</li></ul><p>The core of this workaround is built on<a href="https://cloud.google.com/appengine/"> Google App Engine</a>, which provides <a href="https://cloud.google.com/appengine/docs/standard/python/config/cron">built-in Cron functionality insides its’ Task Queues</a>. Check out the <a href="https://github.com/firebase/functions-cron"><strong>firebase/functions-cron</strong> GitHub repo</a> that uses this methodology using Pub/Sub as the intermediary event; it’s well-documented and describes everything in detail.</p><p>Essentially, the end result is that Google App Engine Cron Jobs are used to call a Python application running in GAE that then calls Pub/Sub which the Google Cloud Function uses as the event source to execute. A bit more complicated than it needs to be, but not too difficult.</p><h3>Swapping out Pub/Sub</h3><p>I didn’t want to use Pub/Sub, and preferred to keep everything inside HTTP, though.</p><p>There is one problem with using HTTP compared to using Pub/Sub, though: we can protect the GAE URL handler (e.g. &lt;url&gt;/publish/hourly-tick) through the GAE app.yaml file through <a href="https://cloud.google.com/appengine/docs/standard/python/config/appref#handlers_login">the </a><a href="https://cloud.google.com/appengine/docs/standard/python/config/appref#handlers_login">login element</a>, but we can’t really protect it the same way with an HTTP trigger. The login element can be configured to login: admin to provide additional security before allowing the handler to run, but even if we add that to our HTTP-based trigger, someone could still navigate to the function HTTP URL directly bypassing GAE and its’ security.</p><p><strong>For the record, if you want the most secure option, use the GAE &amp; Pub/Sub method. </strong>But, if you <em>really </em>want to use HTTP instead, we can instead do the following method (based on an extension of Valerii Iatsko’s <a href="https://medium.com/google-cloud/google-cloud-functions-scheduling-cron-5657c2ae5212">Google Cloud Functions: Scheduling</a>):</p><h4>App Engine Configuration — app.yaml</h4><pre>runtime: python27<br>api_version: 1<br>threadsafe: true</pre><pre>handlers:<br>    - url: /.*<br>      script: main.app</pre><h4><strong>App Engine Cron Configuration — cron.yaml</strong></h4><pre>cron:<br>    - description: &quot;Hourly Job&quot;<br>      url: /hour<br>      schedule: every 1 hours</pre><h4>App Engine Handler — main.py</h4><pre>import webapp2<br>import urllib2</pre><pre>class HourCronPage(webapp2.RequestHandler):<br>    def get(self):<br>        request = urllib2.Request(&#39;&lt;GCF URL&gt;&#39;, headers={&quot;cronrequest&quot; : &quot;true&quot;})<br>        contents = urllib2.urlopen(request).read()</pre><pre>app = webapp2.WSGIApplication([<br>    (&#39;/hour&#39;, HourCronPage),<br>    ], debug=True)</pre><p>With the above App Engine configuration, the &lt;GCF URL&gt; will be hit every 1 hour. If you’re wondering why this is written in Python instead of Node.JS like the Cloud Function itself, that’s because Python is supported within the <a href="https://cloud.google.com/appengine/docs/the-appengine-environments">Google App Engine Standard Environment which is much cheaper than the Google App Engine Flexible Environment</a>. Node.JS requires the Flexible Environment, and it’s not worth paying more when it’s only a few lines of Python.</p><p>To deploy the above, just place the files in a directory inside your Google Cloud Shell then run: gcloud app deploy app.yaml to deploy the App and then gcloud app deploy cron.yaml to deploy the Cronjob.</p><h4>Cloud Functions Handler— index.js</h4><pre>exports.scheduledfunction = (req, res) =&gt; {<br>    if (req.headers[&quot;cronrequest&quot;] === &quot;true&quot;) {<br>        res.status(200).send(&#39;Success&#39;); // Function logic<br>    } else {<br>        res.status(200).send(&#39;Failed&#39;); // Aborted due to no header<br>    }<br>};</pre><p>With the above configuration, the function will only run if it’s executed and the header called cronrequest is set to true. You could replace this with something more complicated or specific, if desired. It’s not going to be as good as the Pub/Sub method… but it does provide some basic validation.</p><h3>Putting it all together…</h3><p>For simplicity’s sake, I forked the <a href="https://github.com/firebase/functions-cron"><strong>firebase/functions-cron repo</strong></a> into <a href="https://github.com/eeg3/gcp-functions-cron-http"><strong>eeg3/gcp-functions-cron-http</strong></a> and made the above modifications. You can simply deploy that project to get this effect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915b5fb8310f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless in the Google Cloud with Firebase & Cloud Functions]]></title>
            <link>https://medium.com/@earlg3/serverless-in-the-google-cloud-with-firebase-cloud-functions-3cc004648ba3?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cc004648ba3</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Sun, 28 Jan 2018 19:35:55 GMT</pubDate>
            <atom:updated>2018-01-28T19:35:55.683Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GYcnX0izi8SeIIHm.png" /></figure><p>Google Cloud Platform’s best kept secret is Firebase. Firebase is Google’s “Mobile platform that helps you quickly develop high-quality apps and grow your business.” In short, it provides a lot of awesome development services like Authentication, Hosting, Real-time Database, and more. In fact, it even takes Google Cloud Functions and adds new triggers, so that you can kick off functions from events that seemed unavailable otherwise!</p><p>If you look at GCP’s Products &amp; Services list, or even if sign up for a GCP account and start navigating the console, you will see scarce if any reference to Firebase directly. On the products page, for example, if you search the page for “<em>Firebase</em>”, there is a small link in a bottom footer to go to (next to Google+ links and Chrome Dev links) and that’s it. In the GCP Console, there is no direct link from the navigation area.</p><p>Your first thought(s) based on that are probably either “Firebase must not be very important” or “I guess GCP doesn’t have those services.” Fortunately, neither are true! Combining the power Firebase &amp; GCP equals a stellar serverless platform.</p><h3>My Journey to Firebase</h3><p>My dive into Firebase came when I decided to build a new personal project on GCP to immerse myself deeper in Google Cloud Functions. I have done a fair bit with Lambda, but didn’t have the depth in Cloud Functions quite yet, so it seemed like an opportune time to remedy that.</p><p>Cloud Functions is still technically in BETA and has some areas for improvement at the time of writing this post:</p><ol><li>Only available in us-central1</li><li>Only supports Node.JS</li><li>Limited triggers: Pub/Sub, Storage, HTTP/S, and Firebase; (E.g. doing a time-based trigger requires some clever workarounds)</li></ol><p>Like with most GCP services, Google does a good job of providing tutorials through sample use cases: <a href="https://cloud.google.com/functions/docs/tutorials/">https://cloud.google.com/functions/docs/tutorials/</a>. The first thing I needed to figure out was authentication of the HTTP/S trigger for my serverless app. In the AWS world, I would front my function with API Gateway and integrate a Cognito Authorizer there, but that isn’t exactly how it works in GCP.</p><p>There is actually an article on “<a href="https://cloud.google.com/solutions/authentication-in-http-cloud-functions">Authentication in HTTP Cloud Functions</a>”, but it uses a pretty convoluted (in my opinion) method of checking for <em>storage.bucket.get</em> access:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TeIxjclNEyVXbsKol1afkg.png" /><figcaption>Google Cloud Functions HTTP Authorization Scheme from GCP Article</figcaption></figure><h4>Enter Firebase Authentication</h4><p>I searched for other solutions for Cloud Functions authentication as I wanted something similar to the AWS Lambda + API Gateway + Cognito approach. I ended up at: <a href="https://github.com/firebase/functions-samples/tree/master/authorized-https-endpoint">GitHub / firebase / functions-samples / Authorized HTTPS Endpoint</a>. The example leverages Firebase Authentication as ExpressJS middleware inside the Google Cloud Function to provide authentication. It’s an easy method to add Authentication, although I am conflicted architecturally on having my authentication directly inside my Function versus at the API Gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ig2zJVULQrunlxiqHmGbHQ.png" /><figcaption>Google Cloud Function Auth through Firebase Authentication with Firebase Hosting Front-end</figcaption></figure><p>The above diagram shows how the authentication works at a high-level. The user accesses the static site hosted on Firebase Hosting, which provides client-side authentication through Firebase Authentication. That Firebase Authentication token is then passed to the Google Cloud Function and verified; if verified, the function runs. The demo code really only verifies that the user has a Google Account and nothing more (more granular access is left as an exercise to the reader).</p><h4>Deploying a Serverless App with Firebase</h4><p>Firebase is great for more than just adding the Authentication component to Cloud Functions. It’s actually a great serverless platform that provides a <a href="https://firebase.google.com/products/">whole collection of development service</a>s: Hosting, Functions, Database, and more. (<strong>Site Note:</strong> <em>Many of Firebase’s services are things one might not think exist within GCP with only a casual glance, which is why I hope Google integrates Firebase &amp; GCP from a UI/Marketing perspective better in the future)</em>.</p><p>Deploying an application with Firebase can be as simple as:</p><ol><li>Creating the Firebase Project</li><li>Installing firebase-tools on your system through npm: npm install -g firebase-tools</li><li>Logging in at the CLI with firebase login</li><li>Configuring what Firebase project to use with firebase use --add</li><li>Deploying with firebase deploy</li></ol><p>The firebase tools also come with local emulators, including for Hosting &amp; Functions, so you can test as simply as: firebase server --only hosting,functions then browsing to localhost your local dev machine!</p><p>Firebase Projects tie to GCP Projects, and Cloud Functions within Firebase deploy within the GCP Console as relatively normal Functions. I wish the UI was a bit better integrated, but the services on the backend work well together regardless.</p><p>There are a lot of tools within Firebase beyond hosting and functions, so I encourage everyone to <a href="https://firebase.google.com/products/">check them all out</a>. I suspect most folks will be very impressed.</p><h3>Breaking Down &amp; Extending the Sample Code</h3><p>The <a href="https://github.com/firebase/functions-samples/tree/master/authorized-https-endpoint">sample code</a> provided by Firebase for authentication is great, but I wanted to fork it to provide some additional capabilities as well as put it into my coding/UI/template style.</p><h4>Function Modifications</h4><p>Overall, I kept the function mostly the same, but added a few things for demo purposes:</p><ol><li>I wanted to be able to call the function directly (e.g. through Postman) with a token, so I added the /token route which displays the token that can be placed in the Authorization header inside Postman for example.</li><li>Added a /world route to show it’s easy to just keep adding routes here, if desired.</li></ol><h4>Front-End Modifications</h4><p>This is the area I changed the most.</p><ol><li>I prefer to use <a href="https://getbootstrap.com/">Bootstrap</a> for my front-end components versus the included usage of <a href="https://getmdl.io/">Material Design Lite,</a> so index.html was modified to swap these.</li><li>I added some basic look and feel components like a navbar.</li><li>The original code included showing usage of direct Authorization and using the __session cookie. I swapped it to simply use the Authorization method. (<strong>Site note:</strong> <em>The </em><em>__session cookie can be set if you want to be able to call the Cloud Function directly from another tab for example, but isn’t really required for persistence within the app.</em>)</li><li>Added a card that shows the User’s details (e.g. Display Name, Email, etc.) after logging in.</li><li>I swapped in jQuery over vanilla javascript just as a personal preference.</li><li>Included some logic for creating the API URL for portability (e.g. more cleanly define the URL for all cases).</li></ol><h4>End Result</h4><p>The outcome was the creation of a simple template I can use to create serverless applications on Google Cloud Platform &amp; Firebase: <a href="https://github.com/eeg3/gcp-firebase-serverless-demo">https://github.com/eeg3/gcp-firebase-serverless-demo</a>. I hope this is useful to someone that wants a simple starter demo, and hope it encourages folks to try out the great combination of Firebase &amp; GCP.</p><h3>More Information</h3><ul><li><a href="https://firebase.google.com/">Firebase</a> &amp; <a href="https://cloud.google.com/functions/">Google Cloud Functions</a></li><li><a href="https://www.youtube.com/playlist?list=PLl-K7zZEsYLkYCygo5_greqgAcNS5P5TH">Google Cloud Next ’17 Conference — Firebase Playlist</a></li><li><a href="https://www.google.com/search?q=google+i%2Fo+firebase+youtube">Google I/O ’17 — Firebase Videos</a></li><li><a href="https://github.com/firebase/functions-samples">Firebase Functions Samples GitHub Repo</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cc004648ba3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VMworld 2017 Highlights: VMware Cloud on AWS Sessions]]></title>
            <link>https://medium.com/@earlg3/vmworld-2017-highlights-vmware-cloud-on-aws-sessions-a31649fe3a42?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31649fe3a42</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Sun, 24 Sep 2017 03:32:44 GMT</pubDate>
            <atom:updated>2017-09-24T03:32:44.551Z</atom:updated>
            <content:encoded><![CDATA[<p>The sessions for VMworld 2017 have been posted on YouTube! Thanks to William Lam for documenting them all, they are all easily found on his GitHub writeup (both US &amp; EU): <a href="https://github.com/lamw/vmworld2017-session-urls">https://github.com/lamw/vmworld2017-session-urls</a></p><p>The most exciting topic for me was VMware Cloud on AWS. It’s going to solve a lot of problems for customer in their journey to the Cloud, and the sessions I attended were packed to maximum capacity. Just from the buzz when talking to organizations at VMworld, I knew this was going to be big. Now that it’s been a few weeks and I’ve had a chance to visit many customers and talk with them about VMC, that hypothesis is proving to be correct.</p><p>There are lots of questions from folks around what exactly is VMware Cloud on AWS, how does it work operationally, what kind of integration is there, and lots and lots of technical deep dive questions. Based on that, I wanted to highlight and categorize some of the great content from the VMworld sessions to make it easier for folks to find (be sure to check the link above to every session available).</p><p>Below you will find sections devoted to the aforementioned categories with some brief highlight commentary to give you a better idea on what is in the session. Hope this helps folks get up to speed with what I know is going to be a hit!</p><h3>Introductions to VMware Cloud on AWS</h3><h4>LHC1547BU — Creating Your VMware Cloud on AWS Data Center: VMware Cloud on AWS Fundamentals</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FkIDwIJus1oM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DkIDwIJus1oM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkIDwIJus1oM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3a3cfaa901877c47099d646011102566/href">https://medium.com/media/3a3cfaa901877c47099d646011102566/href</a></iframe><p>Brought to you by Oren Root &amp; Matt Dreyer of VMware. Lots of demos in this session, including:</p><ul><li>Creating the SDDC in VMware Cloud on AWS</li><li>Connecting to a VMware Cloud on AWS VM from the Internet</li><li>Hybrid Linked Mode</li><li>Cold Migration from On-Premises to VMware Cloud on AWS</li><li>Integrating AWS IoT with VMware Cloud on AWS API</li></ul><h4>LHC1882BU — Service Overview for VMware Cloud on AWS</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBROKtlzsruI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBROKtlzsruI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBROKtlzsruI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5db54cc258a669ccf82775ffb0671d9/href">https://medium.com/media/f5db54cc258a669ccf82775ffb0671d9/href</a></iframe><p>Talks about the delineation of responsibility between Customers &amp; VMware in management and operations of VMware Cloud on AWS, Service Maintenance of the environment (including a video of the Release Coordination Engine), Automated Cluster Remediation (host failure resolution, adding/removing hosts), how support works (models, live chat support addition, service health status monitoring, built-in knowledge base into VMC portal), and how the <a href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/vmw-cloud-aws-service-level-agreement.pdf">Service Level Agreement for VMware Cloud on AWS</a> works. There is also a good 15 minutes worth of audience questions at the end.</p><h4>LHC3371BUS VMware Cloud on AWS — The Painless Path to Hybrid Cloud</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-0ksTmrSez4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-0ksTmrSez4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-0ksTmrSez4%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/8e5346a23150ed2276453dca6103d9cb/href">https://medium.com/media/8e5346a23150ed2276453dca6103d9cb/href</a></iframe><p>This combined session by 451 Research and AWS covers a lot of market type data (e.g. movement to cloud percentages, hybrid cloud customer expectations), how organizations are making the move to Hybrid Cloud (i.e. strategies), etc. It also walks through the opportunity for businesses by Hybrid Cloud and the challenges. It also walks through at a high level: account structure, software/hardware components, connectivity, and integration with AWS services (e.g. Redshift, DynamoDB).</p><h3>Operations with VMware Cloud on AWS</h3><h4>LHC1158BU — Architecture and Tooling for the Brownfield Hybrid Cloud</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-znhNDchdLM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-znhNDchdLM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-znhNDchdLM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d6d43789a3f7c54988717f2560f05a4/href">https://medium.com/media/0d6d43789a3f7c54988717f2560f05a4/href</a></iframe><p>This session goes into Scripps Networks Interactive’s approach to Hybrid Cloud, including their business demands to utilize Public Cloud, how they went about it, and lessons learned. Scripps Network Interactive is the company that brings you channels like Food Network, HGTV, Travel Channel, etc. SNI was a member of the LightHouse and Early Access Program for VMware Cloud on AWS.</p><h4>LHC2971BU — Managing Your Hybrid Cloud with VMware Cloud on AWS</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKtmM67aVp88%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKtmM67aVp88&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKtmM67aVp88%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/7b93e8780a675ff397b42503bdff596b/href">https://medium.com/media/7b93e8780a675ff397b42503bdff596b/href</a></iframe><p>The differences between On-Premises SDDC and VMware Cloud on AWS’ SDDC activities, and how VMC removes some of the pain and mundane activity (e.g. ESXi setup tasks like waiting on hardware, network ports, etc). Talks about the initial configuration options and maximums (which will continually improve), as well as how controllable VMC is as it was built to be API-driven. Lots of other great content in this session as well: Elastic DRS, Hybrid Linked Mode, Resource Pool topology (Compute &amp; Management; vCenter, NSX, and other Management VMs live on your cluster). This session has 15 minutes of audience questions at the end, as well.</p><h4>LHC1910BU — Using vRealize with VMware Cloud on AWS</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3J9ChtZZEvo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3J9ChtZZEvo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3J9ChtZZEvo%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/72058afaf9e0339908084e8b3b545c50/href">https://medium.com/media/72058afaf9e0339908084e8b3b545c50/href</a></iframe><p>vRealize support for VMware Cloud on AWS: Assessing, troubleshooting, capacity management, extend native AWS integration visibility, etc. There are a lot of demos in this session:</p><ul><li>vRealize Business for Cloud</li><li>Using the VMC Assessment tool of vRealize Business via the What-if Analysis options for cost comparison of Private vs VMC</li><li>vRealize Network Insight for Application Dependency Mapping when considering VMC</li><li>vRealize Operations Manager for visibility across On-Premises &amp; VMware Cloud on AWS</li><li>Capacity Management &amp; Reclaimation with vRealize Operations</li><li>Extending Management of Native AWS Services (e.g. EC2, RDS) with vRealize Operations</li></ul><h4>LHC1748BU — VMware Cloud for AWS and the Art of Software-Defined Data Centers: API, CLI, &amp; PowerShell</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FADMi8vNyPvk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DADMi8vNyPvk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FADMi8vNyPvk%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/25a9c88917fd4bbc7118487d5383f82d/href">https://medium.com/media/25a9c88917fd4bbc7118487d5383f82d/href</a></iframe><p>If you love APIs and PowerShell, this is the session for you: API Endpoints for VMC &amp; how to automate and take advantage of the API-driven nature of VMC. Includes a demo of CLI Access to VMC.</p><p>It also talks about the Restrictive Access Model of VMware Cloud on AWS; since VMC is a managed service, not everything is available to modify (e.g. VIBs, no root ESXi access).</p><h4>MMC2455BU — On-Demand Disaster Recovery for Enterprise Applications with the VMware Cloud on AWS</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIJ4TEzm5nhs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIJ4TEzm5nhs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIJ4TEzm5nhs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/23b5639f91434b38c2903c09048441b0/href">https://medium.com/media/23b5639f91434b38c2903c09048441b0/href</a></iframe><p>Starts out discussing the importance of Disaster Recovery and the traditional approaches before diving into DR with native AWS then DR with VMware Cloud on AWS. Discusses on SRM and what they’re working on around it in conjunction with VMC (e.g. flexible version pairing). Shows the concept of “Add-Ons” in VMC, particularly demo’ing Site Recovery Manager as an Add-On. Good chunk of questions at the end.</p><h3>Integrations around VMware Cloud on AWS</h3><h4>LHC2281BU — Intriguing Integrations with VMware Cloud on AWS, EC2, S3, Lambda, and More</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHIpp6WqCGK4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHIpp6WqCGK4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHIpp6WqCGK4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff59c4ebd5ba7fe5ed30ea3fb0283ac9/href">https://medium.com/media/ff59c4ebd5ba7fe5ed30ea3fb0283ac9/href</a></iframe><p>Brian Graf and Matt Dreyer walk through using the VMware Cloud on AWS API. VMware is serious about APIs with VMC, and they go through a lot of examples of cool integration through it. There are a lot of cool demos:</p><ul><li>Sample application for a serverless Self-service Virtual Machine tool using AWS S3, Cognito, Lambda, and VMware Cloud on AWS.</li><li>Slack Integration for VMC Inventory</li><li>Using Amazon RDS with VMware Cloud on AWS Virtual Machines</li><li>Creating a VMware Cloud on AWS IoT Button to spawn a bunch of Photon Clones and also to delete them.</li><li>Creating a VMware Cloud on AWS IoT Button to run a vCheck on the environment and then text message the report that is saved in AWS S3.</li><li>Alexa Skill for VMware Cloud on AWS Service Status and even adding hosts.</li></ul><h4>LHC3175BU — VMware Cloud on AWS Partner Solutions Showcase</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fk0yyd3E6jlE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dk0yyd3E6jlE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fk0yyd3E6jlE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/461a4ab460642f1ba84efb6bd4b880bb/href">https://medium.com/media/461a4ab460642f1ba84efb6bd4b880bb/href</a></iframe><p>Walks through several tested partner ecosystem solutions with the VMware Cloud on AWS, such as: RISC Networks CloudScape, Chef, TrendMicro, Palo Alto, F5, and more. As of the session, there were over 20 ISV tech partners that have tested their solutions against VMC with lots more on the way.</p><h4>LHC3376BUS — AWS Native Services Integration with VMware Cloud on AWS: Technical Deep Dive</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxC4xbysR9zY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxC4xbysR9zY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxC4xbysR9zY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/37b6c584082bee8b6e59553e89404168/href">https://medium.com/media/37b6c584082bee8b6e59553e89404168/href</a></iframe><p>Presented by Paul Bockelman and Haider Witwit of AWS, this session goes into integration use cases (e.g. scaling applications, mitigating DDoS attacks, increasing security visibility). They cover the usage of lots of AWS services alongside and integrated with VMC: AWS Certificate Manager, Elastic Load Balancing, RDS, Storage Gateway, Auto-Scaling EC2, S3, CloudFront, Shield, WAF, CloudWatch, Kinesis Firehose, Elasticsearch, Athena, QuickSight, Lambda, CodeDeploy, and more. Lots of pretty diagrams in this session!</p><h3>Technical Deep Dives</h3><h4>LHC2384BU — VMware Cloud on AWS: A Technical Deep Dive</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFh8VvwHcDUA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFh8VvwHcDUA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFh8VvwHcDUA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a08accff23f3d820cd4b9d7748a93870/href">https://medium.com/media/a08accff23f3d820cd4b9d7748a93870/href</a></iframe><p>Goes into the detail of the compute platform specifics, Cluster Configuration (DRS, Resource Pools, HA, etc), vSAN topology, NSX &amp; Networking, connectivity to native AWS, and ends with answering lots of attendee questions.</p><h4>LHC3375BUS — VMware Cloud on AWS Hybrid Cloud Architectural Deep Dive: Networking and Storage Best Practices</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYsowrnb9E38%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYsowrnb9E38&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYsowrnb9E38%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/da1745989f46e022382294fc760144a2/href">https://medium.com/media/da1745989f46e022382294fc760144a2/href</a></iframe><p>Presented by AWS Solutions Architects, deep dive into VMC &amp; AWS Account topology, networking flow and considerations, integrated storage services (EBS, S3, Storage Gateway), data protection, and workload analysis. Lots of good info on AWS Storage services for folks not as familiar with them.</p><h4>LHC3174BU — VMware Cloud on AWS: An Architectural and Operational Deep Dive</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnQwchswYXYk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnQwchswYXYk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnQwchswYXYk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8e8f469ab072dfdf4ad4e74422dbbff/href">https://medium.com/media/e8e8f469ab072dfdf4ad4e74422dbbff/href</a></iframe><p>Very detailed walkthrough of the operational side of VMware Cloud on AWS (organizations, console walkthroughs, limits on operational permissions). Really good diagrams and walkthroughs of all the pieces fitting together (customer AWS account, SaaS components, SDDC, etc.). There is probably the deepest technical architectural session of any of the deep dives.</p><h4>STO1890BU — VMware Cloud on AWS: Storage Deep Dive</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsuFrjMI5oKg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsuFrjMI5oKg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsuFrjMI5oKg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/511528bbbb58f26dcfd53b8387e2313c/href">https://medium.com/media/511528bbbb58f26dcfd53b8387e2313c/href</a></iframe><p>Unlike the other session above, this session focuses a bit more on the VMware side of the storage equation of VMware Cloud on AWS: vSAN configuration, vSAN operation models, and more. Learn all about vSAN in VMC! There is also some interesting “futures” discussion in this session with detail on things they are working on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a31649fe3a42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Lambda + AWS Cognito Triggers to Only Allow Auto-Verification to Specific Domain]]></title>
            <link>https://medium.com/@earlg3/using-lambda-aws-cognito-triggers-to-only-allow-auto-verification-to-specific-domain-db2efea79c44?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/db2efea79c44</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[aws-cognito]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 04:00:44 GMT</pubDate>
            <atom:updated>2017-08-23T04:00:44.248Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are using <a href="https://aws.amazon.com/cognito/">AWS Cognito</a> for your authentication source for your site, it can be easily configured to require verification of emails which can then automatically confirm users as they sign up. This makes the process very simple to allow users to sign up on their own, verify their email address, and get to using your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*jV0dIKgf4GgTSAsffKxi3Q.png" /><figcaption>Enabling Email Verification within Cognito</figcaption></figure><p>If you need to add some logic into that workflow, Cognito provides “Triggers.” These triggers can occur at various stages of the process, and they execute Lambda functions to provide the customization. An example in <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">the official documentation</a> is blocking authentication based on a particular Client ID, but there are lots of options and it puts the power in your hands.</p><p>The challenge with the original automatic verification process is that it allows anyone at all to sign up, verify, and use the application. In my use case, I wanted to make it so only users with a specific email address domain (e.g. user@approvedemaildomain.com) could do everything automatically. If the user came from an unapproved domain, I still wanted them to be able to sign up, but I wanted it to require manual verification for an override.</p><p>The Lambda Triggers within Cognito let me do this, but I couldn’t find an easily Google-able example online of doing this. After some tinkering, I came to the following simple solution:</p><ol><li>Create a Lambda Function (e.g. cogEmailDomainVerify)</li></ol><pre>exports.handler = function(event, context) {<br>    <br>    // Configure the email domain that will be allowed to automatically verify.<br>    var approvedDomain = &quot;approveddomain.com&quot;;<br>    <br>    // Log the event information for debugging purposes.<br>    console.log(&#39;Received event:&#39;, JSON.stringify(event, null, 2));</pre><pre>if (event.request.userAttributes.email.includes(&#39;@&#39; + approvedDomain)) {<br>        console.log (&quot;This is an approved email address. Proceeding to send verification email.&quot;);<br>        event.response.emailSubject = &quot;Signup Verification Code&quot;;<br>        event.response.emailMessage = &quot;Thank you for signing up. &quot; + event.request.codeParameter + &quot; is your verification code.&quot;;<br>        context.done(null, event);<br>    } else {<br>        console.log (&quot;This is not an approved email address. Throwing error.&quot;);<br>        var error = new Error(&#39;EMAIL_DOMAIN_ERR&#39;);<br>        context.done(error, event);<br>   }</pre><pre>};</pre><p>2. Within Cognito, under Triggers -&gt; Custom Message, choose the Lambda function. (<em>The above code could be modified and the trigger could be performed at a different stage if alternative (i.e. more restrictive) behavior was required.</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*_Z6IfvC_I44c7MFZoJkmEQ.png" /><figcaption>Selecting the Lambda function as a Custom Message Trigger</figcaption></figure><p>3. (Optional) Modify your code to check for an “EMAIL_DOMAIN_ERR” message and handle it accordingly.</p><pre>var onFailure = function registerFailure(err) {<br>            if (err.message.includes(&quot;EMAIL_DOMAIN_ERR&quot;)) {<br>              alert(&quot;This email address is not within the approved list. Please contact an Administrator for manual verfication.&quot;);<br>              window.location.href = signinUrl;<br>            } else {<br>              alert(err);<br>            }<br>        };</pre><p>After making those quick changes, you should now be able to sign up, verify, and start using the application automatically if using an email@approveddomain.com; however, any other email address will require manual verification before they can actually start using the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*4ofZaBCMjocUQ21c6M0R4w.png" /><figcaption>First user is not within the approved domain and required manual verification. Second user is within approved domain and was able to verify automatically.</figcaption></figure><p>In order to do manual verification, that can be done by logging into Cognito, selecting the user, and selecting “Confirm user”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*5nyBAbX4lFsw5YLaInOQLw.png" /><figcaption>Confirming a User within Cognito Manually</figcaption></figure><p>The process is very simple, and shows another way Lambda provides powerful capabilities and integrates well into other AWS services.</p><h4>More Details:</h4><ul><li><a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html">Customizing User Pool Workflows by Using AWS Lambda Triggers</a></li><li><a href="https://aws.amazon.com/blogs/mobile/customizing-your-user-pool-authentication-flow/">Customizing Amazon Cognito User Pool Authentication Flow</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db2efea79c44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless Web Applications with CI/CD in AWS]]></title>
            <link>https://medium.com/a-cloud-guru/serverless-web-applications-with-ci-cd-in-aws-15a49f6cbb1f?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/15a49f6cbb1f</guid>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Sat, 12 Aug 2017 23:36:48 GMT</pubDate>
            <atom:updated>2017-08-19T17:21:25.183Z</atom:updated>
            <content:encoded><![CDATA[<p>Serverless applications integrate managed services such as C0gnito, S3, DynamoDB with event-driven Functions-as-a-Service solutions — AWS Lambda — to deploy applications in a manner which doesn’t require managing servers.</p><blockquote>Serverless computing allows you to build and run applications and services without thinking about servers. Serverless applications don’t require you to provision, scale, and manage any servers. You can build them for virtually <a href="https://aws.amazon.com/serverless/#usecases">any type of application</a> or backend service, and everything required to run and scale your application with high availability is handled for you.</blockquote><p>There’s a lot of awesome benefits of serverless — including dramatically reduced costs of solutions. But the real power of serverless is unleashed when developers start to worry less about their infrastructure — and focus more attention on services to that differentiate their applications.</p><p>An attendee from A Cloud Guru’s recent <a href="http://serverlessconf.io/">Serverlessconf</a> in Austin highlighted that developers are most excited about sharing the <em>solutions</em> they are creating with serverless architectures. That’s the power of serverless — allowing developers to focus on delivering business value.</p><h3>James Wickett on Twitter</h3><p>Software should minimize lead time to value recognition @tastapod @mikebroberts #ServerlessConf</p><p>The enthusiasm for serverless doesn’t mean it’s easy. It takes time to shift to a new approaches and architecture patterns, and there are plenty of challenges with operations and observability.</p><p>There are plenty of deep-dive <a href="https://www.youtube.com/channel/UCqlcVgk8SkUmve4Kw4xSlgw">sessions from Serverlessconf 0n YouTube</a> which dive into the challenges with serverless which are well worth the watch. For the live show, the upcoming serverless conference will be hosted in <a href="https://nyc.serverlessconf.io/">NYC from October 9–11</a>.</p><h4>Getting Up to Speed with AWS Labs</h4><p>To developers get up-to-speed on serverless, AWS released some tutorials focused on building and managing serverless platforms. There are a couple great examples written by AWS labs:</p><ul><li><strong>Learning Paths on AWS: </strong><a href="https://aws.amazon.com/getting-started/serverless-web-app/"><strong>Build a Serverless Web Application Workshop</strong></a> — This tutorial walks through <a href="https://aws.amazon.com/getting-started/serverless-web-app/module-1/">hosting a static website</a> (with AWS S3), <a href="https://aws.amazon.com/getting-started/serverless-web-app/module-2/">managing users</a> (with AWS Cognito), <a href="https://aws.amazon.com/getting-started/serverless-web-app/module-3/">building a serverless backend</a> (with AWS Lambda and DynamoDB), and <a href="https://aws.amazon.com/getting-started/serverless-web-app/module-4/">deploying a RESTful API</a> (with AWS API Gateway).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*3irMy5JjrVsYPkYl37BDPA.png" /><figcaption>The website created using the “Build a Serverless Web Application” Learning Path</figcaption></figure><ul><li><a href="https://github.com/awslabs/aws-serverless-samfarm"><strong>Serverless SAM Farm</strong></a> — This tutorial deploys a CI/CD pipeline using the Serverless <a href="https://aws.amazon.com/about-aws/whats-new/2016/11/introducing-the-aws-serverless-application-model/">Application Model (SAM)</a>, which is an extension of AWS CloudFormation, as well as AWS CodePipeline, CodeBuild, S3, Lambda, and API Gateway. The AWS team also created a great video walkthrough on the process: <a href="https://www.youtube.com/watch?v=P7i01eqmzrs">How to Do Continuous Integration and Continuous Deployment with AWS Lambda and AWS CodePipeline</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-Gezxo_XvflDz98dMhMsg.png" /><figcaption>The SAM the Squirrel Farm deployed within the CI/CD Pipeline</figcaption></figure><h3>Extending the Examples</h3><p>Both of the AWS Labs samples are awesome on their own, but I thought they complemented each other very well, too, so I thought it made sense to combine them. I had a couple of goals when combining the projects:</p><ol><li>Simplify the templates and pipeline so they could be easily deployed as starter kits for projects with minimal tweaks (e.g. remove a lot of the customization around “WildRydes” in the Website and switch from Lambda configuring Cognito to using CloudFormation directly).</li><li>Make the entire process as automated as possible as part of the pipeline (e.g. integrate updating the website itself into the pipeline instead of just the serverless backend).</li></ol><p>As a result, I combined the two projects into the following project: <a href="https://github.com/eeg3/serverless-pipeline">https://github.com/eeg3/serverless-pipeline</a>. For a full list of modifications from the parent projects, check out the <a href="https://github.com/eeg3/serverless-pipeline#modifications-from-original-sources">Modifications from Original Sources</a> section of the README.</p><p>You can find all of the code, instructions, details, modifications, and notes on the <a href="https://github.com/eeg3/serverless-pipeline">GitHub repository</a>. The end-result is a Serverless Web Application template that can be fully deployed into a CI/CD pipeline with minimal effort.</p><h4>Serverless Services Used</h4><p>This project leverages the following AWS services as part of its serverless stack:</p><ol><li><a href="https://aws.amazon.com/cloudformation/"><strong>CloudFormation</strong></a>: Used to deploy the entire stack.</li><li><a href="https://aws.amazon.com/about-aws/whats-new/2016/11/introducing-the-aws-serverless-application-model/"><strong>AWS Serverless Application Model</strong></a>: Used to provision Lambda/API Gateway.</li><li><a href="https://aws.amazon.com/s3/"><strong>S3</strong></a>: Used to provide static website hosting and to store our build artifacts.</li><li><a href="https://aws.amazon.com/lambda/"><strong>Lambda</strong></a>: Used to perform Functions-as-a-Service.</li><li><a href="https://aws.amazon.com/api-gateway/"><strong>API Gateway</strong></a>: Used to provide an integration point to our Lambda functions.</li><li><a href="https://aws.amazon.com/cognito/"><strong>Cognito</strong></a>: Used to provide authentication for our website.</li><li><a href="https://aws.amazon.com/iam/"><strong>IAM</strong></a>: Provides security controls for our process.</li><li><a href="https://aws.amazon.com/codepipeline/"><strong>CodePipeline</strong></a>: Used to provide the pipeline functionality for our CI/CD process.</li><li><a href="https://aws.amazon.com/codebuild/"><strong>Code Build</strong></a>: Used to build the project as part of CodePipeline process.</li><li><a href="http://www.github.com/"><strong>GitHub</strong></a>: Used as the source code repository. Could theoretically be replaced with CodeCommit.</li></ol><h4>Functionality</h4><p>The process starts by deploying the deploy.json file inside CloudFormation. The deploy.json template will ask for the following parameters:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Losp7FJEXuOOVq21UfcPcQ.png" /><figcaption>The Combined Pipeline CloudFormation Template Parameters</figcaption></figure><ol><li><strong>AppName</strong>: Name of the S3 Bucket to create that should house the website. This must be unique.</li><li><strong>CodeBuildImage</strong>: Name of the CodeBuild container image to use. Default should be fine, but customizable if desired.</li><li><strong>CognitoPool</strong>: Name of the Cognito Pool to create to use for authentication purposes.</li><li><strong>GitHubRepoBranch</strong>: Branch of the GitHub repo that houses the application code.</li><li><strong>GitHubRepName</strong>: Name of the GitHub repo that houses the application code.</li><li><strong>GitHubToken</strong>: GitHub token to use for authentication to the GitHub account. Configurable inside Github: <a href="https://github.com/settings/tokens">https://github.com/settings/tokens</a>. Token needs repo_hook permissions.</li><li><strong>GitHubUser</strong>: GitHub Username.</li><li><strong>SAMInputFile</strong>: Serverless transform file. By default, this is the included sam.json file.</li><li><strong>SAMOutputFile</strong>: The filename for the output file from the buildspec file. This doesn’t need to be changed unless the artifact file inside the buildspec.yml file is changed to a different name.</li></ol><p>The files referenced (e.g. SAMInputFile) are expected to exist within the GitHub repository. The CloudFormation deployment will warn that it is creating IAM permissions. This is because it creates roles and policies for the pipeline to use.</p><p>The initial CloudFormation Stack will be created after deploy.json is launched. Once that first stack is created, the CodePipeline will then create the pipeline stack after a period of time. The pipeline stack will be called {parent-stack}-serverless-stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6jC98Nvt044r4oj_201FQ.png" /><figcaption>The Foundational Services Stack and the Pipeline Stack</figcaption></figure><p>After initial deployment, the site will not be fully functional as the config.js file still needs to be updated so the site knows how to utilize the services. Within the parent Stack, the Outputs tab should display the following items: <strong>UserPoolClientId</strong>, <strong>BucketName</strong>, <strong>UserPoolId</strong>, <strong>OriginURL</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*e7ERDvE-MvNY8RK1Z9L50Q.png" /><figcaption>The Outputs from the Foundational Stack that are used within the Web Site</figcaption></figure><p>Within the child pipeline Stack, the Outputs tab should display the following items: <strong>ApiUrl</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*QfS1dBM8nsSCogzwNIbE7A.png" /><figcaption>The API Gateway URL created through the Pipeline that is used within the Web Site</figcaption></figure><p>The UserPoolClientId, UserPoolId, OriginURL, and ApiUrl should all now be placed into the website/js/config.js file so that the website knows how to use the services provisioned; this is a one-time process. Once the config.js file is updated, push the change to the GitHub repo; this will automatically update the application with the new config through the pipeline.</p><p>The site should now work as expected. Browse to the URL defined within OriginURL, and select &quot;Register&quot; from the top right drop-down. Enter an email address and password, and select Register. You will receive a verification code from Cognito. Once received, select &quot;Verify&quot; from the top right drop-down; on the verify page, enter your email and verification code provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XhYPwHcxCZ_UlOnWjGN1zQ.png" /><figcaption>The Base Template Website created through the Pipeline</figcaption></figure><p>Try browsing to the “Squirrel Farm”. If you have not logged in, you should be redirected to the Sign-In page. Enter your credentials, and you should now be taken to the “Squirrel Farm”. Within the graphic in the middle of the page, one SAM Squirrel should initially be displayed, and then it should increase to 15 shortly thereafter, once it has reached out and asked API Gateway/Lambda how many it should display.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*F6tfDav_HqLYC51ZHYdQSw.png" /><figcaption>Look at all those SAM Squirrels!</figcaption></figure><p>You can also browse directly to the API Gateway/Lambda function and see how many Squirrels should be displayed. You can do this by browsing to the “ApiUrl” listed in the pipeline Stack and appending ‘/sam’ to the end (e.g. <a href="https://od3tfr5l1a.execute-api.us-east-1.amazonaws.com/Prod/sam">https://od3tfr5l1a.execute-api.us-east-1.amazonaws.com/Prod/sam</a>). By default, it should return ‘15’. The website uses this return value to decide how many squirrels should be in the farm.</p><p>As the website or serverless function is updated, simply perform the modifications and then push them to the GitHub repo. Once checked in to Github, CodePipeline will handle the rest automatically. To test this functionality, browse to the CodePipeline page and view the pipeline while pushing a change. The pipeline will show the process from Source -&gt; Build -&gt; Deploy. If there are any failures, they will be visible within the pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*VrN-Kr_9mEupLq0FH3i7Mw.png" /><figcaption>The CodePipeline that keeps the Serverless Application Continuously Delivered</figcaption></figure><h3>Start Creating!</h3><p>Many thanks to the awesome folks at <a href="https://github.com/awslabs">AWS Labs</a> for creating the great samples that are used within this template; they deserve all the credit! I hope you find the combined template code useful as you start working with Serverless Applications.</p><p>There are lots of great resources out there around Serverless and the community is exploding. Check out the following other awesome tutorials as you continue on your Serverless journey!</p><ul><li><a href="https://serverless.com/">The Serverless Framework</a>: A framework for deploying and managing Serverless environments; works with AWS, Google Cloud Platform, Azure, and IBM OpenWhisk.</li><li><a href="https://botleg.com/stories/developing-in-aws-lambda-with-serverless-framework/">Developing in AWS Lambda with Serverless Framework</a>: Tutorial on using the Serverless Framework with AWS.</li><li><a href="https://thenewstack.io/five-tips-building-serverless-teams-enterprise/">Five Tips on Building Serverless Teams in an Enterprise</a>: Considerations on operationalizing Serverless architectures.</li><li><a href="https://thenewstack.io/5-handy-api-services-web-development/">5 Handy ‘Serverless’ APIs for Web Development</a>: Some additional services that can be leveraged in Serverless architectures.</li><li><a href="https://auth0.com/blog/building-serverless-apps-with-aws-lambda/">Building Serverless Apps with AWS Lambda</a>: Tutorial on building Serverless Applications by Auth0, which is a great authentication platform.</li><li><a href="https://aws.amazon.com/blogs/compute/the-twelve-days-of-lambda/">The Twelve Days of Lambda</a>: A collection of ideas and examples on using AWS Lambda.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a49f6cbb1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-cloud-guru/serverless-web-applications-with-ci-cd-in-aws-15a49f6cbb1f">Serverless Web Applications with CI/CD in AWS</a> was originally published in <a href="https://medium.com/a-cloud-guru">A Cloud Guru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Architect Exam Study Materials]]></title>
            <link>https://medium.com/@earlg3/google-cloud-architect-exam-study-materials-5ab327b62bc8?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ab327b62bc8</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 01:19:45 GMT</pubDate>
            <atom:updated>2019-07-24T14:56:00.215Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(</em><strong><em>Update: </em></strong><em>I’ve added a new post highlighting my re-certification: </em><a href="https://medium.com/@earlg3/google-cloud-architect-exam-study-materials-updates-for-2019-re-certification-c4894d3a82e7"><strong><em>Google Cloud Architect Exam Study Materials — Updates for 2019 Re-Certification</em></strong></a><em>. Be sure to check it out for some additional notes and prep material!)</em></p><p>After recently completing the Google Cloud Architect certification, I wanted to share the preparation materials that I used. Due to the newness of the exam, one challenge is there is not the same abundance of preparation material as there is for other Cloud exams. The <a href="https://cloud.google.com/certification/guides/cloud-architect/">official Exam Guide</a> leaves a bit to be desired and there is no official Practice Exam at the current time, so I hope this material is helpful for folks preparing.</p><p>I prepared through a combination of methods outlined below (in addition to real-world GCP usage):</p><ul><li><strong>Official GCP Documentation</strong></li><li><strong>Google Cloud Next ’17 Conference Videos</strong></li><li><strong>Coursera</strong></li><li><strong>Linux Academy</strong></li></ul><p>This is probably a little overkill, but none of the aforementioned alone went into the depth in all of the areas that I had hoped. The answer was using the combination, and skipping areas in each that may have been redundant.</p><h3>Official Documentation</h3><p>This is the just the official Google Cloud Platform documentation: <a href="https://cloud.google.com/docs/">https://cloud.google.com/docs/</a>.</p><p><strong>Side-note:</strong> <em>One thing I liked about the exam is that I didn’t feel like any of the questions asked me for point-in-time questions (i.e. what did this feature do when the exam was released versus what it may do now as of July of 2017). As a result, you can prepare well by reviewing the most up-to-date documentation without a fear that your knowledge will be too accurate. That’s kind of a silly thing to say, but other exams from other vendors do have questions where you have to answer them based on a previous point in time, even if the version of the exam and product still match.</em></p><p>Most of these documents are overviews or FAQs. You may want to branch off of them into deeper areas, but I felt the Product Overview and FAQs were solid. I reviewed the product documentation last of all of the study material I used, and mostly used it to fill in gaps of knowledge, though; if you review this material first, you may want to go deeper.</p><h4>Overview</h4><ul><li><a href="https://cloud.google.com/docs/overview/">https://cloud.google.com/docs/overview/</a></li><li><a href="https://cloud.google.com/docs/geography-and-regions">https://cloud.google.com/docs/geography-and-regions</a></li><li><a href="https://cloud.google.com/docs/compare/aws/">https://cloud.google.com/docs/compare/aws/</a></li></ul><h4>Compute Engine</h4><ul><li><a href="https://cloud.google.com/compute/docs/regions-zones/regions-zones">https://cloud.google.com/compute/docs/regions-zones/regions-zones</a></li><li><a href="https://cloud.google.com/compute/docs/faq">https://cloud.google.com/compute/docs/faq</a></li><li><a href="https://cloud.google.com/docs/choosing-a-compute-option">https://cloud.google.com/docs/choosing-a-compute-option</a></li><li><a href="https://cloud.google.com/compute/docs/instances/preemptible">https://cloud.google.com/compute/docs/instances/preemptible</a></li></ul><h4>App Engine</h4><ul><li><a href="https://cloud.google.com/appengine/kb/">https://cloud.google.com/appengine/kb/</a></li><li><a href="https://cloud.google.com/appengine/docs/the-appengine-environments">https://cloud.google.com/appengine/docs/the-appengine-environments</a></li><li><a href="https://cloud.google.com/appengine/docs/flexible/">https://cloud.google.com/appengine/docs/flexible/</a></li><li><a href="https://cloud.google.com/appengine/docs/standard/">https://cloud.google.com/appengine/docs/standard/</a></li><li><a href="https://cloud.google.com/appengine/docs/glossary">https://cloud.google.com/appengine/docs/glossary</a></li></ul><h4>Container Engine</h4><ul><li><a href="https://cloud.google.com/container-engine/">https://cloud.google.com/container-engine/</a></li></ul><h4>Storage Decisions</h4><ul><li><a href="https://cloud.google.com/docs/storing-your-data">https://cloud.google.com/docs/storing-your-data</a></li></ul><h4>Cloud Storage</h4><ul><li><a href="https://cloud.google.com/storage/docs/faq">https://cloud.google.com/storage/docs/faq</a></li><li><a href="https://cloud.google.com/storage/docs/best-practices">https://cloud.google.com/storage/docs/best-practices</a></li></ul><h4>Spanner</h4><ul><li><a href="https://cloud.google.com/spanner/docs/overview">https://cloud.google.com/spanner/docs/overview</a></li></ul><h4>Cloud SQL</h4><ul><li><a href="https://cloud.google.com/sql/faq">https://cloud.google.com/sql/faq</a></li><li><a href="https://cloud.google.com/sql/docs/features">https://cloud.google.com/sql/docs/features</a></li></ul><h4>Bigtable</h4><ul><li><a href="https://cloud.google.com/bigtable/docs/overview">https://cloud.google.com/bigtable/docs/overview</a></li></ul><h4>Datastore</h4><ul><li><a href="https://cloud.google.com/datastore/docs/concepts/overview">https://cloud.google.com/datastore/docs/concepts/overview</a></li><li><a href="https://cloud.google.com/datastore/docs/best-practices">https://cloud.google.com/datastore/docs/best-practices</a></li></ul><h4>Transfer Service</h4><ul><li><a href="https://cloud.google.com/storage/transfer/">https://cloud.google.com/storage/transfer/</a></li></ul><h4>Networking</h4><ul><li><a href="https://cloud.google.com/compute/docs/vpc/">https://cloud.google.com/compute/docs/vpc/</a></li><li><a href="https://cloud.google.com/compute/docs/load-balancing-and-autoscaling">https://cloud.google.com/compute/docs/load-balancing-and-autoscaling</a></li><li><a href="https://cloud.google.com/compute/docs/vpc/firewalls">https://cloud.google.com/compute/docs/vpc/firewalls</a></li><li><a href="https://cloud.google.com/compute/docs/vpn/overview">https://cloud.google.com/compute/docs/vpn/overview</a></li></ul><h4>Stackdriver Logging</h4><ul><li><a href="https://cloud.google.com/logging/">https://cloud.google.com/logging/</a></li><li><a href="https://cloud.google.com/logging/docs/basic-concepts">https://cloud.google.com/logging/docs/basic-concepts</a></li><li><a href="https://cloud.google.com/logging/docs/view/logs_index">https://cloud.google.com/logging/docs/view/logs_index</a></li></ul><h4>Stackdriver Monitoring</h4><ul><li><a href="https://cloud.google.com/monitoring/">https://cloud.google.com/monitoring/</a></li></ul><h4>Stackdriver Error Reporting</h4><ul><li><a href="https://cloud.google.com/error-reporting/">https://cloud.google.com/error-reporting/</a></li><li><a href="https://cloud.google.com/error-reporting/reference/">https://cloud.google.com/error-reporting/reference/</a></li></ul><h4>Stackdriver Trace</h4><ul><li><a href="https://cloud.google.com/trace/">https://cloud.google.com/trace/</a></li><li><a href="https://cloud.google.com/trace/docs/faq">https://cloud.google.com/trace/docs/faq</a></li><li><a href="https://cloud.google.com/trace/docs/reference/">https://cloud.google.com/trace/docs/reference/</a></li></ul><h4>Stackdriver Debugger</h4><ul><li><a href="https://cloud.google.com/debugger/">https://cloud.google.com/debugger/</a></li><li><a href="https://cloud.google.com/debugger/docs/before-you-begin">https://cloud.google.com/debugger/docs/before-you-begin</a></li></ul><h4>Endpoints</h4><ul><li><a href="https://cloud.google.com/endpoints/">https://cloud.google.com/endpoints/</a></li><li><a href="https://cloud.google.com/endpoints/docs/about-cloud-endpoints">https://cloud.google.com/endpoints/docs/about-cloud-endpoints</a></li><li><a href="https://cloud.google.com/endpoints/docs/architecture-overview">https://cloud.google.com/endpoints/docs/architecture-overview</a></li></ul><h4>Security Scanner</h4><ul><li><a href="https://cloud.google.com/security-scanner/">https://cloud.google.com/security-scanner/</a></li><li><a href="https://cloud.google.com/security-scanner/docs/using-the-scanner">https://cloud.google.com/security-scanner/docs/using-the-scanner</a></li><li><a href="https://cloud.google.com/security-scanner/docs/faq">https://cloud.google.com/security-scanner/docs/faq</a></li></ul><h4>Identity and Security</h4><ul><li><a href="https://cloud.google.com/security/">https://cloud.google.com/security/</a></li><li><a href="https://cloud.google.com/compute/docs/access/">https://cloud.google.com/compute/docs/access/</a></li><li><a href="https://cloud.google.com/docs/authentication/">https://cloud.google.com/docs/authentication/</a></li><li><a href="https://cloud.google.com/security/data-loss-prevention/revoking-user-access">https://cloud.google.com/security/data-loss-prevention/revoking-user-access</a></li><li><a href="https://cloud.google.com/solutions/securing-gcp-account-security-keys">https://cloud.google.com/solutions/securing-gcp-account-security-keys</a></li><li><a href="https://cloud.google.com/security/security-design/">https://cloud.google.com/security/security-design/</a></li><li><a href="https://cloud.google.com/iam/docs/overview">https://cloud.google.com/iam/docs/overview</a></li><li><a href="https://cloud.google.com/iam/docs/faq">https://cloud.google.com/iam/docs/faq</a></li></ul><h4>Identity-Aware Proxy</h4><ul><li><a href="https://cloud.google.com/iap/docs/concepts-overview">https://cloud.google.com/iap/docs/concepts-overview</a></li><li><a href="https://cloud.google.com/iap/docs/faq">https://cloud.google.com/iap/docs/faq</a></li></ul><h4>KMS</h4><ul><li><a href="https://cloud.google.com/kms/docs/object-hierarchy">https://cloud.google.com/kms/docs/object-hierarchy</a></li><li><a href="https://cloud.google.com/kms/docs/secret-management">https://cloud.google.com/kms/docs/secret-management</a></li></ul><h4>Developer Tools</h4><ul><li><a href="https://cloud.google.com/tools/docs/">https://cloud.google.com/tools/docs/</a></li></ul><h4>Resource Management</h4><ul><li><a href="https://cloud.google.com/launcher/docs/">https://cloud.google.com/launcher/docs/</a></li><li><a href="https://cloud.google.com/resource-manager/">https://cloud.google.com/resource-manager/</a></li></ul><h4>Deployment Manager</h4><ul><li><a href="https://cloud.google.com/deployment-manager/docs/fundamentals">https://cloud.google.com/deployment-manager/docs/fundamentals</a></li><li><a href="https://cloud.google.com/deployment-manager/docs/best-practices/">https://cloud.google.com/deployment-manager/docs/best-practices/</a></li></ul><h4>DataProc</h4><ul><li><a href="https://cloud.google.com/dataproc/">https://cloud.google.com/dataproc/</a></li><li><a href="https://cloud.google.com/dataproc/docs/resources/faq">https://cloud.google.com/dataproc/docs/resources/faq</a></li></ul><h4>DataFlow</h4><ul><li><a href="https://cloud.google.com/dataflow/">https://cloud.google.com/dataflow/</a></li><li><a href="https://cloud.google.com/dataflow/faq">https://cloud.google.com/dataflow/faq</a></li></ul><h4>Pub/Sub</h4><ul><li><a href="https://cloud.google.com/pubsub/">https://cloud.google.com/pubsub/</a></li><li><a href="https://cloud.google.com/pubsub/docs/faq">https://cloud.google.com/pubsub/docs/faq</a></li></ul><h3>Google Cloud Next Sessions</h3><p>The sessions from Google Cloud Next are on YouTube now (217 of them), and if there are any areas where you feel you’d like a little more depth (e.g. App Engine, Cloud Storage, Datastore, Stackdriver), these sessions can be helpful. They’re also just all really good sessions in general. Even if you’re not preparing for the exam, I’d recommend watching as many of the videos as you can. I like to watch them at 2.0x speed for maximum productivity.</p><ul><li><strong>Google Cloud Next 2017 Playlist:</strong> <a href="https://www.youtube.com/playlist?list=PLIivdWyY5sqI8RuUibiH8sMb1ExIw0lAR">https://www.youtube.com/playlist?list=PLIivdWyY5sqI8RuUibiH8sMb1ExIw0lAR</a></li></ul><h3>Coursera</h3><p>The Coursera courses are made available by Google to partners, but are available for anyone. They have a couple of options for courses, but if you are a current AWS Certified Architect Professional then there is a course available based on that, which is what I took. It compares GCP products with AWS products and is slimmed down from the other option.</p><p>I thought it was a valuable course, but lecture videos were fairly short. Total lecture time was 121 minutes, but there are quizzes and labs. The non-AWS specific course appears to be a little longer.</p><ul><li><a href="https://www.coursera.org/">Coursera</a> — <strong>Google Cloud Platform Fundamentals for AWS Professionals</strong>: <a href="https://www.coursera.org/learn/gcp-fundamentals-aws/">https://www.coursera.org/learn/gcp-fundamentals-aws/</a></li></ul><h3>Linux Academy</h3><p>I subscribe to Linux Academy because they have a ton of great courses in general even outside of GCP, but they also have several Google Cloud Platform courses available. Honestly, I only skimmed through the course because I had done all of the other preparation prior, but the material seems solid.</p><ul><li>Linux Academy — <strong>Google Cloud Platform Essentials</strong>: <a href="https://linuxacademy.com/cp/modules/view/id/133">https://linuxacademy.com/cp/modules/view/id/133</a></li></ul><h3>Final Thoughts</h3><p>Overall, I thought the exam was done well. It’s not too long, and the questions are good Architect-level questions: it’s about being able to architect solutions, not necessarily memorizing every low-level command. With that said, a few final thoughts as you prepare for the exam:</p><ul><li>As the official exam guide notes, there are Case Studies as part of the exam. I recommend preparing yourself by reading those and figuring out how to define the requirements in each and how those requirements match up to GCP services.</li><li>Know this decision tree well, and understand when to use what:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5Uxr7B6K-Kolz-E3KGWHA.png" /></figure><ul><li>Don’t forget about services like Dataflow, Dataproc, Pub/Sub, and other Big Data concepts.</li><li>Like with similar exams, there will be several good options and a best option. Make sure to really dive into each question to understand specific requirements that will help you determine which is best. You really need to know when to use X and when to use Y, even if Y would kind of work.</li><li>Get into Google Cloud Platform and build something! There’s nothing better than real-world experience, and Google makes it really easy to get in and use the platform for free.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ab327b62bc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up an IPsec VPN to Google Cloud with Libreswan & Ubiquiti EdgeRouter]]></title>
            <link>https://medium.com/@earlg3/setting-up-an-ipsec-vpn-to-google-cloud-with-libreswan-ubiquiti-edgerouter-39f064559fcb?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f064559fcb</guid>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Sun, 19 Mar 2017 01:32:50 GMT</pubDate>
            <atom:updated>2017-03-19T01:32:50.279Z</atom:updated>
            <content:encoded><![CDATA[<p>The <a href="https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations">best practice</a> for setting up a Site-to-Site IPsec VPN with Google Cloud is to use the <a href="https://cloud.google.com/compute/docs/vpn/overview">Cloud VPN</a> service. The Cloud VPN service within GCP provides a 99.9% SLA and is managed by Google on their side. It, however, costs a flat <a href="https://cloud.google.com/compute/pricing">$0.05/hr per tunnel</a> plus regular traffic rates, so if using 24/7 would cost $36.50, which is certainly reasonable for a production environment. For testing or lab purposes, a Google Compute Engine (GCE) instance can perform the VPN functionality as well, at a lower cost.</p><p>For lab purposes where substantial throughput isn’t required, the <a href="https://cloud.google.com/free/docs/always-free-usage-limits">Always Free</a> f1-micro instance that is part of the <a href="https://cloud.google.com/free/">GCP Free Tier</a> can do the trick. The <a href="https://cloud.google.com/compute/docs/machine-types">f1-micro</a> has 1 shared vCPU and .6GB of RAM, but will work for testing and lab usage. In this scenario, since the f1-micro is free, the cost will be the regular traffic rates and anything that goes beyond the Always Free tier restrictions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*sbzPHLK9cpogeigpTz1l0w.png" /><figcaption>GCP Internet Egress Rates</figcaption></figure><p>With that said, theoretically, this GCE setup could be configured with redundancy with multiple higher-powered instances if scripts were set up to monitor the VPN and manage failover, and all that jazz. It would be tedious, though, so for production just use the Google Cloud VPN.</p><p>The following guide will walk through the steps to connect a Google Compute Engine (GCE) instance running Libreswan to a separate network with a <a href="https://www.ubnt.com/edgemax/edgerouter/">Ubiquiti EdgeRouter</a>. There is nothing requiring a Ubiquiti device on the other end, but it’s a popular lab router and avoids having to manage a virtual machine on the other side. If there is something else preferred on the other end, it should be trivial to swap it in. This example is similar to the behavior described in AWS’ “<a href="https://aws.amazon.com/articles/5472675506466066">Connecting Multiple VPCs with EC2 Instances</a>” tutorial, for reference.</p><p>Without any further ado, let’s begin. We’ll go through the following:</p><ol><li>Creating the GCE Instance for Libreswan</li><li>Configuring the GCE Instance for Libreswan</li><li>Configuring Ubiquiti EdgeOS</li><li>Confirming Direct Connectivity</li><li>Creating GCP Route for Network to Connect</li><li>Confirming Network Connectivity</li></ol><p>The following are the parameters used in this example setup, but should be changed to match the actual environment:</p><pre><strong>GCE Instance Name:</strong> gcp-vpn-01<br><strong>GCE Instance IP (Internal):</strong> 10.1.2.2<br><strong>GCE Instance IP (External):</strong> 35.185.42.90<br><strong>GCP XPN Network Range:</strong> 10.1.0.0/16</pre><pre><strong>Lab External IP:</strong> 104.139.101.201<br><strong>Lab Network Range:</strong> 192.168.1.0/24</pre><h3>Creating the GCE Instance for Libreswan</h3><h4>Overview</h4><p>Create the instance in your <a href="https://cloud.google.com/compute/docs/xpn/">XPN Host Project</a>, if using Cross Project Networking; if only aiming to create the VPN for a single project, simply create it in that project.</p><p>CentOS 7 was chosen as the distribution in this example, so if using Debian or Ubuntu then the commands shown will change slightly in regards to package managers used, as well as possibly location of files, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*6pbNeOVZSRDPjOheNg27sA.png" /><figcaption>GCP VPN Instance Overview</figcaption></figure><h4>Networking</h4><p>If you have setup <a href="https://cloud.google.com/compute/docs/xpn/">Cross Project Networking (XPN)</a>, putting the GCE VPN Instance within the XPN Network will let service projects be able to use the connectivity, as opposed to only usable within a single project.</p><p>When creating the GCE instance, ensure a Static IP is chosen instead of ephemeral so that when the instance reboots there is no need to change IPs. Make a note of the static IP given (e.g. 35.185.42.90) as it will be used during setup. Also, make note of the subnet range(s) we will be connecting on the GCP side (e.g. 10.1.0.0/16).</p><p>You also need to ensure “<a href="https://cloud.google.com/compute/docs/networking?hl=en_US&amp;_ga=1.162115964.1935625925.1489866303#canipforward">IP forwarding</a>” is turned on. This is equivalent to “Disable Source / Destination Check” in AWS, and allows the instance to route traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*8E7GdqLVDGLcg9aI_SSYcQ.png" /><figcaption>Networking Settings for GCP VPN Instance</figcaption></figure><p>Ideally, be sure to create appropriate firewall rules to only allow the GCE VPN instance to communicate only to other networks that are approved. Leaving the VPN instance open to the world is not recommended.</p><h3>Configuring the GCE Instance for Libreswan</h3><p>Once the instance is provisioned, proceed to log in through SSH.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*ZJoSz-FUfeaw_Mjf7l_3pg.png" /><figcaption>GCP VPN Instance Created</figcaption></figure><h4>Install libreswan</h4><p>Depending on your distribution, installing “openswan” will either install openswan or libreswan, but both seem mostly compatible. Run the following command within the GCP instance to install openswan: sudo yum install openswan -y</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*I_NUcNxLre-2ITw15rr8UQ.png" /><figcaption>Libreswan Installed</figcaption></figure><h4>Configure Openswan</h4><p>By default libreswan includes any configuration files under /etc/ipsec.d/*.conf. We are going to create gcp-to-lab.conf and put our configuration in here.</p><pre>conn gcp-to-lab <br>    type=tunnel <br>    authby=secret <br>    left=%defaultroute <br>    leftid=35.185.42.90<br>    leftnexthop=%defaultroute <br>    leftsubnet=10.1.0.0/16 <br>    right=104.139.101.201 <br>    rightsubnet=192.168.1.0/24 <br>    pfs=yes <br>    auto=start</pre><p>We also need a .secrets file that will include our Pre-Shared Key. Create gcp-to-lab.secrets inside /etc/ipsec.d/.</p><pre>35.185.42.90 104.139.101.201: PSK “PRESHARED_KEY_HERE”</pre><p>After both files are created, you should see them both and a few default files inside /etc/ipsec.d/:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*n33Vf31vdsU9gaPkx0lfHw.png" /><figcaption>Configured Openswan /etc/ipsec.d/ Folder</figcaption></figure><h4>Start Openswan</h4><p>Start up openswan by executing: sudo systemctl start ipsec.service</p><p>If you run ps ax|grep ipsec, you should now see it running:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*Rs24XGyywXC18YfMHY_88g.png" /><figcaption>Openswan Running</figcaption></figure><p>Enable Openswan to start at boot with: sudo systemctl enable ipsec.service</p><p>Add the following to /etc/sysctl.conf:</p><pre>net.ipv4.ip_forward = <strong>1</strong><br>net.ipv4.conf.all.accept_redirects = <strong>0</strong><br>net.ipv4.conf.all.send_redirects = <strong>0</strong></pre><p>Restart networking: sudo /etc/initd.network restart</p><p>At this point the GCP instance is configured, so let’s move to the Ubiquiti confiruation.</p><h3>Configuring Ubiquiti EdgeOS</h3><p>Log in to EdgeMAX through the GUI; this could also be configured through CLI, but the GUI is pretty simple.</p><p>Navigate to the VPN section of the EdgeRouter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*iQtd7Ohz8L2t4a8_YGLKbg.png" /><figcaption>VPN Tab Screenshot</figcaption></figure><p>Select the “IPsec Site-to-Site” tab, configure the Peer settings, and then select “Apply”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*8zS8no5MSIDYJJS5LLu-Pg.png" /><figcaption>Example VPN Configuration Settings (*PSK is temporary for demonstration purposes)</figcaption></figure><h3>Confirming Direct Connectivity</h3><p>Reboot the GCP Instance to make sure Libreswan starts at boot and connects properly.</p><p>After rebooting, log in and run the following: service ipsec status. Status showing “IPsec SA established tunnel mode” should be displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*vLt_UBphAhGhZcYaiffSMg.png" /><figcaption>Successful Openswan Status</figcaption></figure><p>Try to ping the lab network (e.g. 192.168.1.100) from the GCP VPN instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*tlG1Y2iKUwFpz1Ova6lpFg.png" /><figcaption>Successfully Pinging Lab from GCP</figcaption></figure><p>Try to ping the GCP VPN from the lab network:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*6gqphwpb3eK74V5-DNd-ag.png" /><figcaption>Successfully Pinging GCP from Lab</figcaption></figure><h3>Creating GCP Route for Network to Connect</h3><p>Up until this point, a VPN has been created between the GCP Instance (i.e. gcp-vpn-01) and the Lab Network (192.168.1.0/24), but the rest of the GCP network has not been configured to be able to reach the Lab Network. To solve this, we need to create a route within GCP Networking.</p><p>Navigate to Networking -&gt; Routes within the Host Project. Select “Create Route”. Configure the route similar to the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*RLuY7ff7dBYrafQ5dJOTaA.png" /><figcaption>Example Route to Lab Network through VPN Instance</figcaption></figure><h3>Confirming Networking Connectivity</h3><p>From an unrelated Google Compute Engine instance, try to ping to the Lab Network. It should be successful:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*o_IKav-6dujIRGjiAR3gJA.png" /><figcaption>Successful VPN Connectivity from GCP Network to Lab Network</figcaption></figure><p>And vice versa:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*qakOCE-Yhy9OWpvdQF6cfQ.png" /><figcaption>Successful VPN Connectivity from Lab Network to GCP Network</figcaption></figure><h3>Final Thoughts</h3><p>Connectivity between the Lab Network and the GCP Network has now been set up. There is no redundancy, and if either the EdgeRouter or the GCE instance go down then the VPN network connection goes down. The GCE instance configured is small, so performance is not the goal. That said, if testing or requirements allow for those caveats, it’s a nice and comparatively inexpensive connection between a lab and the GCP network.</p><p>For production, use <a href="https://cloud.google.com/compute/docs/vpn/overview">Google Cloud VPN</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f064559fcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Next ’17 and the Future of GCP]]></title>
            <link>https://medium.com/@earlg3/google-cloud-next-17-and-the-future-of-gcp-cbd31f15a952?source=rss-eabbaa1967dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbd31f15a952</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Earl Gay]]></dc:creator>
            <pubDate>Mon, 13 Mar 2017 22:01:23 GMT</pubDate>
            <atom:updated>2017-03-13T22:01:23.367Z</atom:updated>
            <content:encoded><![CDATA[<p>If you haven’t seen them yet, the <a href="https://www.youtube.com/playlist?list=PLIivdWyY5sqI8RuUibiH8sMb1ExIw0lAR">sessions from Google Cloud Next ’17</a> are all on YouTube. They actually managed to post the sessions on the same days they were held, which is amazing turnaround time compared to most conferences.</p><h3>Earl Gay on Twitter</h3><p>After binge watching #GoogleNext17 sessions on YouTube, competition&#39;s biggest fear should rise from quantity of top talent @googlecloud has.</p><p>As I posted on Twitter, the sessions and Google speakers were spectacular, and you should watch the videos and verify for yourself if you can. The talent that Google has is tremendous, and it should be a concern for AWS and Azure competitively.</p><p>That said, the Google Cloud Platform hasn’t had the fanfare that AWS or even Azure has had recently. Some of that is due to their perceived inability to understand the Enterprise market, which Google is working to solve with their hiring of ex-VMware CEO Diane Greene; some of that was due to their previous support models and processes, which they’ve turned around over recent years including <a href="http://www.pcworld.com/article/3180175/cloud-computing/heres-why-google-cloud-support-is-now-priced-per-person.html">announcing even better support model/plans at Next</a>.</p><p>Nevertheless, the perception and corresponding reality of GCP’s place in the pecking order exists… but I think that’s going to change quickly. GCP is maturing, and it’s doing so fast. According to Eric Schmidt in the keynote, Google has spent $30 billion on GCP, so they’re committed.</p><p>I’ll start by thanking Google for their YouTube’s 2x speed playback functionality that made catching up on the sessions more enjoyable. After diving into the sessions and starting to tinker with GCP more, I wanted to share some of the big differentiators that GCP has.</p><p>The list below is going to include things that existed before Google Next ’17, as well as announcements at Google Next ’17. These are just a couple of things that I think are unique differentiation in the Cloud Wars.</p><h3>Pricing</h3><h4>Sustained Use Discounts</h4><p>Google has had <a href="https://cloud.google.com/compute/pricing#sustained_use">Sustained Use Discounts</a> for awhile, which are the simplest approach to saving money via usage of any of the big providers, as it’s automatic and requires no upfront commitment. Sustained Use Discounts (SUD) basically work by providing a discount for instances that have been running for at least 25% of the time, with additional discounts the more the instance is used per billing cycle. For example, an instance running 100% of the month would automatically get 30% off. GCP also uses “Inferred Instances” to combine multiple, non-overlapping instances in the same zone into a single instance to maximum SUD benefits. The instance pricing for Google is also Per-Minute compared to Per-Hour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*lEEXvVNpJj8iRM3Jaksymg.png" /><figcaption>Effective discount increases with use under Google’s Sustained Use Discount</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*gbpXEVulidRjNp6tURR45g.png" /><figcaption>Inferred Instances Example Calculation</figcaption></figure><h4>Committed Use Discounts</h4><p>Google announced the release of <a href="https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts">Committed Use Discounts</a> at Next. Committed Use Discounts work by purchasing a committed amount of vCPUs and RAM. The vCPUs and RAM can then be used across instances at your discretion on all non-shared core machine types in a region. Discounts up to 57% can be had with Committed Use Discounts versus full price. This contrasts with AWS’ approach of Reserved Instances which have a bit less flexibility. Currently, none of the big competitors offer pricing discounts similar to this.</p><h4>Always Free Tier</h4><p>Google Cloud Platform also announced their expanded <a href="https://cloud.google.com/free/">Free Tier</a> that allows $300 free trial credit would extend to 12 months, but the best part is they have announced their “Always Free” tier. This “Always Free” collection includes things like 1 f1-micro instance per month, 5 GB-months of Regional Google Cloud Storage, 1GB of Google Cloud Datastore, and more. Full list available on the <a href="https://cloud.google.com/free/docs/always-free-usage-limits">Always Free Usage Limits page</a>.</p><h3>User Interface &amp; User Experience</h3><h4>Google Cloud Shell</h4><p><a href="https://cloud.google.com/shell/docs/">Google Cloud Shell</a> is not something new, but it’s something as an administrator I enjoy. The Cloud Shell provides CLI access directly inside the GCP UI to run “gcloud” commands and other utilities (e.g. mysql client, etc). It’s also a session you don’t have to pay for, and comes with 5GB persistent disk storage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*k143zg_zYAaGPcwxhmIYIw.png" /><figcaption>Google Cloud Shell listed all installed Cloud SDK Components</figcaption></figure><h4>Equivalent REST or Command Line Display</h4><p>Whenever you perform an action in the GCP UI, there is a link to see the equivalent REST and CLI commands that would be performed. These commands can be used instead of clicking “Apply” if desired, but it’s all formulated based on your settings defined in the GUI. Very neat compared to having to figure out the command line or API call on your own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*hKlLkp6ioxy3cCDo7YpCoQ.png" /><figcaption>Generate Equivalent REST of Command Line Buttons on Wizards</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*_rJkIbVs3fpMmuZiX1Ymwg.png" /><figcaption>Equivalent REST Request Example for Creating GCE Instance</figcaption></figure><h4>Google Cloud Deployment Manager</h4><p>GCP’s equivalent to AWS CloudFormation is <a href="https://cloud.google.com/deployment-manager/docs/">Google Cloud Deployment Manager</a>. It uses YAML versus JSON, so I am naturally a fan based on the readability of YAML comparatively.</p><h4>Projects</h4><p>Google groups resources into <a href="https://cloud.google.com/resource-manager/docs/creating-managing-projects">Projects</a> instead of tying everything to Accounts like AWS. Depending on your perspective, this could be a benefit. <a href="https://cloud.google.com/compute/docs/xpn/">Cross Project Networking (XPN)</a> is still in beta which allows cross project networking as the name implies, and while the documentation breaks it down it comes off as a not as nice as <a href="https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-peering.html">VPC Peering</a> among accounts with AWS.</p><h3>Technical Goodies</h3><h4>Live Migration</h4><p><a href="https://cloudplatform.googleblog.com/2015/03/Google-Compute-Engine-uses-Live-Migration-technology-to-service-infrastructure-without-application-downtime.html">Not a new feature</a>, but if there is maintenance required on the host where your GCE instance runs, Google can Live Migrate it without disruption. If that happens in AWS, you need to restart your instance on a new host as there is no live migration.</p><h4>Custom Instance Sizes</h4><p>Google Compute Engine is not bound to pre-configured instance sizes, although they do have them as options (e.g. f1-micro). Instead, you get a slider to select CPU and RAM. This isn’t completely customizable, because you can only do 6.5GB of RAM per vCPU to avoid tilting too far in one direction, but the customization is nice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*B4fOOe5vGHRDtbaexbw6mQ.png" /><figcaption>GCE Instance Size Sliders</figcaption></figure><h4>Open Standards</h4><p>Google is big on Open Source and Open Standards. The release a lot of research as a company, and there are <a href="https://developers.google.com/open-source/projects">A LOT of popular open source projects</a> released by Google.</p><h4>Cloud Spanner</h4><p>“<a href="https://cloud.google.com/spanner/docs/">Google Cloud Spanner</a> is a fully managed, mission critical, relational database service that offers transactional consistency at global scale, schemas, SQL, and automatic, synchronous replication for high availability.” That’s the formal definition of Cloud Spanner, but the informal definition is that it’s a way to do massive relational databases at global scale easily. It’s a unique solution.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Famcf6W2Xv6M%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Damcf6W2Xv6M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Famcf6W2Xv6M%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/289d9b6d09b1b5ef924471b05127b838/href">https://medium.com/media/289d9b6d09b1b5ef924471b05127b838/href</a></iframe><h4>The Entire Google Cloud Platform</h4><p>I’m not going to go nearly as deep as one should on the technical goodies in GCP, so you’ll need to dig for yourself into awesome solutions like <a href="https://cloud.google.com/appengine/">App Engine</a>, <a href="https://cloud.google.com/functions/">Cloud Functions</a>, <a href="https://cloud.google.com/bigquery/">BigQuery</a>, <a href="https://cloud.google.com/products/machine-learning/">Machine Learning</a>, and more. Big Data and Machine Learning are areas where Google is naturally very strong, and will lead the way.</p><p><strong>There is a lot to the platform: in the words of Google, “<em>Cloud Platform is what brings Google’s innovation and infrastructure to you.</em>”</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbd31f15a952" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>