AWS Builder Center
No-Code AWS Chatbot using Devops Agent - 2

No-Code AWS Chatbot using Devops Agent - 2

This article explores if Chatbot using AWS Devops Agent works with least privilege access.

Series: AWS Devops Agent (4 articles)

  1. …
  2. 3
    No-Code AWS Chatbot using Devops Agent - 2 This article
We have previously explored on Agent space creation for Chatbot and basic functional testing with some useful prompts for AWS EKS in article  https://builder.aws.com/content/3HYCBSztz2djMsAOQlPnwABBJb8/ai-chatbot-using-aws-devops-agent-in-5-minutes 
We have also explored on how devops Agent provides low code no code Chatbot as a web application and its features in article  https://builder.aws.com/content/3HpBdNchqHDqA9VwRFr8B0PBHZP/no-code-aws-chatbot-using-devops-agent 
In this article sharing my experience with applications of AWS Devops Agent as a No-Code Chabot web application from Access Policies perspective.
I was getting queries from many members if this chatbot requires AWS root account access. So, I thought I will share a short article based on my personal testing experiences.
I created the Agent space n Devops Agent using my Admin Access user Account. However, for accessing chatbot the AWS User must have access to AIDevOpsAgent only and access policies based on their role to perform investigation. I created an IAM user with only below policies (AWS managed) to investigate my AWS resources using the chatbot.
✔️ AIDevOpsAgentAccessPolicy - Permissions to Access AWS services for investigation in read-only mode.
✔️ AIDevOpsAgentFullAccess - Permission to access and update Devops Agent features
✔️ AIDevOpsAgentReadOnlyAccess - permissions to only view Devops Agent features
✳️ Chat response is intersection of User Access and Chatbot Agent Access.

Some features of the Devops Agent Access Policies:
✅ Agent requires Read-only Access to AWS services.
✅ AWS Users can be provided with only least privilege access for Chabot web application.
✅ This Chatbot or its AWS Users do not require root access for investigations. Only least privilege access is required.
✅ It does investigation of our AWS account based on IAM role we have provided and provides us with response specific to our AWS environment.

Series: AWS Devops Agent (4 articles)

  1. …
  2. 3
    No-Code AWS Chatbot using Devops Agent - 2 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