This repository demonstrates automated AI-powered code review (Amazon Q Developer) and security scanning (Amazon Inspector) triggered automatically during pull requests.
This demo is based on the real PR CarsonBytes/aws_code_review#5 which shows:
- Amazon Inspector bot scanning for security vulnerabilities
- Amazon Q Developer bot providing code review with security recommendations
- Both tools automatically commenting on PR changes
- Security issues blocking merge until remediated
When the PR was opened, both bots automatically reviewed the code:
Amazon Inspector Bot:
- Scanned CloudFormation template for security issues
- Found missing
AssumeRolePolicyDocumentproperty (High severity) - Left inline comments on vulnerable resources
Amazon Q Developer Bot:
- Performed comprehensive security review
- Found 3 critical issues:
- IAM role with
AdministratorAccess(violates least privilege) - Vulnerable
requestslibrary version 2.25.1 with known CVEs - Missing input validation in
order_logicfunction
- IAM role with
- Provided specific suggested fixes for each issue
- Blocked merge until issues are addressed
Developer creates PR
↓
GitHub Actions workflow activates
↓
┌────┴────┐
↓ ↓
Q Developer Amazon Inspector
Code Review Security Scan
↓ ↓
Results → PR Status
- Triggered: On PR creation/modification
- Purpose: AI-powered code quality and security review
- Checks: Code patterns, best practices, potential bugs, security vulnerabilities
- Location:
demo1_q_developer/- Simple order manager demonstrating code review - Features:
- Natural language code suggestions (
/qcommand) - CWE-linked security recommendations
- Suggested code fixes
- Natural language code suggestions (
- Triggered: Via GitHub Actions workflow on PR
- Purpose: Automated security vulnerability scanning
- Checks: Security issues in code and infrastructure
- Location:
demo2_pr_inspector/- Application + CloudFormation template with security issues - Features:
- Severity classification (Critical, High, Medium, Low)
- PR blocking on critical/high findings
- Detailed vulnerability reports
aws_demo2/
├── demo1_q_developer/ # Q Developer demo - code review example
│ ├── order_manager.py # Sample code for AI review
│ ├── test_order_manager.py # Tests
│ └── requirements.txt
│
├── demo2_pr_inspector/ # Inspector demo - security scan example
│ ├── order_logic.py # App with security vulnerabilities
│ ├── template.yaml # CloudFormation with security issues
│ ├── test_vulnerabilities.py # Vulnerability tests
│ └── requirements.txt
│
└── .github/workflows/
└── inspector-pr-scan.yml # GitHub Actions workflow
The workflow runs on every PR to main or master:
on:
pull_request:
branches: [main, master]- Checkout code - Gets PR code
- Configure AWS Credentials - Uses GitHub Secrets
- Run Amazon Inspector Scan - Scans repository for vulnerabilities
- Check Results - Blocks merge if Critical/High findings exist
- ✅ No critical/high vulnerabilities → PR can merge
- ❌ Critical or High vulnerabilities found → PR blocked
Simple Python application showing code patterns Q Developer reviews:
- Order management logic
- Mock database
- Payment gateway integration
- Intentional: Hardcoded API key for demonstration
Contains multiple vulnerability types for Inspector to detect:
Application (order_logic.py):
- Command injection
- Insecure pickle deserialization
- Hardcoded AWS credentials
- SQL injection
- Path traversal
- Weak MD5 encryption
Infrastructure (template.yaml):
- IAM role with AdministratorAccess
- Public S3 bucket
- Open security group (all traffic)
- KMS key with wildcard policy
- Lambda with excessive permissions
Real PR Review Comments (from #5)
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues.
✅ I finished the code review, and left comments with the issues I found.
## Security Review Summary
This PR introduces critical security vulnerabilities that must be addressed before merge:
### Critical Issues Found:
1. IAM Overprivileged Role: The CloudFormation template grants AdministratorAccess,
violating least privilege principles and creating significant security risks
2. Vulnerable Dependency: The requests library version 2.25.1 contains known CVEs
3. Missing Input Validation: The order_logic function lacks input validation
### Action Required:
Please address all security findings before this PR can be approved.
# Before (VULNERABLE)
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AdministratorAccess
# After (FIXED)
ManagedPolicyArns:
- arn:aws:iam::aws:policy/ReadOnlyAccess# Before (VULNERABLE)
def update_delivery_date(order_id, new_date):
return {"status": "updated", "new_date": new_date}
# After (FIXED)
def update_delivery_date(order_id, new_date):
if not order_id or not new_date:
raise ValueError("Invalid input parameters")
return {"status": "updated", "new_date": new_date}Add these to your repository settings:
| Secret | Description |
|---|---|
AWS_ACCESS_KEY_ID |
AWS access key |
AWS_SECRET_ACCESS_KEY |
AWS secret key |
AWS_REGION |
AWS region (default: us-east-1) |
# Install dependencies
cd demo2_pr_inspector
pip install -r requirements.txt
# Run vulnerability tests
python test_vulnerabilities.py- Q Developer provides AI-powered code review automatically on every PR
- Amazon Inspector scans for security vulnerabilities in PRs
- Automated blocking prevents insecure code from reaching production
- Natural language suggestions (
/qcommand) let developers fix issues quickly - CWE-linked recommendations provide context and remediation guidance
- Both tools work together for comprehensive security coverage