AWS Builder Center
My Assistant, My Chatbot, My AWS Devops Agent

My Assistant, My Chatbot, My AWS Devops Agent

In this article I am sharing my review of how I was able to analyse my AWS EKS Implementation errors with Chatbot created using AWS Devops Agent service.

Series: AWS Devops Agent (4 articles)

  1. …
  2. 4
    My Assistant, My Chatbot, My AWS Devops Agent This article
Hello ALL ...I have been exploring AWS Devops Agent Web Application Chatbot to assist me in Devops Activities as AWS Administrator and EKS Administrator.

Want to know how to create Chatbot assistant using AWS Devops Agent refer  AI Chatbot using AWS Devops Agent in 5 minutes | AWS Builder Center. 

Want to know more about features and applications of AWS Devops Agent refer  No-Code AWS Chatbot using Devops Agent | AWS Builder Center .

AWS Devops Agent can work with least privileges access and do not require root access, want to know more refer  No-Code AWS Chatbot using Devops Agent - 2 | AWS Builder Center. 

I am sharing some sneak peek into my investigations and resolutions using AWS Devops agent web application chatbot.
Investigation 1: 0/1 nodes are available: Too many pods
Problem Statement: I was trying to create a EKS cluster for my proof-of-concept testing. I used instance type t3.medium for EKS Master node. This is a configuration I have been using regularly, so I expect it to be created without any issues. However, I found many pods are pending this time.
Analysis: I analysed it with Chatbot created using Devops agent. I got suggestions to Scale Up the Node Group, Free Up Pods on the Existing Node, Enable VPC CNI Prefix Delegation, use a Larger Instance Type / Enable Prefix Delegation and Enable Cluster Autoscaler to Prevent Recurrence. I was exploring each choice through testing and found using larger Instance type suitable. The chatbot provided details pros and cons for each choice and also steps to attempt testing each option.
Investigation 2: Karpenter Node Provisioning Failure
Problem Statement: My Karpenter addon stopped working and it was not creating new worker nodes for my EKS cluster. I have added a new condition in Karpenter disruption policy.
Analysis: I prompted my chatbot created using Devops Agent, why karpneter was not creating any worker node. It analysed my environment and provided me detailed response with executive summary. It also rightly pointed the error condition to be removed to resolve my errors. Following the analysis, I was able to resolve my error in an hour.

Investigation 3: EBS Volume Migration Analysis: gp3 → sc1
Problem statement: As part of cost optimization, we were exploring migrating the EBS volumes from gp3 to sc1 types for the application we were testing.
Analysis: I analysed using AWS Devops Agent web application chatbot using prompt - can I migrate my EBS <name of volume> to sc1 type. The chatbot analysed and provided detailed response that this migration has High Rish and provided Architectural warning based on the nature of our application. It helped us stop the migration activity and mitigate the risk.


Series: AWS Devops Agent (4 articles)

  1. …
  2. 4
    My Assistant, My Chatbot, My AWS Devops Agent This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article