<?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 Aksharjoshi on Medium]]></title>
        <description><![CDATA[Stories by Aksharjoshi on Medium]]></description>
        <link>https://medium.com/@thetechnocommercialguy?source=rss-12c6f9af840b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vd1e9m0fpSkxSUIP</url>
            <title>Stories by Aksharjoshi on Medium</title>
            <link>https://medium.com/@thetechnocommercialguy?source=rss-12c6f9af840b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:49:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thetechnocommercialguy/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[How to sync data between Google Cloud Storage and Filestore?]]></title>
            <link>https://blog.searce.com/how-to-sync-data-between-google-cloud-storage-and-filestore-358719411a?source=rss-12c6f9af840b------2</link>
            <guid isPermaLink="false">https://medium.com/p/358719411a</guid>
            <category><![CDATA[google-cloud-storage]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[file-store]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Aksharjoshi]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 18:19:00 GMT</pubDate>
            <atom:updated>2023-10-04T04:36:40.051Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Key concepts: Google Cloud Storage, Filestore, Storage Transfer Service</em></p><ul><li>Google Cloud Storage- GCPs service for blob storage.</li><li>Filestore instances are fully managed file servers on Google Cloud that can be connected to multiple client types within the same network/VPC/IP range. In short, GCPs NFS service.</li><li>Storage Transfer Service (STS)- Quickly and securely transfer data to, from, and between cloud and on-premises storage systems.</li></ul><p><strong>Why was the concept of Network File System (NFS) introduced?</strong></p><p>The objective was to provide transparent, remote access to file systems on the same network via a client server</p><p><em>Pre-requisites</em>: GCP Account, GCP Project (Role: Owner), Basic understanding of cloud infrastructure</p><p><em>Gotchas- All resources being spun up should be in the same region and VPC</em></p><p>Steps: <em>(I won’t be getting into the machine configs/bucket types as they are subjective to your requirements)</em></p><ol><li>Create a Service Account with the following permissions</li></ol><p>Permissions: Owner, Project IAM Admin, Role Administrator, Pub/Sub Editor, Cloud Filestore Editor, Storage Object Admin, Storage Transfer Admin, Storage Transfer Agent</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NMYaO12HLtt6h5Ng" /></figure><p>2. Create a GCS bucket: Multi-regional, Standard class, Uniform Access Control</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MT1b5dbYKEfeHMBl" /></figure><p>3. Upload dummy files 🙂</p><p>4. Create a filestore instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnzPdCiJsNIWVPivoFqGJA.png" /></figure><p>5. Create a VM instance (Same Region, Same VPC)</p><p>I used e2-standard-32 for this POC purposes, to have a good performance</p><p>Attach the Service Account that was created to this VM</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ybX4-sDHSPn661-Y" /></figure><p>6. SSH into the instance (Each command will followed by its purpose)</p><p>Perform the following commands</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*O_5iVMWMPSJ4qCSU" /></figure><ul><li>Using a Vim editor to create a new file</li><li>copy the service account key data (which was stored locally)</li><li>Paste it to this new file and save it locally to this VM</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*lT9tmzsbCUe5qkZE" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*p4t_YGrhBRPpt3Qu" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*Ewm15_KrcqGQGFfR" /><figcaption>Install Docker</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*rx--COzZOfZlEytJ" /><figcaption>Authorize the Service Account to gcloud</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*kgKlb00lWZqq4ki0" /><figcaption>Install NFS</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*PW_GkAk_2MFYvJK0" /></figure><ul><li>Make a local directory to map to the Filestore file share</li><li>/usr/local/my_dir is the name of the local POSIX directory for the Compute Engine VM instance</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*oSgTmxMZL9hloGZF" /><figcaption>Mount the file share associated with the Filestore instance</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*r74oVkTDaGGBAr2p" /><figcaption>Confirm the mount point</figcaption></figure><p>7. Create a Storage Transfer Service Job</p><p>Source: GCS</p><p>Destination: POSIX filesystem</p><p>GCS Path</p><p>Create an agent pool</p><p>Authorize the Service Account for all STS features</p><p>Set a frequency for the Transfer Jobs (Hourly, Daily, Weekly)</p><p>8. Monitor/Track Transfer Status</p><p><strong><em>Important Links</em></strong>:</p><ul><li><a href="https://cloud.google.com/filestore/docs/overview">Filestore overview | Google Cloud</a></li><li><a href="https://cloud.google.com/storage-transfer/docs/on-prem-set-up#install_docker">Requirements for file system transfers | Cloud Storage Transfer Service Documentation | Google Cloud</a></li><li><a href="https://cloud.google.com/iam/docs/keys-create-delete#iam-service-account-keys-create-console">Create and delete service account keys | IAM Documentation | Google Cloud</a></li><li><a href="https://cloud.google.com/filestore/docs/transfer-data-from-gcs">Transfer large data sets from Cloud Storage to Filestore | Google Cloud</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z5MXj2ePfqxthQ6avEnkrw.png" /><figcaption>Commands</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=358719411a" width="1" height="1" alt=""><hr><p><a href="https://blog.searce.com/how-to-sync-data-between-google-cloud-storage-and-filestore-358719411a">How to sync data between Google Cloud Storage and Filestore?</a> was originally published in <a href="https://blog.searce.com/">Searce</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How connect to a CloudSQL instance with a Private IP?]]></title>
            <link>https://blog.searce.com/how-connect-to-a-cloudsql-instance-with-a-private-ip-572448779637?source=rss-12c6f9af840b------2</link>
            <guid isPermaLink="false">https://medium.com/p/572448779637</guid>
            <category><![CDATA[cloud-sql-proxy]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[private-ip]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-sql]]></category>
            <dc:creator><![CDATA[Aksharjoshi]]></dc:creator>
            <pubDate>Sun, 28 May 2023 16:45:40 GMT</pubDate>
            <atom:updated>2023-05-30T16:27:38.401Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>How to connect to a CloudSQL instance with a Private IP?</em></strong></h3><p>This question has come up on various of my customer calls, where connecting to a CloudSQL instance with private IP is a hassle, as there is no out of the box solution.</p><p>CloudSQL instance with public IP gives you the feature to whitelist the network addresses that need to interact with your instance, making it relatively easier. The idea here is to simplify the way to connect to a CloudSQL instance with private IP.</p><p>Benefits of having private IP enabled:</p><ul><li>Secure connection</li><li>Private connections make services reachable without going through the internet or using external IP addresses, and leverages Google’s networking infrastructure in the backend. For this reason, private IP provides lower network latency than public IP.</li></ul><p>Steps: <em>(I won’t be getting into the machine configs as they are subjective to your requirements)</em></p><ol><li>Spin up a SQL instance with your respective configurations (Postgres flavor)</li></ol><p>Check on private IP (Cloud SQL requires private services access for each VPC network that’s used for private IP connections; so do enable private service access)</p><p><em>Private services access is a private connection between your VPC network and a network owned by Google or a third party.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*8GlTvbZKdwT7v7qm-yFQuw.png" /><figcaption>CloudSQL creation interface</figcaption></figure><p>2. Spin up a GCE instance in the same VPC as the SQL instance</p><p>3. SSH into the instance</p><p>{Don’t forget to follow accessing a VM via OSLogin. If you only want some of your teams to access this VM, then create groups. Read this blog that I wrote previously on this) 🙂}</p><p>“<a href="https://medium.com/searce/restrict-manage-users-to-access-specific-vms-using-os-login-32ef1a847957">https://medium.com/searce/restrict-manage-users-to-access-specific-vms-using-os-login-32ef1a847957</a>”</p><p>Once you have SSH’s, ensure that you are in the Home directory</p><p>4. Install psql client on the VM via the SSH browser</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*zkFXWll3ddtfc5b8TvLMPw.png" /></figure><p>5. Install CloudSQL Auth Proxy on the same SSH browser</p><p><em>The Cloud SQL Auth Proxy is a utility for ensuring secure connections to your Cloud SQL instances. It provides IAM authorization, allowing you to control who can connect to your instance through IAM permissions, and TLS 1.3 encryption, without having to manage certificates.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*bMoFzjELa7E1UwTW3C4ocg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZA8YiRr1K5ealGVLk2lRQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*sDRr5kOe1-iRWvwl1NMHPw.png" /></figure><p>6. Run the CloudSQL Auth Proxy to monitor its operation and output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FtE0slrRTJTjtoijSTpzZg.png" /></figure><p>Instance Connection name can be found within a respective instance’s overview section</p><p>7. Open a separate SSH window within the same VM</p><p>8. Within this window, connect to your CloudSQL instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIyPXxMkkgRscKp2YzZ3EA.png" /></figure><p>Enter your password for your database and you are connected to your CloudSQL instance with private IP</p><p>9. Open the other SSH window that has CloudSQL Auth proxy running and you can monitor the established connection</p><p><strong><em>Note</em></strong>- This setup can also be achieved without the installation of CloudSQL Auth Proxy; thus I made sure to highlight its importance in point 5.</p><p><strong><em>Important links</em></strong>-</p><ul><li><a href="https://github.com/GoogleCloudPlatform/cloud-sql-proxy">GitHub - GoogleCloudPlatform/cloud-sql-proxy: A utility for connecting securely to your Cloud SQL instances</a></li><li><a href="https://cloud.google.com/sql/docs/postgres/connect-instance-private-ip">Quickstart: Connect to a Cloud SQL for PostgreSQL instance with private IP | Google Cloud</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*uspY_6Bicy07Hhhe2R42Ig.png" /><figcaption>Commands</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=572448779637" width="1" height="1" alt=""><hr><p><a href="https://blog.searce.com/how-connect-to-a-cloudsql-instance-with-a-private-ip-572448779637">How connect to a CloudSQL instance with a Private IP?</a> was originally published in <a href="https://blog.searce.com/">Searce</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Restrict/Manage users to access specific VMs using OS Login]]></title>
            <link>https://blog.searce.com/restrict-manage-users-to-access-specific-vms-using-os-login-32ef1a847957?source=rss-12c6f9af840b------2</link>
            <guid isPermaLink="false">https://medium.com/p/32ef1a847957</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[techcommunity]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[os-login]]></category>
            <dc:creator><![CDATA[Aksharjoshi]]></dc:creator>
            <pubDate>Wed, 15 Feb 2023 16:59:24 GMT</pubDate>
            <atom:updated>2023-02-16T05:00:50.435Z</atom:updated>
            <content:encoded><![CDATA[<p>How can a company restrict/manage users to access specific VMs using OS Login?</p><p><em>For example, there are database and application servers. Database users/teams should have access only to database servers, the application users/team should have access to only application servers, and devops team to have access to all these servers in the project.</em></p><p>There are two ways to access a VM, via SSH keys and via OS Login.</p><p>When accessing using SSH keys to log in, the user-specific SSH keys stored in VM metadata are read to enable access to the VM. Even if you remove a user from IAM to access a specific VM, the user will still be able to access the VM, unless you remove the specific SSH keys from metadata.</p><p>VM access via OS Login simplifies this process by mapping the Linux user in the VM to the user in Google Cloud IAM, instead of connecting to the SSH keys in metadata. Additionally, this mapping can be enabled at a VM level, project level, or organization level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*CFQezKo7ALHMUuLQuBQ4wg.png" /><figcaption><strong>Fig. a</strong>: OS Login at the VM level (Advanced Options &gt; Security)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*yhvNHag14ID8xiJxzz9fbA.png" /><figcaption><strong>Fig. b</strong>: OS Login at the project level (Compute Engine &gt; Settings &gt; Metadata)</figcaption></figure><p>Benefits of OS Login:</p><ul><li>It links your Google Cloud Account (either user or service account) to the Linux user</li><li>Ease of administration</li><li>Restricts the root access</li><li>The start-up time of a VM is faster compared to using SSH keys</li></ul><p>Let’s take an example here:<br>Akshar is a part of the application/dev team, and Karan is a part of the database team at Searce.</p><p>Akshar should only be able to have root access to application/dev VMs, and Karan should only be able to have root access to database VMs.</p><p>Steps to follow-</p><ol><li>Give Akshar a Compute Viewer and necessary Service Account User Role at a broader IAM level</li><li>Similarly, give Karan the same roles at a broader IAM level</li><li>Now go to Compute Engine &gt; VM Instances</li><li>Select the application/dev VM, and Select “Permissions”</li><li>Select “Add Principal”, and give Akshar “Compute OS Admin Login Role”</li><li>Follow steps 3 to 5, for the database VM and give Karan the same permissions</li></ol><p>Now, if Akshar tries accessing the database VMs, he will only be able to view it, and not SSH into it. The same goes for Karan accessing the application/dev VMs.</p><p><strong>Note</strong>- Ensure that neither Akshar/Karan has higher privileges (such as Editor/Owner)</p><p>To make this scalable, you can have “Groups” created for the database and application/dev teams. Follow these steps for groups instead of individual users.</p><p>Important links:</p><ol><li><a href="https://cloud.google.com/compute/docs/oslogin">https://cloud.google.com/compute/docs/oslogin</a></li><li><a href="https://cloud.google.com/compute/docs/oslogin/set-up-oslogin">https://cloud.google.com/compute/docs/oslogin/set-up-oslogin</a></li><li><a href="https://cloud.google.com/iam/docs/groups-in-cloud-console">https://cloud.google.com/iam/docs/groups-in-cloud-console</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32ef1a847957" width="1" height="1" alt=""><hr><p><a href="https://blog.searce.com/restrict-manage-users-to-access-specific-vms-using-os-login-32ef1a847957">Restrict/Manage users to access specific VMs using OS Login</a> was originally published in <a href="https://blog.searce.com/">Searce</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>