<?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 Azidin Shairi on Medium]]></title>
        <description><![CDATA[Stories by Azidin Shairi on Medium]]></description>
        <link>https://medium.com/@azidin?source=rss-840bcd912661------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FyyzAeaioPQg3wxLRVfosw.png</url>
            <title>Stories by Azidin Shairi on Medium</title>
            <link>https://medium.com/@azidin?source=rss-840bcd912661------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:43:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azidin/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[Zero Trust CI/CD: Keyless Bitbucket Deployment on Google Cloud]]></title>
            <link>https://medium.com/google-cloud/zero-trust-ci-cd-keyless-bitbucket-deployment-on-google-cloud-c4711281c23f?source=rss-840bcd912661------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4711281c23f</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Azidin Shairi]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 15:23:13 GMT</pubDate>
            <atom:updated>2026-10-30T09:25:37.824Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phhqFZXjL6irXU6KmDAvYQ.png" /></figure><p>Using static Service Account (SA) keys in CI/CD pipelines has long been a common method for authenticating to Google Cloud Platform (GCP). However, storing long-lived credentials inside external pipeline environment variables introduces severe security vulnerabilities and ongoing operational friction.</p><p>Google Mandiant demonstrated in a threat intelligence blog post (<a href="https://cloud.google.com/blog/topics/threat-intelligence/bitbucket-pipeline-leaking-secrets">Holes in Your Bitbucket: Why Your CI/CD Pipeline Is Leaking Secrets</a>) that secret variables in Bitbucket pipelines can easily be extracted from environment variables during runtime. Moving away from static JSON keys toward Google Cloud Workload Identity Federation (WIF) provides a modern, keyless authentication mechanism that leverages OpenID Connect (OIDC) to exchange short-lived tokens, eliminating the risks associated with static credential management.</p><h3>Why Service Account Keys Are a Bad Security Practice</h3><p>While Atlassian Bitbucket documentation describes <a href="https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-google-cloud/">deployment to Google Cloud using Service Account keys</a>, relying on traditional static JSON key files introduces two fundamental security and operational flaws:</p><p><strong>High Security Risk &amp; Lack of Traceability:</strong> Service account keys do not expire automatically and carry persistent security exposure. They lack strict origin traceability and can easily be copied, downloaded, or exfiltrated to execute commands anywhere outside Bitbucket without network restrictions or audit context. If a key is compromised, malicious actors gain unrestricted access until it is manually identified and revoked.</p><p><strong>Management &amp; Operational Overhead:</strong> Even if key expiration limits are configured, security compliance mandates continuous key lifecycle management, including periodic rotation and distribution across multiple repositories and workspaces. This creates substantial administrative overhead for platform engineering teams and risks pipeline failures when keys expire or are revoked prematurely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hb22pMwy68bQQkvqIAnzg.png" /><figcaption>Hiding it behind wildcards make it secure does it?</figcaption></figure><h3>Introducing Workload Identity Federation (WIF)</h3><p>Workload Identity Federation establishes direct federated trust between Atlassian Bitbucket, acting as the Identity Provider and Google Cloud using OpenID Connect (OIDC) over the OAuth 2.0 framework. While OAuth 2.0 handles authorization, deciding what resources can be accessed, OIDC adds authentication verifying identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*Wdn6ap3RtKmLJIeTwqdfZQ.png" /></figure><p>Key benefits of WIF include:</p><ul><li><strong>Short-Lived Token Exchange:</strong> Bitbucket generates a temporary OIDC identity token for each pipeline step. Workload Identity Federation validates this token and exchanges it for a short-lived access token to Google Cloud, valid strictly for the duration of the job.</li><li><strong>Fine-Grained Scope Control:</strong> Access permissions can be tightly scoped per Bitbucket workspace, project, repository, or down to a specific deployment environment pipeline (e.g., staging vs. production).</li></ul><h3>Migrating Bitbucket Pipelines from using Service Account Keys to Google Cloud Workload Identity Federation</h3><p>Before configuring Workload Identity Federation, gather your Bitbucket workspace OIDC configurations from your repository admin setting page.</p><p>You will need the following details from Bitbucket Workspace :</p><ul><li><strong>Identity Provider URL: </strong>https://api.bitbucket.org/2.0/workspaces/WORKSPACE_ID/pipelines-config/identity/oidc</li><li><strong>Audience: </strong>ari:cloud:bitbucket::workspace/WORKSPACE_UUID</li></ul><p>Bitbucket issues an OIDC token claim payload during pipeline execution structured as follows:</p><pre>{<br> &quot;sub&quot;: &quot;{REPOSITORY_UUID}:{stepUuid}&quot;,<br> &quot;aud&quot;: &quot;ari:cloud:bitbucket::workspace/WORKSPACE_UUID&quot;,<br> &quot;stepUuid&quot;: &quot;{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}&quot;,<br> &quot;iss&quot;: &quot;https://api.bitbucket.org/2.0/workspaces/WORKSPACE_ID/pipelines-config/identity/oidc&quot;,<br> &quot;repositoryUuid&quot;: &quot;{REPOSITORY_UUID}&quot;,<br> &quot;branchName&quot;: &quot;xxxxxxxxx&quot;,<br> &quot;exp&quot;: &quot;xxxxxxxxxx&quot;,<br> &quot;iat&quot;: &quot;xxxxxxxxxx&quot;,<br> &quot;pipelineUuid&quot;: &quot;{xxxxx-xxxxx-xxxx-xxxx-xxxxxxxxxxx}&quot;,<br> &quot;workspaceUuid&quot;: &quot;{WORKSPACE_UUID}&quot;<br>}</pre><p>Bitbucket OpenID Connect settings page looks like this: <a href="https://bitbucket.org/WORKSPACE_ID/REPO_ID/admin/pipelines/openid-connect">https://bitbucket.org/WORKSPACE_ID/REPO_ID/admin/pipelines/openid-connect</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAhh3o9Cvy8x3ka0G_xDuA.png" /><figcaption>O.I.D.C.</figcaption></figure><h4>Step 1: Enable and Set Up WIF in Target GCP Projects</h4><p>To establish federated authentication between Bitbucket Pipelines and GCP, create a Workload Identity Pool and Provider in your target GCP project.</p><p><strong>1.1 Create a Workload Identity Pool</strong></p><p>Create a global Workload Identity Pool dedicated to Bitbucket:</p><pre>gcloud iam workload-identity-pools create bitbucket \<br>    --location=&quot;global&quot; \<br>    --description=&quot;Bitbucket Workload Identity Pool&quot; \<br>    --display-name=&quot;Bitbucket&quot;</pre><p><strong>1.2 Create the Workload Identity Provider</strong></p><p>Configure an OIDC provider that trusts Bitbucket’s issuer URL and maps claims (such as workspace UUID, repository UUID, and deployment environment) to Google attributes:</p><pre>gcloud iam workload-identity-pools providers create-oidc bitbucket \<br>    --location=&quot;global&quot; \<br>    --display-name=&quot;Bitbucket&quot; \<br>    --description=&quot;Bitbucket Identity Provider&quot; \<br>    --workload-identity-pool=&quot;bitbucket&quot; \<br>    --issuer-uri=&quot;https://api.bitbucket.org/2.0/workspaces/WORKSPACE_ID/pipelines-config/identity/oidc&quot; \<br>    --allowed-audiences=&quot;ari:cloud:bitbucket::workspace/WORKSPACE_UUID&quot; \<br>    --attribute-mapping=&quot;google.subject=assertion.sub,attribute.workspace_uuid=assertion.workspaceUuid,attribute.repository_uuid=assertion.repositoryUuid,attribute.deployment_env_uuid=assertion.deploymentEnvironmentUuid&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2xghjFvqflee_LBqBVbrg.png" /></figure><p><strong>1.3 Map Bitbucket Identity to the GCP Service Account</strong></p><p>Grant your Bitbucket Workspace permission to impersonate the target GCP existing Service Account by binding the roles/iam.workloadIdentityUser role:</p><pre>gcloud iam service-accounts add-iam-policy-binding bitbucket-pipelines@PROJECT_ID.iam.gserviceaccount.com \<br>    --role=roles/iam.workloadIdentityUser \<br>    --member=&quot;principalSet://iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/bitbucket/attribute.workspace_uuid/{WORKSPACE_UUID}&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d1deJF1-9LkaMxOHrmUyoQ.png" /><figcaption>Workload Identity Pool and Service Account Mapping</figcaption></figure><h4>Step 2: Update Bitbucket Pipelines to Use OIDC Authentication</h4><p>Once Workload Identity Federation and the Identity Pool are configured, update your bitbucket-pipelines.yml configuration.</p><p><strong>Legacy Pipeline Configuration (Using Static SA Keys):</strong></p><pre>pipelines:<br>  default:<br>    - step:<br>        name: Deployment Step<br>        script:<br>          - gcloud auth activate-service-account --key-file &lt;(echo &quot;${GCLOUD_DEPLOYER_KEYFILE}&quot; | base64 --decode --ignore-garbage)<br>          - gcloud config set project $GCLOUD_PROJECT</pre><p>To migrate your pipeline to OIDC authentication, first update each pipeline step requiring Google Cloud access by enabling oidc: true. This allows Bitbucket to generate an OIDC token during execution, which you then export from the $BITBUCKET_STEP_OIDC_TOKEN environment variable to a temporary file for gcloud usage.</p><p>Next, update your authentication commands by switching</p><p>from gcloud auth activate-service-account --key-file=file.json</p><p>to gcloud auth login --cred-file=file.json.</p><p>Finally, update your workspace variables to replace the legacy key variable (GCLOUD_DEPLOYER_KEYFILE) with a reference pointing to your credential configuration file (GCLOUD_DEPLOYER_CREDFILE).</p><p><strong>Migrated Pipeline Configuration (Using Keyless WIF via OIDC):</strong></p><pre>pipelines:<br>  default:<br>    - step:<br>        name: Deployment Step with OIDC<br>        oidc: true<br>        script:<br>          - echo $BITBUCKET_STEP_OIDC_TOKEN &gt; /tmp/bitbucket-step-oidc-token.txt<br>          - gcloud auth login --cred-file &lt;(echo &quot;$GCLOUD_DEPLOYER_CREDFILE&quot;)<br>          - gcloud config set project $GCLOUD_PROJECT</pre><h4>Step 3: Remove Bitbucket Workspace Level GCP SA Keys</h4><p>After validating that the updated pipeline runs and authenticates successfully using Workload Identity Federation, navigate to your Bitbucket Workspace or Repository Settings to permanently delete the legacy Service Account key variables, such as GCLOUD_DEPLOYER_KEYFILE.</p><p>Finally, navigate to the Google Cloud Console or run gcloud iam service-accounts keys delete to revoke and delete the corresponding static Service Account JSON keys from GCP.</p><h3><strong>Summary &amp; Best Practices</strong></h3><p>Migrating from static Service Account keys to Workload Identity Federation aligns your CI/CD workflows with Zero Trust security principles. By enforcing keyless authentication with short-lived OIDC tokens, you eliminate secret leakage risks, remove rotation management overhead, and gain fine-grained control over your Google Cloud deployments.</p><p>To maximize your security posture during and after migration:</p><ul><li><strong>Apply Least Privilege:</strong> Restrict IAM role permissions on target GCP Service Accounts to only the explicit roles required for deployment.</li><li><strong>Leverage Fine-Grained Attribute Mappings:</strong> Use WIF attribute conditions to strictly isolate non-production environments from production infrastructure based on repository UUIDs, branch names, or deployment environments.</li><li><strong>Audit Organization Workflows:</strong> Review active pipelines across your repositories to ensure all legacy gcloud auth activate-service-account commands and static key variables are fully removed.</li></ul><h3>Reference links:</h3><ul><li><a href="https://cloud.google.com/blog/topics/threat-intelligence/bitbucket-pipeline-leaking-secrets">Google Mandiant: Bitbucket Pipeline Leaking Secrets</a></li><li><a href="https://cloud.google.com/iam/docs/workload-identity-federation">Managing Workload Identity Federation in GCP</a></li><li><a href="https://support.atlassian.com/bitbucket-cloud/docs/integrate-pipelines-with-resource-servers-using-oidc/">Atlassian Support: Integrate Bitbucket Pipelines with Resource Servers Using OIDC</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4711281c23f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/zero-trust-ci-cd-keyless-bitbucket-deployment-on-google-cloud-c4711281c23f">Zero Trust CI/CD: Keyless Bitbucket Deployment on Google Cloud</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure Your GKE Control Plane: Migrating from IP-Based Authorized Networks to IAM-Based DNS…]]></title>
            <link>https://medium.com/google-cloud/how-to-migrate-gke-control-plane-access-from-ip-based-authorization-to-dns-endpoint-7c62b86891a3?source=rss-840bcd912661------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c62b86891a3</guid>
            <category><![CDATA[kubernetes-security]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Azidin Shairi]]></dc:creator>
            <pubDate>Fri, 31 Oct 2025 22:00:13 GMT</pubDate>
            <atom:updated>2025-11-03T03:00:58.709Z</atom:updated>
            <content:encoded><![CDATA[<h3>Secure Your GKE Control Plane: Migrating from IP-Based Authorized Networks to IAM-Based DNS Endpoint Access</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dIH_J-8WR14huE9fAn9ZfQ.png" /></figure><p>The GKE DNS-based endpoint provides a cluster-unique FQDN (Fully Qualified Domain Name) for the Kubernetes control plane, allowing for simplified, IAM-based access control instead of relying on static IP-based authorized networks. This guide outlines the steps to enable this feature and transition your access methods.</p><p>The DNS-Based Endpoint offers several advantages over the IP-Based Endpoint with Authorized Networks for accessing Google Cloud clusters. While IP-based access relies on source IP CIDR blocks and often requires bastion hosts or VPN for private clusters, the DNS-based approach uses Google Cloud IAM and is accessible from any network that can reach Google Cloud APIs. This provides a more flexible and dynamic access control model, integrated with IAM and VPC Service Controls for enhanced security, compared to the primarily network-layer security of IP-based endpoints.</p><p>This guide walks through the steps to enable the DNS endpoint on an existing GKE cluster and migrate the access to it. We’ll use a GKE cluster named gke-test-cluster-1, deployed in the GCP Finland region, zone europe-north1-a.</p><p><strong>Step 1: Enable the DNS-Based Endpoint</strong></p><p>You can enable the DNS-based endpoint on an existing GKE Standard or Autopilot cluster using the gcloud CLI.</p><p>First, let’s review the GKE Control Plane configuration:</p><pre>gcloud container clusters describe gke-test-cluster-1 \<br>--zone europe-north1-a --format=”yaml(controlPlaneEndpointsConfig)”</pre><p>The output should look like this:</p><pre>controlPlaneEndpointsConfig:<br>  dnsEndpointConfig:<br>    allowExternalTraffic: false<br>    enableK8sCertsViaDns: false<br>    enableK8sTokensViaDns: false<br>    endpoint: gke-CLUSTER_ID-PROJECT.europe-north1-a.gke.goog<br>  ipEndpointsConfig:<br>    authorizedNetworksConfig:<br>      cidrBlocks:<br>      - cidrBlock: ALLOWED_IP_ADDR<br>        displayName: office-network<br>      enabled: true<br>      gcpPublicCidrsAccessEnabled: true<br>    enablePublicEndpoint: true<br>    enabled: true<br>    privateEndpoint: PRV_IP_ADDR<br>    publicEndpoint: PUB_IP_ADDR</pre><p>This is the current GKE Control Plane configuration. The IP-based Endpoint is enabled for both Public and Private IPs and Authorized Network is also enabled allowing “office-network” IP addresses.</p><p>The GKE DNS Endpoint FQDN follows this format:</p><p>gke-CLUSTER_ID-PROJECT.europe-north1-a.gke.goog</p><p>However, it is currently disabled.</p><p>So let’s update the cluster to enable DNS-based access.</p><pre>gcloud container clusters update gke-test-cluster-1 \<br>--zone europe-north1-a --enable-dns-access</pre><p>It may take a few minutes for the GKE Control Plane to update with DNS Endpoint.</p><p>Once the operation is completed, you can run gcloud container clusters describe command again and should see allowExternalTraffic is enabled for dnsEndpointConfig .</p><p>Now, both IP-based and DNS-based endpoints are enabled. Both coexist at this point while we work on the next steps migrating the access from IP-based to DNS-based.</p><p><strong>Step 2: Configure IAM Access</strong></p><p>Access to the DNS endpoint is controlled by IAM. The specific IAM permission required for DNS-based access is container.clusters.connect</p><p>The permission container.clusters.connect is included in many predefined IAM roles such as “<em>Kubernetes Engine Admin</em>” and “<em>Kubernetes Engine Developer</em>”. It’s most likely your IAM user already has the permission through existing IAM roles, otherwise you were not able to update the GKE cluster in the previous step.</p><p>For other users however, your fellow developers, CI/CD pipelines and such might use other IAM roles or custom roles. In this case you need to update those roles to include the IAM permission.</p><p>As an example here if you need to add another GKE admin user, you can grant the IAM role as follow:</p><pre>gcloud projects add-iam-policy-binding $PROJECT \<br>--member=&quot;user:$GKE_ADMIN&quot; --role=&quot;roles/container.admin&quot;</pre><p><strong>Step 3: Test and Migrate Client Access</strong></p><p>Now that the GKE Control Plane DNS Endpoint is enabled and IAM roles are configured, it’s time to update clients to use the FQDN.</p><p>To make use of the DNS Endpoint in kubectl you need to refresh the kubeconfig file by fetching the new GKE cluster’s credentials:</p><pre>gcloud container clusters get-credentials gke-test-cluster-1 \<br>--zone europe-north1-a --dns-endpoint</pre><p>Take note of the --dns-endpoint parameter. This updates the kubeconfig and replaces the configuration for accessing your GKE Control Plane using FQDN instead of public IP address.</p><p>You can view the kubeconfig configuration using command:</p><pre>kubectl config view --minify</pre><p>Output:</p><pre>apiVersion: v1<br>clusters:<br>- cluster:<br>    server: https://gke-CLUSTER_ID-PROJECT.europe-north1-a.gke.goog<br>  name: gke_PROJECT_europe-north1-a_gke-test-cluster-1</pre><p>Now, run your favourite kubectl command as usual like kubectl get namespaces. If the command executed successfully it means our setup now works correctly.</p><p>Once you verified it’s working, it’s time to update all your CI/CD tools, pipelines to include --dns-endpoint parameter when fetching GKE cluster credentials, and inform your fellow GKE admins and developers to refresh their GKE cluster credentials.</p><p><strong>Step 4: Disable IP-Based Authorized Networks</strong></p><p>After you have successfully migrated all clients to using DNS Endpoint you can safely remove the IP-based authorized network along with the IP-based Endpoint. This helps keep your GKE clusters configuration clean.</p><p>There are 2 options here:</p><p>1) Disabling the Public IP Endpoint which removes the Public IP address from your GKE Control Plane.</p><p>2) Disable IP-based Endpoint completely which removes both Public and Private IP Endpoint. If you still have some other dependency on the Private IP Endpoint, you can just remove the Public IP Endpoint which improves your Control Plane security by not exposing it directly to the public.</p><p>Please note that the DNS Endpoint also works from your VPC.</p><p>Nonetheless to disable the Public IP Endpoint while keeping the Private IP Endpoint you can update the GKE cluster as follow:</p><pre>gcloud container clusters update gke-test-cluster-1 \<br>--zone europe-north1-a --enable-private-endpoint</pre><p>To disable IP-based Endpoint completely you can disable both Public IP and Private IP Endpoints as follow:</p><pre>gcloud container clusters update gke-test-cluster-1 \<br>--zone europe-north1-a --no-enable-ip-access</pre><p>Your GKE Control Plane Endpoint config will look like this after the clean up.</p><pre>controlPlaneEndpointsConfig:<br>  dnsEndpointConfig:<br>    allowExternalTraffic: true<br>    enableK8sCertsViaDns: false<br>    enableK8sTokensViaDns: false<br>    endpoint: gke-CLUSTER_ID-PROJECT.europe-north1-a.gke.goog<br>  ipEndpointsConfig:<br>    enabled: false</pre><p>With GKE Control Plane access now managed by IAM, you can use VPC Service Controls to add Context-Aware Access and further secure your GKE clusters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c62b86891a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/how-to-migrate-gke-control-plane-access-from-ip-based-authorization-to-dns-endpoint-7c62b86891a3">Secure Your GKE Control Plane: Migrating from IP-Based Authorized Networks to IAM-Based DNS…</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Centralized Monitoring and Observability in Google Cloud]]></title>
            <link>https://medium.com/google-cloud/centralized-observability-in-google-cloud-0fd30c393d97?source=rss-840bcd912661------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fd30c393d97</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Azidin Shairi]]></dc:creator>
            <pubDate>Sun, 10 Nov 2024 09:18:11 GMT</pubDate>
            <atom:updated>2025-11-03T03:00:45.296Z</atom:updated>
            <content:encoded><![CDATA[<p>Working with a few Google Cloud projects can be straightforward initially, but it becomes increasingly complicated as the number of projects grows. With several applications running across different projects and environments, accessing logs and metrics requires constant switching between projects. This repetitive process can be inefficient and cumbersome, especially during troubleshooting efforts.</p><h4>Introducing Log and Metric Scopes</h4><p>Google Cloud provides a built-in solution to solve this problem using scopes. To get started, you’ll need a Scoping Project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*85wO2LCpEVxSmTdcdiB5Gg.jpeg" /></figure><p>What’s a Scoping Project? A Scoping Project is a dedicated Google Cloud project that enables you to query all your logs and metrics across multiple projects. As the name suggests, the scope provides a view, while the telemetry data remains stored in origin log buckets and the projects where you provision your applications and are not copied to the Scoping Project.</p><h4>Configuring the Scopes</h4><p>First, let’s create a new project with a name such as “Project Monitor”. This project is dedicated to Observability purposes. Then, in the Cloud Console, navigate to <em>Observability</em> or <em>Monitoring</em> &gt; <em>Configure</em> &gt; <em>Settings. </em>You will see the option to configure Log Scopes and Metric Scope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6L0V05ms2KUCGL94p0TYSw.jpeg" /></figure><p>Then, select and add projects to the Metric Scope. After you add the projects, it will take a little while for the metrics to be visible in the Scoping Project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o_qFlUjuHmHQcIN1nc0_8g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-N9DL8trIeRM55BrudLFWA.jpeg" /><figcaption>Adding projects to Scoping Project for Metric Scope</figcaption></figure><p>Once all the metrics from Monitored Projects are populated, you can query them using Metrics Explorer. You can also filter and aggregate the metrics by Project IDs in the Metrics Explorer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eB4VMq6FsXJsTpAh8fRc7w.jpeg" /><figcaption>Group metrics by Project IDs in Metrics Explorer</figcaption></figure><p>The next step is configuring the Log Scopes. You have two options in the Log Scopes tab: add Projects or Log Views. The difference here is adding Projects will add all logs from the project you selected, whereas adding Log Views allows you to select a specific or combination of Log Views from the project. The option is useful, for example, when you want to create separate scopes for application and audit logs. So let’s try that; we create a scope for all applications logs located in the “_Default” Log Bucket and “_Default” Log View, and then another scope for all audit logs located in the “_Required” Log Bucket in “_AllLogs” Log View.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*urD6RhETUa91ecvWFBSgyw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*db3X_I1Ygbo-l4CrcKHnoA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gBOY_gPWoOmWpU9H0JF40A.jpeg" /><figcaption>Creating Log Scopes from different Log Views and Setting the Default Log Scope</figcaption></figure><p>Now, we have two new Log Scopes. For ease of use, let’s set all application Log Scope as the Default Log Scope in this Scoping Project’s Log Explorer.</p><p>Querying logs in Log Explorer will return all results for all application log events from all projects in the scope. You can change the scope in Log Explorer to query different Log Scopes you configured earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LPR49sT_KPzgWFyjkInGg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*xTpujElgbZZXz4sjPYgxKw.jpeg" /><figcaption>Log Explorer showing all logs from Default Log Scope</figcaption></figure><h4>Leveraging Log and Metric Scopes</h4><p>Now that all the logs and metrics from across multiple projects are visible in this Scoping Project, you can add them to dashboards to create a centralized view of all your application health. Predefined dashboards in the Dashboards section already recognize metrics from Monitored Projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNqZWVM-s0NHDrnPfPGGvw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlSCTVb0pSgJAg6-JvLkjA.jpeg" /><figcaption>Google Cloud Predefined Observability Dashboard showing metrics from all Monitored</figcaption></figure><p>Combining this feature with Log Analytics allows you to create dashboards with a mix of logs and metrics. You can also create SLOs based on all the metrics from the scopes. This option is handy when you have service dependencies across several projects. You can also create Alerting Policies based on the metrics visible in the Scoping Project and use this project as a single project to manage all Incidents.</p><p>To wrap up, using Scoping Project in Google Cloud makes it much easier to search for logs and metrics across multiple projects, saving you time and improving Developer Experience. You can then focus on responding to incidents more effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fd30c393d97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/centralized-observability-in-google-cloud-0fd30c393d97">Centralized Monitoring and Observability in Google Cloud</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to become a Cloud Digital Leader: Guide to the Google Cloud Digital Leader Certification 2024]]></title>
            <link>https://medium.com/@azidin/become-a-cloud-leader-guide-to-the-google-cloud-digital-leader-certification-2024-c05c72604853?source=rss-840bcd912661------2</link>
            <guid isPermaLink="false">https://medium.com/p/c05c72604853</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[gcp-certification]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[google-cloud]]></category>
            <dc:creator><![CDATA[Azidin Shairi]]></dc:creator>
            <pubDate>Tue, 02 Apr 2024 00:43:29 GMT</pubDate>
            <atom:updated>2024-11-07T22:53:58.457Z</atom:updated>
            <content:encoded><![CDATA[<p>The cloud landscape is constantly evolving, driven by advancements in AI and the critical role of data, demands businesses to leverage cloud technology effectively. The Google Cloud Digital Leader equips professionals with the knowledge to navigate this dynamic environment. This guide explores the exam format, content areas, and resources to help you earn the certification.</p><p><strong>What is the Cloud Digital Leader Certification?</strong></p><p>Cloud Digital Leader certification validates your competency in understanding Google Cloud’s core offerings and how they can empower organizations to achieve digital transformation. It’s ideal for a wide range of professionals, from technical specialists to business leaders, who want to demonstrate their proficiency in cloud fundamentals and how Google Cloud can propel business goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AuvdezbHZY-q2h3HKxWk-A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mitchel3uo?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Mitchell Luo</a> on <a href="https://unsplash.com/photos/white-and-blue-cards-on-white-surface-XQjovx-X5-k?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p><strong>Learning Path and Content Breakdown</strong></p><p>The <a href="https://cloud.google.com/learn/certification/guides/cloud-digital-leader">Cloud Digital Leader exam guide</a> outlines the six key domains you’ll need to master. This structure is mirrored in the learning path available on Cloud Skills Boost <a href="https://www.cloudskillsboost.google/paths/9">Cloud Digital Leader Learning Path</a>.</p><p>Here’s a breakdown of the six key domains covered:</p><ul><li><strong>Digital Transformation with Google Cloud:</strong> This section delves into the impact of cloud technology on businesses, covering topics like scalability, agility, and cost-effectiveness. You’ll explore the benefits of Google Cloud for digital transformation and how it compares to on-premises solutions.</li><li><strong>Exploring Data Transformation with Google Cloud:</strong> This section explores the value of data and how Google Cloud’s data management solutions empower you to make your data useful and accessible. You’ll learn about data management concepts, Google Cloud’s data solutions like BigQuery and Cloud Storage, and how to unlock insights from various data types.</li><li><strong>Innovating with Google Cloud Artificial Intelligence:</strong> This section explores the exciting world of Artificial Intelligence (AI) and Machine Learning (ML). You’ll understand how Google Cloud’s AI and ML solutions like AutoML and pre-trained APIs can automate tasks and generate valuable insights for businesses.</li><li><strong>Modernize Infrastructure and Applications with Google Cloud:</strong> Modernization is key in cloud adoption. This section covers strategies for migrating and modernizing applications on Google Cloud, including containerization and serverless options like Cloud Run and Cloud Functions.</li><li><strong>Trust and Security with Google Cloud:</strong> Cloud security can’t be an afterthought. This section explores Google’s robust security infrastructure and tools like Cloud Identity and Access Management (IAM) to ensure data protection and compliance.</li><li><strong>Scaling with Google Cloud Operations:</strong> Optimizing cloud usage involves effective cost management and operational excellence. You’ll learn about financial governance best practices and tools like Cloud Billing for cost control. Additionally, it covers Google Cloud’s commitment to sustainability and its eco-friendly cloud practices.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*_CN5Fcpd81lL2iET8IHlhw.png" /></figure><p><strong>Tips for the Exam</strong></p><p>The exam tests your ability to solve real-world problems using Google Cloud. Expect scenario-based questions where you’ll apply your knowledge to address business challenges. It is a comprehensive assessment with roughly 50 to 60 multiple-choice questions to be completed within 90 minutes. Effective time management is crucial as you have 1.5 minutes to answer each question. Consider <a href="https://docs.google.com/forms/d/e/1FAIpQLSedAmf77MGS7FGEaylFzY51KtBd7kkIZJIMDsV5zSRSmpKIOA/viewform">practicing the exam with the sample questions</a>.</p><p>You can choose to take the exam online or at a physical testing center depending on your location. Before you register, be sure to review the exam requirements and access additional study resources: <a href="https://cloud.google.com/learn/certification/cloud-digital-leader">https://cloud.google.com/learn/certification/cloud-digital-leader</a></p><p><strong>Continuous Learning</strong></p><p>The Google Cloud Digital Leader certification is a valuable credential for anyone seeking to demonstrate their cloud expertise and become a leader in digital transformation initiatives. With a focus on practical applications and the right preparation resources, you can confidently conquer the exam and showcase your cloud knowledge to potential employers or clients. Remember, this certification is a stepping stone, as you progress in your cloud journey, explore more specialized Google Cloud certifications to deepen your expertise in specific areas. The cloud landscape is constantly evolving, so continuous learning is key to staying ahead of the curve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c05c72604853" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Look at Firestore Multiple Databases]]></title>
            <link>https://medium.com/@azidin/first-look-at-firestore-multiple-databases-374a148dbb43?source=rss-840bcd912661------2</link>
            <guid isPermaLink="false">https://medium.com/p/374a148dbb43</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[firestore]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Azidin Shairi]]></dc:creator>
            <pubDate>Fri, 29 Sep 2023 19:55:55 GMT</pubDate>
            <atom:updated>2023-09-29T20:07:34.063Z</atom:updated>
            <content:encoded><![CDATA[<p>Firestore is a NoSQL document database in Google Cloud. Since the introduction Firestore only supported one database per project. Recently Google Cloud announced the support for multiple databases in a project. Now it is possible to create multiple databases for different applications, customers or environments. This new feature is currently in Public Preview and database management is only available via gcloud alpha CLI.</p><h4>Creating Firestore Database</h4><p>To create a named Firestore database you can use gcloud alpha CLI as follow:</p><pre>gcloud alpha firestore databases create --type=firestore-native \<br>--database=fsdb1 --location=eur3</pre><p>Both Firestore in native mode and Datastore mode can co-exist in the same project unlike before where you can either have Firestore or Datastore.</p><p>To create a named Datastore database you can specify the database type:</p><pre>gcloud alpha firestore databases create --type=datastore-mode \<br>--database=dsdb1 --location=eur3</pre><p>Also, previously Firestore and Datastore are linked to App Engine service, and therefore your database must be in the same region as App Engine. This new capability allows you to provision Firestore databases in any supported regions or multi-regions in the same project.</p><pre>gcloud alpha firestore databases create --type=datastore-mode \<br>--database=dsdb1 --location=europe-west4</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lvtH-gC5AE9w6hqs2T9lQ.png" /><figcaption>Firestore multiple databases in different modes and regions</figcaption></figure><h4>Deleting Firestore Database</h4><p>If you need to delete a database you can use the same gcloud alpha CLI with delete command:</p><pre>gcloud alpha firestore databases delete --database=fsdb1</pre><p>However if you have an existing Firestore or Datastore (default) database, you must empty all records before you can delete it.</p><p>If you want to prevent accidental deletion of a named database, you can enable protection with --delete-protection flag specified during creation of the database or by updating the existing one.</p><pre>gcloud alpha firestore databases update --database=fsdb1 --delete-protection</pre><h4>Managing Firestore Access Control</h4><p>Firestore access control is managed with IAM at the lowest on project level. There’s a separate data access control for clients application, and that is called Security Rules. Here we’re considering the case where we have multiple applications in the same project with separate service accounts where each application stores data in different Firestore databases.</p><p>At this point, there’s no option to manage Firestore permissions on the resource level and I hope this will change in the future. If you need granular control, the only option for now is using IAM conditions. You can specify the Firestore database name with resource.name and resource.type if you want to be explicit. Here’s an example of project level IAM policy with conditions:</p><pre>{<br>  &quot;members&quot;: [&quot;serviceAccount:&lt;service-account&gt;@&lt;project&gt;.iam.gserviceaccount.com&quot;],<br>  &quot;role&quot;: &quot;roles/roles/datastore.user&quot;,<br>  &quot;condition&quot;: {<br>    &quot;title&quot;: &quot;Firestore Database Conditional IAM&quot;,<br>    &quot;expression&quot;:<br>      &quot;resource.type == \&quot;firestore.googleapis.com/Database\&quot; &amp;&amp; <br>      resource.name == \&quot;projects/&lt;project&gt;/databases/&lt;db-name&gt;\&quot;&quot;<br>  }<br>}</pre><p>Support for Firestore multiple databases is an improvement on NoSQL service offering in Google Cloud. This eliminates the need to create multiple projects just for Firestore databases and if you have a small environment, this also reduces the complexity with cross-projects access control.</p><p>Links:</p><ul><li>Managing Firestore Databases: <a href="https://cloud.google.com/firestore/docs/manage-databases">https://cloud.google.com/firestore/docs/manage-databases</a></li><li>IAM Condition Resource Bases Access: <a href="https://cloud.google.com/iam/docs/configuring-resource-based-access">https://cloud.google.com/iam/docs/configuring-resource-based-access</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=374a148dbb43" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>