Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-cloud-migrate

azure-cloud-migrate

Verified

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

FileKindSize
SKILL.mdskill md4.3 KB
references/services/app-service/app-engine-to-app-service.mdmarkdown7.1 KB
references/services/app-service/assessment.mdmarkdown5.2 KB
references/services/app-service/beanstalk-to-app-service.mdmarkdown6.4 KB
references/services/app-service/code-migration.mdmarkdown5.0 KB
references/services/app-service/global-rules.mdmarkdown2.8 KB
references/services/app-service/heroku-to-app-service.mdmarkdown7.5 KB
references/services/container-apps/assessment-guide.mdmarkdown7.0 KB
references/services/container-apps/cloudrun-assessment-guide.mdmarkdown2.5 KB
references/services/container-apps/cloudrun-deployment-guide.mdmarkdown7.9 KB
references/services/container-apps/cloudrun-to-container-apps.mdmarkdown2.2 KB
references/services/container-apps/deployment-guide.mdmarkdown9.6 KB
references/services/container-apps/fargate-assessment-guide.mdmarkdown2.4 KB
references/services/container-apps/fargate-deployment-guide.mdmarkdown10.1 KB
references/services/container-apps/fargate-to-container-apps.mdmarkdown4.0 KB
references/services/container-apps/k8s-to-container-apps.mdmarkdown4.9 KB
references/services/container-apps/spring-apps-to-aca.mdmarkdown3.8 KB
references/services/container-apps/spring-assessment-guide.mdmarkdown5.2 KB
references/services/container-apps/spring-dependency-patterns.mdmarkdown1.2 KB
references/services/container-apps/spring-deployment-guide.mdmarkdown15.1 KB
references/services/functions/assessment.mdmarkdown6.3 KB
references/services/functions/code-migration.mdmarkdown6.0 KB
references/services/functions/global-rules.mdmarkdown3.3 KB
references/services/functions/lambda-to-functions.mdmarkdown10.2 KB
references/services/functions/runtimes/csharp.mdmarkdown5.5 KB
references/services/functions/runtimes/java.mdmarkdown6.4 KB
references/services/functions/runtimes/javascript.mdmarkdown8.5 KB
references/services/functions/runtimes/powershell.mdmarkdown5.0 KB
references/services/functions/runtimes/python.mdmarkdown6.4 KB
references/services/functions/runtimes/typescript.mdmarkdown3.5 KB
references/workflow-details.mdmarkdown2.3 KB

references/services/container-apps/spring-apps-to-aca.md

View on GitHub
# Spring Boot to Azure Container Apps Migration

> Migrate Spring Boot applications from Azure Spring Apps, VMs, or other platforms to Azure Container Apps with containerization, deployment, and Spring Cloud integration.

## Overview

This migration enables you to move existing Spring Boot applications from Azure Spring Apps (or any platform) to Azure Container Apps with minimal code changes.

## Migration Scenarios

| Source Platform | Target Platform | Migration Path |
|----------------|-----------------|----------------|
| Azure Spring Apps | Azure Container Apps | Assess → Containerize → Deploy → Spring Cloud components |
| Spring Boot on VMs | Azure Container Apps | Assess → Containerize → Deploy |
| Spring Boot (other cloud) | Azure Container Apps | Assess → Containerize → Deploy |

## Service Mapping

| Spring Apps Feature | Container Apps Equivalent |
|-------------------|---------------------------|
| App Deployment | Container App |
| Service Registry (Eureka) | Managed Eureka for Spring (`eureka-server-for-spring`); alt: Dapr service invocation + internal DNS |
| Config Server | Managed Config Server for Spring (`config-server-for-spring`); alt: Azure App Configuration + Key Vault |
| Spring Cloud Gateway | Managed Gateway for Spring; alt: Azure API Management / Container Apps ingress |
| Distributed Tracing | Application Insights |
| Log Streaming | Log Analytics Workspace |

## Pre-Migration Assessment

Assess your Spring Boot application for migration readiness:

- **Local State**: Check for in-memory sessions, singletons, file-based state → [spring-assessment-guide.md](spring-assessment-guide.md#local-state-assessment)
- **File System**: Identify file writes, temp files, shared storage needs → [spring-assessment-guide.md](spring-assessment-guide.md#file-system-usage)
- **Platform Compatibility**: Verify Java 17+, Spring Boot 3.x support → [spring-assessment-guide.md](spring-assessment-guide.md#platform-compatibility)
- **External Resources**: Inventory databases, message brokers, caches → [spring-assessment-guide.md](spring-assessment-guide.md#external-resources-inventory)

## Migration Workflow

1. **Assess** — Analyze application for migration readiness
   > Present findings and complexity rating to user. Ask: "Assessment complete — proceed with containerization?"
2. **Containerize** — Create Dockerfile, build image, push to ACR
3. **Provision** — Create Container Apps environment, configure logging
4. **Deploy** — Deploy container to Azure Container Apps
5. **Optimize** — Add Spring Cloud components (Config, Eureka, Gateway)

See [spring-deployment-guide.md](spring-deployment-guide.md) for detailed phase-by-phase instructions.

## Key Differences from Azure Spring Apps

| Aspect | Azure Spring Apps | Container Apps |
|--------|-------------------|----------------|
| Deployment Unit | JAR/WAR | Container Image |
| Service Discovery | Built-in Eureka | Managed Eureka component (or Dapr / DNS) |
| Configuration Management | Built-in Config Server | Managed Config Server component (or App Configuration) |
| Scaling | Auto-scaling | HTTP/CPU/Memory/Custom metrics |
| Networking | VNet injection | VNet integration + Internal ingress |

## Best Practices

- Use managed identity for Azure resource access (no connection strings)
- Store secrets in Azure Key Vault, reference via environment variables
- Use Application Insights for observability
- Enable Log Analytics for centralized logging
- Use Azure Files for persistent storage if needed

## Next Steps After Migration

After successful migration:
1. Configure Spring Cloud components (optional)
2. Set up CI/CD pipeline with GitHub Actions / Azure DevOps
3. Configure custom domains and SSL certificates
4. Implement autoscaling rules
5. Hand off to `azure-prepare` for infrastructure optimization
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall