---
title: "Glenn Gray (@tallgray) | Hashnode"
description: "Infrastructure Architect · AWS · Kubernetes · Terraform. Read the latest articles by Glenn Gray on Hashnode."
url: "https://hashnode.com/@tallgray"
---

@tallgray

# Glenn Gray

@tallgray · Denver, CO · Joined March 2026

Infrastructure Architect · AWS · Kubernetes · Terraform

[Website](https://graycloudarch.com/)

### [Stop Manually Updating Jira After Every PR Merge](https://tallgray.hashnode.dev/stop-manually-updating-jira-after-every-pr-merge-1?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. You just merged a PR. Now you open Jira, find the ticket, paste the PR link in a comment, transition the status to Done, and update the deployed field. Five minutes. Twenty times a week. That's 1,700 minute...

6 min read · [tallgray.hashnode.dev](https://tallgray.hashnode.dev/stop-manually-updating-jira-after-every-pr-merge-1?utm_source=hashnode&utm_medium=feed)

[May 5](https://hashnode.com/posts/stop-manually-updating-jira-after-every-pr-merge-1/69f9e336a54cd251b367e150)

### [What the first 24 hours of production CloudWatch data told us](https://tallgray.hashnode.dev/what-the-first-24-hours-of-production-cloudwatch-data-told-us?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. The morning after go-live, the first thing I looked at was CPU. One of the two delivery services was sitting at 99.8% average utilization across 9 tasks. P50 latency: 1,010ms. We'd launched deliberately wit...

7 min read · [tallgray.hashnode.dev](https://tallgray.hashnode.dev/what-the-first-24-hours-of-production-cloudwatch-data-told-us?utm_source=hashnode&utm_medium=feed)

[May 4](https://hashnode.com/posts/what-the-first-24-hours-of-production-cloudwatch-data-told-us/69f8e8d7f6d79aef973bdbbd)

### [Building Automated AWS Permission Testing Infrastructure for CI/CD](https://tallgray.hashnode.dev/building-automated-aws-permission-testing-infrastructure-for-cicd-1?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. I deployed a permission set for our data engineers five times before it worked correctly. The first deployment: S3 reads worked, Glue Data Catalog reads worked. Athena queries failed — the query engine need...

7 min read · [tallgray.hashnode.dev](https://tallgray.hashnode.dev/building-automated-aws-permission-testing-infrastructure-for-cicd-1?utm_source=hashnode&utm_medium=feed)

[Apr 5](https://hashnode.com/posts/building-automated-aws-permission-testing-infrastructure-for-cicd-1/69d2939ae72c816fdf49bd5a)

### [Stop Managing EKS Add-ons by Hand](https://tallgray.hashnode.dev/stop-managing-eks-add-ons-by-hand-1?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. I was preparing to upgrade a production EKS cluster to version 1.32 when I discovered a problem. Four of our core cluster components—VPC CNI, CoreDNS, kube-proxy, and Metrics Server—were all running version...

5 min read · [tallgray.hashnode.dev](https://tallgray.hashnode.dev/stop-managing-eks-add-ons-by-hand-1?utm_source=hashnode&utm_medium=feed)

[Apr 5](https://hashnode.com/posts/stop-managing-eks-add-ons-by-hand-1/69d293967b9dd37d867911cc)

### [Building Apache Iceberg Lakehouse Storage with S3 Table Buckets](https://tallgray.hashnode.dev/building-apache-iceberg-lakehouse-storage-with-s3-table-buckets-1?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. The data platform team had a deadline and a storage decision to make. They'd committed to Apache Iceberg as the table format — open standard, time travel, schema evolution, the usual reasons. What they hadn...

7 min read · [tallgray.hashnode.dev](https://tallgray.hashnode.dev/building-apache-iceberg-lakehouse-storage-with-s3-table-buckets-1?utm_source=hashnode&utm_medium=feed)

[Apr 4](https://hashnode.com/posts/building-apache-iceberg-lakehouse-storage-with-s3-table-buckets-1/69d1911a1507412e985db891)
