AWS emr documentation change
Summary
Added 'EMR on EKS' to supported platforms list for troubleshooting
Security assessment
Expanded platform support documentation without security implications. No security features or vulnerabilities addressed.
Diff
diff --git a/emr/latest/ReleaseGuide/spark-troubleshooting-agent-workflow.md b/emr/latest/ReleaseGuide/spark-troubleshooting-agent-workflow.md index 7e14c3dcd..083bcc363 100644 --- a//emr/latest/ReleaseGuide/spark-troubleshooting-agent-workflow.md +++ b//emr/latest/ReleaseGuide/spark-troubleshooting-agent-workflow.md @@ -9 +9 @@ -To initiate the troubleshooting process, you will need access to your failed Spark application identifiers running on supported platforms (EMR-EC2, EMR Serverless, AWS Glue, or Amazon SageMaker Data Notebooks). The application should have accessible logs, Spark History Server, and configuration details. Ensure you have the necessary permissions to access the platform resources and application metadata. Once these requirements are established, you can submit a prompt like the following to kick off the troubleshooting workflow: +To initiate the troubleshooting process, you will need access to your failed Spark application identifiers running on supported platforms (EMR on EC2, EMR Serverless, EMR on EKS, AWS Glue, or Amazon SageMaker Data Notebooks). The application should have accessible logs, Spark History Server, and configuration details. Ensure you have the necessary permissions to access the platform resources and application metadata. Once these requirements are established, you can submit a prompt like the following to kick off the troubleshooting workflow: