Upgrade an AWS Glue ETL job from Glue version 0.9 or 1.0 to Glue 4.0. Runs the job against Glue 4.0, diagnoses failures against a known breaking-change catalogue, patches the job script and configuration, and iterates until the job succeeds or the fix attempt limit is exhausted. Jobs using the AWS Encryption SDK…
Migrate a legacy AWS Glue development endpoint to a Glue interactive session, following the official AWS migration checklist. Inventories the dev endpoint config, maps it to an equivalent interactive session (runtime role, Glue version, workers, VPC connection, idle timeout), provisions the session, validates by…
Migrate an AWS Glue for Ray job (Command.Name glueray, Runtime Ray2.4) to a Ray job on Amazon EKS with KubeRay, at the same Ray and Python versions (Ray 2.4.0 / Python 3.9) with equivalent functionality. Use when a customer must move Glue for Ray workloads to Ray on EKS before Glue for Ray end of life. Do NOT use for…
Manages AWS Glue auto version (GlueVersion = "auto") for existing Spark ETL jobs. Setup: assesses each job's auto version eligibility and reports eligible jobs, blocking reasons and effort; enables auto version for the eligible jobs the user confirms; sets up encrypted email notifications. Consent: finds jobs whose…
Transform OpenAPI specifications (Swagger 2.0, OpenAPI 3.0, 3.1) into Amazon API Gateway-compatible REST APIs. Orchestrates transform, validate, optionally deploy via AWS SAM, E2E test against live endpoints, and report unsupported features. Use when converting OpenAPI to API Gateway, importing a Swagger/OpenAPI spec…
Perform a full AWS Well-Architected Framework review of the user's workload by analyzing code, IaC, and configurations to produce evidence-backed findings with prioritized remediation.
Assess a workload's readiness to migrate to AWS by analyzing existing code, dependencies, configurations, and infrastructure to produce evidence-backed findings covering the 7 Rs, risks, and a migration plan.
"Learn then Build" — help the user understand AWS Well-Architected best practices for their specific workload, then produce actionable visual artifacts (architecture diagrams with WA annotations, decision trees, improvement roadmaps) they can commit and use.
Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) — so a workload stays aligned with Well-Architected best practices over time instead of being assessed once.
Perform a full AWS Well-Architected Framework review evaluating all 57 questions across 6 pillars by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: