<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on Gerard Samuel</title><link>https://gerardsamuel.me/categories/cloud/</link><description>Recent content in Cloud on Gerard Samuel</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 25 Nov 2024 13:20:59 -0500</lastBuildDate><atom:link href="https://gerardsamuel.me/categories/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Cloud Workload Identities with GitLab</title><link>https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/</link><pubDate>Mon, 25 Nov 2024 13:20:59 -0500</pubDate><guid>https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/</guid><description>&lt;p&gt;Using JSON keys to authenticate with Google Cloud is highly frowned upon. Unless you have no other &lt;a href="https://cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys" target="_blank" rel="noreferrer"&gt;option&lt;/a&gt;, Google Cloud provides a more secure means of authenticating externally executed code. My use case is for authentication in GitLab pipelines so that I can automate tasks. Think Terraform jobs or updating the files for a website stored in a Google Cloud storage bucket. I will use Google Cloud&amp;rsquo;s Workload Identity Federation solution and the OIDC (Open ID Connect) &lt;a href="https://openid.net/developers/how-connect-works/" target="_blank" rel="noreferrer"&gt;protocol&lt;/a&gt; in this solution.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/featured.png"/></item><item><title>Google Cloud federation with Microsoft Entra ID - Part 2</title><link>https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part2/</link><pubDate>Sat, 14 Sep 2024 13:23:00 -0500</pubDate><guid>https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part2/</guid><description>&lt;p&gt;In my previous &lt;a href="https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part1/" &gt;article&lt;/a&gt; on Google Cloud federation and account provisioning with Microsoft Entra ID, I showed how to get started to configure it. This article constitutes the second part, utilizing &lt;a href="https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language" target="_blank" rel="noreferrer"&gt;SAML&lt;/a&gt; authentication to complete the solution.
Once you complete the steps here, you will have a secure means of logging into Google Cloud with your Entra ID account.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part2/featured.svg"/></item><item><title>Google Cloud federation with Microsoft Entra ID - Part 1</title><link>https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part1/</link><pubDate>Sat, 07 Sep 2024 10:52:59 -0500</pubDate><guid>https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part1/</guid><description>&lt;p&gt;I wanted to use a single account to log into my Azure and Google Cloud environments and automatically provision &amp;ldquo;source of truth&amp;rdquo; accounts from Entra ID to Google Cloud Identity. This article will explain how I configured account provisioning of the identity federation solution between Microsoft Entra ID and Google Cloud Identity.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/how-to-federate-google-cloud-entra-id-part1/featured.svg"/></item><item><title>Google Document AI: Bulk Import and Results</title><link>https://gerardsamuel.me/posts/google-document-ai-bulk-import-and-results/</link><pubDate>Mon, 20 Nov 2023 15:51:08 -0400</pubDate><guid>https://gerardsamuel.me/posts/google-document-ai-bulk-import-and-results/</guid><description>&lt;p&gt;Continuing from my last post on &lt;a href="https://gerardsamuel.me/posts/google-document-ai-how-to-get-started/" &gt;Document AI&lt;/a&gt;, I am going to show what the bulk import experience is like and a peek at the extracted data.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/google-document-ai-bulk-import-and-results/featured.webp"/></item><item><title>Google Document AI: How to Get Started</title><link>https://gerardsamuel.me/posts/google-document-ai-how-to-get-started/</link><pubDate>Wed, 18 Oct 2023 15:16:01 -0400</pubDate><guid>https://gerardsamuel.me/posts/google-document-ai-how-to-get-started/</guid><description>&lt;p&gt;Document AI is a Google Cloud solution that imports structured data from unstructured or semi structured documents.
The output can then be treated as first class data citizens for analysis with your other data sources to gain deeper insight from your “dark” document data.
In this first post on Document AI, I will go over the initial steps to get started.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/google-document-ai-how-to-get-started/featured.webp"/></item></channel></rss>