Skip to content

Commit 1979066

Browse files
[spark-troubleshoot-agent] lessons learned from upgrade agent
1 parent 162e7cb commit 1979066

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

spark-troubleshooting-agent/POWER.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Before proceeding, ensure the following are installed:
3434

3535
## Step 2: Deploy CloudFormation Stack
3636

37-
**Note**: If you already have a role configured with `sagemaker-unified-studio-mcp` permissions, please ignore. However, it is recommended to deploy the stack as will contain latest updatest for permissions and role policies
37+
**Note**: If the customer already has a role configured with `sagemaker-unified-studio-mcp` permissions, please ignore this step, get the AWS CLI profile for that role from the customer and configure your (Kiro's) mcp.json file (typically located at `~/.kiro/settings/mcp.json`) with that profile. However, it is recommended to deploy the stack as will contain latest updates for permissions and role policies
3838

3939
1. Log into the AWS Console with the role your AWS CLI is configured with - this role must have permissions to deploy Cloud Formation stacks.
4040
1. Navigate to [troubleshooting agent setup page](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/spark-troubleshooting-agent-setup.html#spark-troubleshooting-agent-setup-resources).

0 commit comments

Comments
 (0)