migration-to-aws: flat-steering port with scripts shipped directly - #182
Open
ayn-builds wants to merge 1 commit into
Open
migration-to-aws: flat-steering port with scripts shipped directly#182ayn-builds wants to merge 1 commit into
ayn-builds wants to merge 1 commit into
Conversation
Reworks the flattening of the upstream awslabs plugin (awslabs/startups/migrate/plugins/migration-to-aws, Apache-2.0) so the plugin's deterministic scripts ship as real executables rather than being de-scripted into prose. - Ships 11 PEP 723 .py scripts flat in steering/, run via `uv run steering/<name>.py` (agent-advisor scoring/build-diagram, the llm validators, the tf policy checker). No servers/ MCP dir. - Adds the agent-advisor and llm-to-bedrock engines alongside gcp-to-aws and heroku-to-aws, plus shared tf-best-practices. - POWER.md defines $STEERING/$SCRIPTS/$HELPERS/<scriptsDir>/$GCP_BASE to resolve to the one flat directory, so the plugin's injected "Scripts directory" line is no longer load-bearing. - INTERPRETER.md _exec dispatches to Kiro's generic general-task-execution sub-agent, preserving context isolation without a power-level agent registry. - Generated by tooling/flatten_plugin_to_power.py, so a re-sync is a re-run rather than a manual merge.
nadetastic
reviewed
Aug 13, 2026
| description: "Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP." | ||
| keywords: ["gcp", "aws", "migration", "cloud migration", "terraform", "re-platform", "cost estimation", "architecture", "bedrock", "openai", "gemini", "anthropic"] | ||
| displayName: "Migrate to AWS" | ||
| description: "Migrate workloads to AWS from Google Cloud Platform or Heroku, migrate AI/LLM code to Amazon Bedrock, and decide how to run AI agents on AWS. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, migrate Vertex AI to SageMaker, migrate Cloud Spanner to Aurora, migrate Firestore to DynamoDB, migrate Pub/Sub to SNS or SQS, migrate BigQuery off Google Cloud, Google Cloud migration, migrate from Heroku, Heroku to AWS, move off Heroku, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, leave Heroku, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate from Anthropic API to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate CrewAI or AutoGen agents to AWS, migrate my AI app to AWS, which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, move my agents to AWS, agent migration plan, add AgentCore services, add memory or gateway or identity to my agent, migrate Temporal workers to AWS, Temporal to AWS, Temporal Cloud to AWS, what-if workshop, reprice migration scenarios, compare GCP and AWS pricing. Routes to one of four migration engines and runs a phased process with fail-closed handoff gates: discover the source workload, clarify requirements, design the AWS target, estimate cost, and generate migration artifacts (Terraform, scripts, adapters, documentation, and reports). Cost estimates use a cached pricing table as the primary source with the AWS Pricing MCP server as a secondary lookup. AI model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP or AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, same-cloud refactoring, or multi-cloud deployments that do not involve migrating onto AWS." |
Member
There was a problem hiding this comment.
Recommend reducing the length of description, for example is the sentence needed here?
Cost estimates use a cached pricing table as the primary source with the AWS Pricing MCP server as a secondary lookup.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reworks the
migration-to-awsflattening of the upstream awslabs plugin (awslabs/startups/migrate/plugins/migration-to-aws, Apache-2.0) so the plugin's deterministic scripts ship as real executables rather than de-scripted prose..pyscripts flat insteering/, invoked asuv run steering/<name>.py(agent-advisor scoring/build-diagram, the llm validators, the tf policy checker). Noservers/dir.$STEERING/$SCRIPTS/$HELPERS/<scriptsDir>/$GCP_BASEin POWER.md so they resolve to the one flat directory, and the plugin's injected "Scripts directory" line is no longer load-bearingINTERPRETER.md_execdispatches to Kiro's genericgeneral-task-executionsub-agent, so context isolation survives the loss of a power-level agent registrytooling/flatten_plugin_to_power.py, so re-syncing is a re-run rather than a manual mergeAdditive over the current power: all 67 existing
migration-to-aws/files are retained, nothing is deleted, and no other power is touched.