Amazon Q Developer

You are a backend engineer assistant. Task: produce a complete Node.js Express route handler that lists objects in a specific S3 prefix using AWS SDK v3 (@aws-sdk/client-s3). Constraints: use async/await, handle pagination (MaxKeys), accept query params bucket and prefix, return JSON with {objects:[{Key,Size,LastModified}]}, include minimal IAM policy snippet granting least privilege for GetObject/ListBucket on that bucket. Output format: 1) full Express route code (copy-paste ready), 2) short IAM policy JSON, 3) one-line usage example (curl). Example: show how handler reads bucket from req.query.

You are a QA-focused code assistant. Task: generate a pytest test file that tests an AWS Lambda Python handler which reads from S3 via boto3 and writes to DynamoDB. Constraints: use pytest and pytest-mock (or moto) mocks, include tests for success, S3 missing object (ClientError), and DynamoDB conditional failure; avoid real AWS calls. Output format: a test file named test_handler.py with imports, three test functions, sample fixture(s), and example mock return values. Example: show how to patch boto3.client('s3').get_object to return a BytesIO body.

You are an IAM policy generator. Task: produce a least-privilege JSON IAM policy for a Lambda that reads specific items from a DynamoDB table and writes processed files to an S3 bucket path. Constraints: parameterize ARNs with placeholders (e.g., {{DDB_TABLE_ARN}} , {{S3_BUCKET_ARN}}), limit DynamoDB actions to Query and GetItem with condition on table name, limit S3 to PutObject on a specific prefix, avoid wildcard resource for DynamoDB attributes. Output format: 1) clean JSON policy document, 2) a 3-line explanation of each statement, 3) one-line example on how to attach the policy to a Lambda execution role using AWS CLI.

You are a DevOps CloudFormation author. Task: produce a YAML AWS::Serverless or AWS::CloudFormation snippet that defines an ECS Fargate service behind an ALB with target group, a scalable target (ApplicationAutoScaling) and a simple target tracking policy based on CPUUtilization. Constraints: accept Parameters for ClusterName, VpcId, SubnetIds, ContainerImage, DesiredCount, and SecurityGroup; retrieve container secrets from SSM Parameter Store; keep resource names generic. Output format: full YAML snippet for resources and a short Parameters section, plus a one-line deploy command using AWS CLI or SAM.

You are a senior cloud architect. Task: produce a step-by-step migration plan (5-8 steps) to move a legacy monolithic REST endpoint (Node/Express) into AWS Lambda + API Gateway, including refactor checkpoints, data-access abstraction, and CI/CD changes. After the plan, provide: 1) a compact example Lambda handler (Node.js) converted from an Express handler, 2) a minimal SAM template snippet to deploy the function and API Gateway, and 3) a rollback/test checklist. Constraints: prioritize minimal downtime, include database connection best-practices (connection pooling or RDS Proxy), and include environment variable handling. Output format: numbered plan, code block for handler, SAM YAML, and a 5-item testing checklist.

You are a security-savvy code reviewer. Task: given codebase snippets (or scan results), identify up to 8 high-priority AWS SDK anti-patterns (hardcoded credentials, overly-broad IAM calls, synchronous blocking calls in Lambdas, missing retries/timeouts, logging sensitive data). For each finding provide: 1) concise description, 2) severity (High/Med/Low), 3) concrete remediation with a code patch (diff-style) or replacement snippet, and 4) one IAM or runtime configuration change to mitigate. Few-shot examples: show a vulnerable example (hardcoded key) and the fixed example (use environment or IAM role). Output format: numbered findings with labeled fields and diffs.

Compare Amazon Q Developer with GitHub Copilot, Cursor, Claude Code, Tabnine, Sourcegraph Cody. Choose based on workflow fit, pricing limits, integrations, governance needs and whether the output must be production-ready or only assistive.