---
title: "SageMaker Unified Studio Spark Upgrade MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/awslabs-sagemaker-unified-studio-spark-upgrade/
description: "Remote EMR Spark upgrade endpoint reached by a local stdio proxy that assumes an IAM role, then edits code and submits validation jobs."
---

# SageMaker Unified Studio Spark Upgrade MCP: review, setup & limitations · Undominated.ai

> Remote EMR Spark upgrade endpoint reached by a local stdio proxy that assumes an IAM role, then edits code and submits validation jobs.

[← Explore all mcp servers](/mcp-servers/)

CLOUD OPERATIONS / AWS Labs

# SageMaker Unified Studio Spark Upgrade MCP

Remote EMR Spark upgrade endpoint reached by a local stdio proxy that assumes an IAM role, then edits code and submits validation jobs.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/awslabs/mcp/tree/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher AWS Labs
 Licence [Apache-2.0 ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE)
 Revision 8840003820a7
 [Read what was—and wasn’t—checked ↓](#review)

“Remote stdio-proxied server that plans EMR Spark upgrades, then applies code edits and submits validation jobs.”

 [AWS Labs · upstream description ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The AWS Authentication section assumes an IAM role into spark-upgrade-profile, and the stdio proxy is started with that profile.
- After planning, the code-edit tool applies source updates and validation submits remote EMR jobs that can store artifacts on an S3 path the user names.

### A good fit for

 - Planning an EMR Spark upgrade inside the README's Spark 2.4–3.5 and EMR release windows, then excluding transformations you do not want
- Not a general Spark editor for releases outside those EMR on EC2 and EMR Serverless bounds

### Weigh up before choosing

 - This review did not execute the resource.
- install.command is null. mcp-proxy-for-aws@latest is indented, uses @latest, and is a proxy package rather than this repository path.
- There is no named dry-run flag. The code-edit tool applies changes and validation submits EMR jobs. The README says transformations can be excluded and the user keeps control.
- The EMR-S usage example names an EMR on EC2 source, and the EMR-EC2 example names an EMR Serverless source. Those headings match the validation target, not a second version rule.
- The server directory has no LICENSE. The root LICENSE is Apache-2.0 and the root README says Apache-2.0.
- The linked tool list was not opened. The claim that sensitive data is not stored permanently was not tested.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md
- README.md
- LICENSE

### Our findings

 - The AWS Authentication section writes profile spark-upgrade-profile with an assumed IAM role, a source profile, and a region. The stdio proxy is then pointed at that profile and the spark-upgrade URL.
- The documented flow plans the upgrade, updates dependencies and compiles, applies code edits for Spark incompatibilities, then submits remote EMR validation jobs. A saved plan JSON can be reused, and specific transformations can be excluded.
- Supported paths are Spark 2.4 through 3.5. EMR on EC2 sources start at 5.20.0 and targets stop at 7.12.0 and must be newer than 5.20.0. EMR Serverless sources start at 6.6.0 and targets stop at 7.12.0.
- The README says the caller keeps full control of changes. It does not name a dry-run mode separate from the plan step and that control.

### Not established by this review

 - The resource was not executed.
- The server was not started and no tool was called.
- No EMR validation job was submitted and no project files were edited.
- The linked AWS docs and the docusaurus copy of this page were not fetched.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md)
 - Run the three unindented aws configure set lines that point profile spark-upgrade-profile at an IAM role, a source profile, and a region.
- Register a stdio client whose command is uvx and whose first argument is the indented mcp-proxy-for-aws@latest line, aimed at the spark-upgrade URL.
- Kiro, Cline, and GitHub Copilot are named as clients. Their extra setup is linked out of this file and was not opened.

### Before you start

 - uv
- AWS CLI profile spark-upgrade-profile assuming an IAM role
- A local stdio MCP client

### Compatibility

Kiro · VS Code · Cline · GitHub Copilot · Local stdio MCP clients

### Transports

stdio

### Local stdio proxy, assumed AWS role

 - Assumes the IAM role stored on profile spark-upgrade-profile
- Can edit project code and dependencies for a Spark upgrade
- Can submit EMR validation jobs and store artifacts on an S3 path supplied in the prompt

### Cost model

Apache-2.0 text. The README states no price for the remote endpoint or for EMR jobs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Spark upgrade README ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/sagemaker-unified-studio-spark-upgrade-mcp-server/README.md Supports: Role assumption, code edits, and remote EMR validation
- [Repository licence ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE Supports: Apache License Version 2.0 header
- [Repository README licence section ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md Supports: States the project licence is Apache-2.0

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### AWS Billing and Cost Management MCP Server ↗ Reads realised AWS billing and cost-management data, which is a different number from the advertised unit price.](/mcp-servers/awslabs-aws-billing-cost-management/)[### AWS CloudTrail MCP Server ↗ Queries CloudTrail events for an account you administer.](/mcp-servers/awslabs-cloudtrail/)[### AWS CloudWatch Application Signals MCP Server ↗ Reads CloudWatch Application Signals for an account you administer. It is not the general CloudWatch server.](/mcp-servers/awslabs-cloudwatch-applicationsignals/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
