Skip to content
View thulasirajkomminar's full-sized avatar
:octocat:
#coding
:octocat:
#coding
9 followers · 3 following

Achievements

Achievement: Pair Extraordinairex3Achievement: YOLOAchievement: QuickdrawAchievement: Pull Sharkx4Achievement: Arctic Code Vault Contributor

Achievements

Achievement: Pair Extraordinairex3Achievement: YOLOAchievement: QuickdrawAchievement: Pull Sharkx4Achievement: Arctic Code Vault Contributor

Organizations

@schubergphilis

Block or report thulasirajkomminar

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
thulasirajkomminar/README.md

Hi there 👋, I'm Thulasiraj

About me

  • 🧑‍💻 Data Platform Engineer at Schuberg Philis
  • 💻 AWS Community Builder

⚡ Connect with me

Languages and Tools

My Skills

My Latest Blog Posts

From Zero to Fargate: Running Containerized Apps with Aurora on AWS From Zero to Fargate: Running Containerized Apps with Aurora on AWS
My team needed a simple on-call scheduler to manage who's on call, handle escalations, and send alerts without building something custom. After evaluating options we landed on GoAlert, an open-source on-call scheduling and alerting platform that does exactly what we needed, without the SaaS price tag.


Terraform AWS Provider v6: Redesigning API Gateway for Multi-Team Ownership Terraform AWS Provider v6: Redesigning API Gateway for Multi-Team Ownership
Initially when we first designed our AWS API Gateway setup, the goal was simple, one custom domain, one REST API, and a top-level path-based routing strategy to serve multiple teams. It worked. Teams were onboarded quickly, routing was predictable, and the Terraform was easy to understand. For a while, it was the right call.

Pinned Loading

  1. terraform-provider-influxdb3 terraform-provider-influxdb3 Public

    Terraform provider to manage InfluxDB V3

    Go

  2. terraform-aws-sagemaker-studio terraform-aws-sagemaker-studio Public

    Terraform module to create and manage a SageMaker studio

    HCL 5 2

  3. terraform-provider-influxdb terraform-provider-influxdb Public

    Terraform provider to manage InfluxDB

    Go 4 3

  4. schubergphilis/terraform-aws-mcaf-redshift schubergphilis/terraform-aws-mcaf-redshift Public

    Terraform module to setup and manage an AWS Redshift cluster.

    HCL 3