AWS emr documentation change
Summary
Extended pricing explanation to include custom registries and orchestration methods
Security assessment
Change only clarifies billing details without any security-related content.
Diff
diff --git a/emr/latest/EMR-on-EKS-DevelopmentGuide/spark-operator.md b/emr/latest/EMR-on-EKS-DevelopmentGuide/spark-operator.md index cc2bb6f33..f09842cf4 100644 --- a//emr/latest/EMR-on-EKS-DevelopmentGuide/spark-operator.md +++ b//emr/latest/EMR-on-EKS-DevelopmentGuide/spark-operator.md @@ -13 +13 @@ Amazon EMR releases 6.10.0 and higher support the Kubernetes operator for Apache -Amazon EMR calculates pricing on Amazon EKS based on vCPU and memory consumption. This calculation applies to driver and executor pods. This calculation starts from when you download your Amazon EMR application image until the Amazon EKS pod terminates and is rounded to the nearest second. +Amazon EMR calculates pricing on Amazon EKS based on vCPU and memory consumption. This calculation applies to driver and executor pods. This calculation starts from when you download your Amazon EMR application image until the Amazon EKS pod terminates and is rounded to the nearest second. Pricing applies whenever pods run using an image derived from the Amazon EMR runtime, regardless of whether the image is stored in the public Amazon EMR Amazon ECR registry or your own private registry, and regardless of how the job is orchestrated (for example, the StartJobRun API, the Spark operator, or spark-submit).