Skip to content

Amazon q agentapi integration #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Amazon q agentapi integration #242

wants to merge 6 commits into from

Conversation

Sahelisaha04
Copy link

Summary

This PR adds Amazon Q module support with Coder Tasks + AgentAPI integration as a web chat interface (closes #240).

Changes

  • Created new Amazon Q module in saheli namespace following the Goose module architecture
  • Integrated AgentAPI for web chat interface support
  • Added AWS credential support via environment variables
  • Implemented support for both Amazon Q and Aider modes
  • Added comprehensive test coverage

Module Features

  • Web Interface: Amazon Q accessible through AgentAPI web chat on port 3284
  • CLI Interface: Terminal-based Amazon Q/Aider access
  • Task Reporting: MCP protocol integration for task status reporting to Coder dashboard
  • AWS Authentication: Support for AWS credentials via environment variables or IAM roles
  • Flexible Configuration: Toggle between Amazon Q and Aider with use_aider parameter

Testing

  • All module tests pass successfully
  • Terraform validation passes (terraform init and terraform plan)
  • Demo template tested and working
Screencast.from.2025-07-18.13-57-34.mp4

@Sahelisaha04
feat(saheli): add Amazon Q module with AgentAPI integration
a1318b1 
- Follow Goose module architecture patterns exactly
- Add AgentAPI integration for web chat interface
- Add AWS credentials support (access key, secret key, region, profile)
- Add script-based installation and startup (scripts/install.sh, scripts/start.sh)
- Add support for both Amazon Q and Aider modes
- Add enhanced logging and error handling
- Add proper task reporting via MCP integration
- Add environment variable configuration for authentication
- Terraform init and plan validated successfully

Addresses GitHub issue coder#240 for Amazon Q + AgentAPI + Coder Tasks integration
@Sahelisaha04
docs(saheli): add example usage for Amazon Q module
82ef94e 
- Add example.tf showing how to use the module
- Include AWS credentials configuration
- Show task reporting and prompt configuration
- Include Docker container example
@Sahelisaha04
chore: remove example usage file for Amazon Q module
cd82233
@Sahelisaha04
test: enhance tests for coder_script and coder_app resources in amazo…
fb58b9e 
…n-q module
@Sahelisaha04
feat: add Amazon Q module with comprehensive README and test cases
e77d0e3
@bpmct
Copy link
Member

bpmct commented Jul 19, 2025

Hey @Sahelisaha04 - can you get this working in a similar way as https://registry.coder.com/templates/coder-labs/tasks-docker

@Sahelisaha04 Sahelisaha04 reopened this Jul 22, 2025
@Sahelisaha04
Copy link
Author

Screencast.from.2025-07-22.21-04-08.mp4

@bpmct is it okay now ?

@bpmct
Copy link
Member

bpmct commented Jul 22, 2025

Can you show the tasks UI. Also the "Amazon Q Web" app didn't appear healthy from your demo

@DevelopmentCats
Copy link
Contributor

Should we be doing this in a seperate namespace since the coder/amazon-q module exists already?

@keirans
Copy link

keirans commented Jul 23, 2025 •
edited
Loading

Hey Everyone,
We are another user of this module, so I wanted to weigh in on this PR as we have been watching it's development closely.

AWS Authentication Method
This proposed change affects the authentication method from the tar bundle to AWS Credentials, and would break our use of the module as well, and this change will not allow Non-Pro users of Amazon Q to use it in a fully automated manner for Agentic actions. Can I ask that this PR introduces some logic to select an authentication method so that you can use one or the other. It will also allow future configuration to support assuming external roles, etc

Variable Names
Can we look to transition away from the experimental prefixes on all variable names as this module is maturing ?
We can call out some of the functionality being experimental or being refined in the documentation.

Q Shell Script / MCP Ordering
We have opened a PR overnight to address some ordering issues in the 1.x release that prevent additional MCP servers from being introduced, We ask that these changes are factored into this PR to ensure this functionality is enhanced. As a suggestion, we'd like to see this PR merged before this 2.x bump for compatibility purposes as it will give us some time to test out the 2.x version.

Namspacing in the Repo
I agree with @DevelopmentCats - This should be an enhancement to the existing codebase rather than an introducing a fork of the current module.

Thanks again for your contributions on this module, I've been watching this prior to this Issue being submitted and PR opened as it was an area of focus for us as well. Happy to test it as part of the review process when it is ready for merge, I'll likely do a bit more of a review of the approach to this over the next few days as there is quite a bit to unpack :)

K

@matifali
Copy link
Member

This is great feedback @keirans. @Sahelisaha04 can you address the feedback provided? Thanks

@Sahelisaha04
Copy link
Author

Sahelisaha04 commented Jul 23, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Amazon Q Module: Tasks + AgentAPI Support
5 participants
@Sahelisaha04 @bpmct @DevelopmentCats @keirans @matifali