Skip to content

feat(gcp-to-aws): add Elastic Beanstalk as migration target for App E…#101

Open
azpaulp wants to merge 4 commits into
awslabs:mainfrom
azpaulp:feat/elastic-beanstalk-gcp
Open

feat(gcp-to-aws): add Elastic Beanstalk as migration target for App E…#101
azpaulp wants to merge 4 commits into
awslabs:mainfrom
azpaulp:feat/elastic-beanstalk-gcp

Conversation

@azpaulp

@azpaulp azpaulp commented Jul 1, 2026

Copy link
Copy Markdown

…ngine workloads

Problem

Add AWS Elastic Beanstalk as a PaaS-to-PaaS mapping for Google App Engine resources. App Engine Standard/Flexible now maps to EB by default, with user override to Fargate or Lambda via a new Clarify question (Q7b).

Solution

  • App Engine → EB is a conditional fast-path (deterministic when compute_model is absent or "managed_platform")
  • Cloud Run remains unconditionally mapped to Fargate (unaffected)
  • Q7b only fires when App Engine is in inventory
  • EB design reference provides platform detection, configuration, deployment policies, and App Engine feature mapping
  • google_app_engine_standard/flexible_app_version added to Skip Mappings

Also fixes pre-existing inaccuracies in compute.md examples where Cloud Run and Cloud Functions were incorrectly shown as rubric-evaluated (they're deterministic fast-path mappings).

Type of Change

  • New plugin/power/tool
  • Bug fix

Team Folder

  • advisor/
  • migrate/
  • Other: ___

Checklist

  • I have read the CONTRIBUTING.md guidelines
  • My changes do not include hardcoded secrets, credentials, or internal-only content
  • I have run mise run build locally and it passes
  • I have updated documentation if needed
  • My changes are scoped to my team's folder only

azpaulp added 2 commits July 1, 2026 13:29
…ngine workloads

Add AWS Elastic Beanstalk as a PaaS-to-PaaS mapping for Google App Engine
resources. App Engine Standard/Flexible now maps to EB by default, with
user override to Fargate or Lambda via a new Clarify question (Q7b).

Key decisions:
- App Engine → EB is a conditional fast-path (deterministic when
  compute_model is absent or "managed_platform")
- Cloud Run remains unconditionally mapped to Fargate (unaffected)
- Q7b only fires when App Engine is in inventory
- EB design reference provides platform detection, configuration,
  deployment policies, and App Engine feature mapping
- google_app_engine_standard/flexible_app_version added to Skip Mappings

Also fixes pre-existing inaccuracies in compute.md examples where Cloud
Run and Cloud Functions were incorrectly shown as rubric-evaluated
(they're deterministic fast-path mappings).
Fix pre-existing inaccuracies where Cloud Run and Cloud Functions
examples showed rubric-based evaluation (inferred) when they actually
use deterministic fast-path mappings. Replace the single Output Schema
with two examples showing both deterministic and inferred patterns.

Also add compute_model to the User Preference criterion description
in design-infra.md.
@azpaulp azpaulp requested a review from a team as a code owner July 1, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant