Repository navigation
Implement quadrant-based architecture with unified workers for ChatOps Lambda and SQS - #14
Conversation
Co-authored-by: llama90 <6668548+llama90@users.noreply.github.com>
Co-authored-by: llama90 <6668548+llama90@users.noreply.github.com>
Co-authored-by: llama90 <6668548+llama90@users.noreply.github.com>
|
@copilot Why are you upating naming for sqs and labmda for audrant-based command. |
I didn't change any resource names. The Lambda function names and SQS queue names remain unchanged:
The "quadrant-based" approach only changes the configurations (timeout, concurrency, memory, IAM permissions, tags) to optimize each worker based on command characteristics, not the resource names themselves. |
|
@copilot Why? I want to change the resource names too. |
What naming scheme would you like for the resources? For example:
Please specify the desired naming pattern for Lambda functions and SQS queues. |
- feat: add Lambda and SQS for short-read commands - chore: auto-format terragrunt HCL files --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
- feat: add Lambda and SQS for long-write commands - chore: auto-format terragrunt HCL files - chore: remove SQS queue-level delay and rely on Lambda concurrency for rate limiting --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
Update resource naming to align with directory structure:
- SR queue: sr-queue → chatbot-command-sr-queue
- SR worker: sr-worker → chatbot-command-sr-worker
- LW queue: lw-queue → chatbot-command-lw-queue (already correct)
- LW worker: lw-worker → chatbot-command-lw-worker
This provides better consistency between directory names and actual
AWS resource names, making infrastructure easier to navigate and understand.
Changes:
- Updated queue_name and function_name in locals
- Updated Component tag to match directory naming pattern
- Added clarifying comment for queue naming convention
Resource naming pattern:
{org}-{env}-chatbot-command-{quadrant}-{type}
Example: laco-plt-chatbot-command-sr-sqs
🔍 Terragrunt Check Results📊 Summary✅ All checks passed!
🔒 Trivy Security Details (0 issue(s))💡 Note: Terragrunt plan is disabled. To enable, configure AWS OIDC credentials in the workflow. 👤 Pusher: @llama90 | 🔄 Action: |
|
@copilot Is title and description for Pull Request right? |
The PR title is accurate, but the description is outdated. The actual implementation uses: Unified Workers per Quadrant (not individual workers):
Queue names:
The description should be updated to reflect that this creates unified workers per quadrant category (SR/LW) rather than separate workers for each command (echo/build). The resource names also changed from |
ChatOps platform currently uses identical configurations for all Lambda workers and SQS queues regardless of command characteristics, causing security issues (over-permissioned read workers), performance issues (slow reads), and resource inefficiency. This implements quadrant-based optimization using execution time (short/long) and side effects (read/write) as classification axes, with unified workers per quadrant category.
Related PR
Architecture
Unified Workers per Quadrant (replaces individual command workers):
Short-Read (SR) Worker
Resource:
chatbot-command-sr-worker/echo,/status, and future short-read commandsCommandCategory=short-read,SLOTarget=p99-500msLong-Write (LW) Worker
Resource:
chatbot-command-lw-worker/build,/deploy, and future long-write commandsCommandCategory=long-write,SLOTarget=p95-10minSQS Queues
SR Queue (
chatbot-command-sr-queue):LW Queue (
chatbot-command-lw-queue):EventBridge Routing
Routes individual commands to appropriate quadrant queues:
/echo,/build→ command-specific rulesRouter
Added
COMMAND_CATEGORIESenvironment variable:Impact
Documentation
QUADRANT-ARCHITECTURE.mdwith classification matrix, security rationale, cost analysisSLACK-BOT-ARCHITECTURE.mdwith quadrant mappingstest-quadrant-permissions.shintegration testMigration Notes
Resource names changed:
chatbot-echo-worker→chatbot-command-sr-workerchatbot-build-worker→chatbot-command-lw-workerchatbot-echo-sqs→chatbot-command-sr-sqschatbot-build-sqs→chatbot-command-lw-sqsAll changes are backward compatible at the API level. No application code changes required.
This pull request was created from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.