DEV Community: Aman Pathak

How You Can Become an AWS Community Builder in 2026

Aman Pathak — Sat, 06 Dec 2025 07:17:40 +0000

Introduction

Hi everyone, my name is Aman. I create DevOps and cloud content to share my learning with the community. As we are heading toward 2026, many of us want to grow more, learn more, and share more. Today, I am not showing any demo or project. Instead, I want to talk about something people keep asking about. The AWS Community Builder Program.

I have been part of this program for the last three years. I learned a lot through it, and I want to share how you can also become an AWS Community Builder.

I have covered the same thing in my YouTube video. If you want, you can watch it here:

What the AWS Community Builder Program Is

This is an official AWS program created for people who actively learn and share knowledge on platforms like LinkedIn, Medium, YouTube, or anywhere you share your work. If you use AWS services in your projects and share your learnings publicly, AWS considers you a good fit.

The idea is simple. People who learn. People who share. People who contribute to the community.

What You Get When You Become a Community Builder

Here are the main benefits based on my experience.

AWS Credits

You receive 500 credits. I call it minimum because if you genuinely run out while building something, you can request more, and they will provide it after verifying your work.

One Free AWS Certification
Every year, you get one free certification voucher. This saves a lot because AWS certifications cost money, especially the speciality level ones.

Swags

Every year, AWS sends swag. I received a cap, bottle, bag, travel pouch, diaries and other small items. Nothing huge, but it feels good when you’re wearing the cap or using the bag.

Access to QA Learning Platform

You also get access to CloudAcademy or QA.com, where they have a lot of AWS learning content.

Networking

This personally helped me the most. You get a chance to connect with AWS experts and other builders. People who know more than you. People who share insights and correct you. You learn a lot from these conversations.

Who Can Apply

Anyone who is learning and sharing consistently. You do not have to be perfect or advanced. I was a beginner when I applied for the first time. Your consistency matters more than your depth.

Even basic projects, basic blogs, 30-day challenges or simple YouTube videos count. You just need to show that you are learning and sharing.

A Note About Using AI for Content

AWS prefers original work. If your content looks completely AI-generated, it may affect your selection. You can use help for small parts, but your main content should be written by you.

How to Apply

Right now, applications are not open. You can join the waitlist. When the window opens, AWS sends you the application link. Usually it happens between January and March.

Join the Waitlist

The form takes time. You will have to add your blogs, videos, GitHub work and explain what you did in the last year. Mention your best content. Mention your top-performing posts. Be honest about what you learned and built.

After applying, AWS takes around one to two months to evaluate.

Once selected, you stay in the program for one year. Every year, you need to renew. I have done it three times.

What AWS Looks For

AWS focuses on intent, consistency and genuine contribution. They are not looking for experts only. They want people who share their learning journey openly and help others.

Final Thoughts

I hope this gives you an understanding of the AWS Community Builder program. If you want, once the application window opens, I can guide you on what to write and how to prepare your form.

All the best for 2026. Keep learning and keep sharing. See you at the next one.

🚀 Enjoyed this content?
If you found it useful, don’t forget to 👏 clap, 🔄 share, and 💬 follow for more DevOps & Cloud insights.

💡 Want to discuss trending technologies in DevOps & Cloud?

👥 Join the community on Discord
🎥 I am on YouTube
🌐 Explore all my socials & blogs → Linktree
🤝 1:1 Mentorship
If you’re looking for personalised guidance in DevOps & Cloud (career growth, projects, real-world problem-solving), I’m opening limited slots for 1:1 mentorship. Please drop me a DM to know more.

👉 Keep experimenting. Keep learning. Keep growing!

How to Package and Publish Your Custom Helm Charts- A Hands-On Tutorial

Aman Pathak — Mon, 14 Oct 2024 10:42:15 +0000

Introduction

In this guide, we will explore how to package and publish multiple Helm charts in a single GitHub repository. We’ll deploy two distinct applications — a Go-based portfolio website and the classic Tetris game — on a Kubernetes cluster using Helm. By the end, you will have learned how to create, package, and publish Helm charts on GitHub and deploy them in a Kubernetes environment.

Objective

The objective of this tutorial is to help you understand:

How to create multiple Helm charts.
How to package and publish those charts on a GitHub repository.
How to install and run those applications on Kubernetes using Helm.

Pre-requisites

Before starting, ensure you have the following tools installed:

kubectl for interacting with Kubernetes clusters.
Helm for managing Kubernetes applications.
Minikube for local Kubernetes cluster setup (optional).
A public GitHub repository to publish your Helm charts.
Repository for this Hands-On Project- https://github.com/AmanPathak-DevOps/Helm-Charts/tree/master

Hands-On Guide 👐📘

Create a new GitHub repository

Note: It is required to keep your repository public to publish the helm charts

I am cloning the same repo on my EC2 machine. You can do the same on your local machine with the above-required tool installation.

We are going to create two different charts. So we can learn how to package multiple charts in one repo and publish them on Git Hub as well. The first chart has a portfolio website in Go Lang and the second chart is a game known as Tetris. You don’t need to follow the Kubernetes manifest file if you don’t want to.

To create a first helm chart, run the below command

helm create go-portfolio-app

We already have our own Manifest file content and values file. So, empty the templates folder and remove the values.yaml file

Now, create a deployment.yaml file and service.yaml file then copy the content from below.

namespace.yaml

apiVersion: v1
kind: Namespace
metadata: 
    name: go-app

deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: go-portfolio
  namespace: go-app
  labels:
    role: go-portfolio
    env: dev
spec:
  replicas: {{ .Values.replicaCount }}  # Use replica count from values.yaml
  selector:
    matchLabels:
      role: go-portfolio
  template:
    metadata:
      labels:
        role: go-portfolio
    spec:
      containers:
      - name: go-portfolio
        image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"  # Pull image and tag from values.yaml
        imagePullPolicy: {{ .Values.image.pullPolicy }}
        ports:
        - containerPort: 8080
        resources:
          requests:
            memory: "256Mi"
            cpu: "500m"
          limits:
            memory: "512Mi"
            cpu: "1"

service.yaml

apiVersion: v1
kind: Service
metadata: 
  name: go-portfolio-svc
  namespace: go-app
spec: 
  ports: 
  - port: 8080
    targetPort: 8080
  type: ClusterIP
  selector: 
    role: go-portfolio

values.yaml

replicaCount: 1

image:
  repository: avian19/go-port
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: "10201891038"

Hope you have added the above YAML code in your respective files.

Before going to package your helm chart, you can validate whether the helm chart is correct or not by deploying it.

helm install <chart-name> <chart-dir>

The Go App is running fine. So, don’t forget to uninstall it

helm uninstall <chart-name>

Now, we are ready to package our helm chart.

Go to the GitHub root directory and check the status

I am pushing my changes to the master branch(to keep track) which is not required in the process of packaging and publishing the helm chart.

To Package your Helm Chart and publish it, the gh-pages branch is required in our GitHub Repo. So, create a branch called gh-pages

git checkout -b gh-pages

Once, the branch gets created. We need to create a package of our go-portfolio-app.

To generate the package, you need to run the below command which will generate a file having tgz extension.

Note: The branch will be master as it contains the Chart.yaml file

helm package <chart-name(dir)>

So, we packaged our helm chart. Now, we are ready to publish it.

To publish, we need to create an index.yaml file that keeps track of all the packaged helm charts whenever you install them.

So, create an index.yaml file at the same place

touch index.yaml

As you can see, the index.yaml file did not have any content. But now, we need to generate the index file based on the charts present in our repository which is go-portfolio-app.

To generate the index.yaml file, run the below command

helm repo index <dir-where-tgz-file-located>

Now, Index.yaml is not empty as it holds the chart name go-portfolio-app

Finally, we need to push our gh-pages branch changes to GitHub.

As soon as you push your changes to the GitHub repo.

Go to the browser and check the GitHub repository, you will see there will a GitHub Actions workflow getting triggered in Orange color.

Once you click on it you will see the deployment gets completed. But where is it deployed?

To check the deployed place,

Go to the Settings of your GitHub repository and navigate to Pages where we are hosting our helm charts

As you can see in the below snippet, Your site is live at https://amanpathak-devops.github.io/Helm-Charts/. This will be our URL to deploy Helm charts on any Kubernetes Cluster.

Now, add the helm chart repo using the below command

helm repo add aman-devops https://amanpathak-devops.github.io/Helm-Charts/

Now, we are ready to install our helm chart through the helm install command

helm install go-app aman-devops/go-portfolio-app

You can run the below command to list the created Kubernetes resources through the helm chart

kubectl get all -n go-app

Run the below command to access your application

kubectl port-forward svc/tetris-service -n tetris 3000:3000

To access your application on the browser, you can hit the showing link in your browser

If you are using EC2 Server and want to access applications in your browser then, the kubectl port-forward command won’t be enough. To access your browser, run one more command on your local machine it is almost the same command as ssh does.

ssh -L 8080:localhost:8080 <ec2-user>@<public-ip> -i <Pem-file>

We have successfully packaged and published our first Helm chart. If you feel confident with this process, you can go ahead and exit this blog or document. I hope you found something new to learn. However, if you’re interested in learning how to create multiple charts within a single GitHub repository, I invite you to continue with me in this guide.

Let’s go ahead and create another chart, which should be quick if you already grasp the process!

So, I switched back to my master branch in my GitHub repository

git switch master

Create a new helm chart named tetris-game

helm create tetris-game

Empty the templates folder and remove the values.yaml file

Now, add your YAML files given below

namespace.yaml

apiVersion: v1
kind: Namespace
metadata: 
    name: tetris

deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: tetris
  namespace: tetris
spec:
  replicas: 3
  selector:
    matchLabels:
      app: tetris
  template:
    metadata:
      labels:
        app: tetris
    spec:
      containers:
      - name: tetris
        image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
        ports:
        - containerPort: 3000

service.yaml

apiVersion: v1
kind: Service
metadata:
  name: tetris-service
  namespace: tetris
spec:
  selector:
    app: tetris
  ports:
  - protocol: TCP
    port: 3000
    targetPort: 3000
  type: ClusterIP

values.yaml

replicaCount: 1

image:
  repository: avian19/tetrisv2
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: "1"

Before going to package your helm chart, you can validate whether the helm chart is correct or not by deploying it.

helm install <chart-name> <chart-dir>

The Tetris App is running fine. So, don’t forget to uninstall it

helm uninstall <chart-name>

Now, we are ready to package our helm chart.

Go to the GitHub root directory and check the status

I am pushing my changes to the master branch(to keep track) which is not required in the process of packaging and publishing the helm chart.

Package the Tetris application by running the below command on the master branch

helm package <chart-name(dir)>

Now, switch to gh-pages to package the helm chart and publish it

git switch gh-pages

As you can see in the below snippet, the index.yaml file has a go-app chart configuration. Now, we need to update the index file to have the Tetris app configuration.

Run the below command to update the index file for the Tetris app

helm repo index <dir-where-tgz-file-located>

Now, Index.yaml contains the configuration for chart tetris.

So we can push our gh-pages branch changes to GitHub.

As soon as you push your changes to the GitHub repo.

Go to the browser and check the GitHub repository, you will see there will a GitHub Actions workflow getting triggered in Orange color.

You can check the process of deployments by clicking on the Orange icon

You can also go to Actions to view the GitHub workflow

Now, when you are trying to install the Tetris app you might get errors as the old chart doesn’t have Tetris application configuration including index.yaml file.

Before installing the Tetris app, we need to update our helm chart

helm repo update

Now, we are ready to install our helm chart through the helm install command

helm install tetris aman-devops/tetris-game

You can run the below command to list the created Kubernetes resources through the helm chart

kubectl get all -n tetris

Run the below command to access your application

kubectl port-forward svc/tetris-service -n tetris 3000:3000

To access your application on the browser, you can hit the showing link in your browser

Enjoy the Game!

ssh -L 3000:localhost:3000 <ec2-user>@<public-ip> -i <Pem-file>

That’s it for today. I hope you learned something new today.

Conclusion

By the end of this guide, you successfully packaged, published, and deployed two different applications using Helm charts in a Kubernetes environment. You’ve also learned how to manage multiple charts within a single GitHub repository. With this foundation, you can now apply the same process to other applications or scale your deployment strategies further!

Support my work-
https://www.buymeacoffee.com/aman.pathak

Stay connected on LinkedIn: https://www.linkedin.com/in/aman-devops/

Stay up-to-date with GitHub: https://github.com/AmanPathak-DevOps

Want to discuss trending technologies in DevOps & Cloud
Join the Discord Server- https://discord.gg/jdzF8kTtw2

Feel free to reach out to me, if you have any other queries.

Happy Learning!