Amazon EMR
Managed Hadoop and Spark cluster platform on EC2 for large-scale data processing.
- Provider
- aws
- Kind
- Big data cluster
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | ▸ false |
| engine | enum | spark | hadoop | presto | flink | hpc | ray | dask | kubernetes-batch | no | — | inherited |
| instanceProvisioning | enum | instance-groups | instance-fleets | no | instance-groups | inherited |
| managed | boolean | — | no | false | ▸ true |
| primaryNodeHighAvailability | boolean | — | no | false | inherited |
| runtimeVersion | string | — | no | — | inherited |
| securityConfiguration | boolean | — | no | false | inherited |
| spotInstances | boolean | — | no | false | ▸ false |
| workerNodes | integer | — | no | — | inherited |
| zoneRedundant | boolean | — | no | — | ▸ false |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "emr", component: "aws-emr" }Elastic High Performance Computingalibaba-e-hpcE-MapReducealibaba-e-mapreduceAWS Clean Roomsaws-clean-roomsAmazon EMR Serverlessaws-emr-serverlessAWS Parallel Computing Serviceaws-pcsAmazon SageMaker HyperPodaws-sagemaker-hyperpodAzure CycleCloudazure-cyclecloudAzure Databricksazure-databricksAzure HDInsightazure-hdinsightArmadaarmadaGeneric big data clusterbig-data-clusterDaskdaskDatabricksdatabricksApache Hadoop YARNhadoop-yarnRayraySlurmslurmApache Spark clusterspark-clusterVolcanovolcanoCluster Directorgoogle-cluster-directorDataprocgoogle-dataprocManaged Service for Apache Spark (serverless)google-dataproc-serverlessIBM Analytics Engineibm-analytics-engineOCI AI Data Platformoci-ai-data-platformOCI Big Data Serviceoci-big-data-serviceOCI Data Flowoci-data-flow
# yaml-language-server: $schema=../../schema/component.schema.json # Amazon EMR cluster on EC2: managed Hadoop/Spark cluster platform ("What is Amazon EMR?"). A cluster # "can reside only in one Availability Zone or subnet" and launches with one primary node unless three are # chosen ("Plan and configure primary nodes"); managed scaling is enabled explicitly ("Using managed scaling") # and encryption at rest or in transit needs a security configuration ("Encryption options for Amazon EMR"). schemaVersion: "1" type: "component" id: "aws-emr" kind: "big-data-cluster" provider: "aws" docs: "https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-ha.html" aliases: ["EMR"] defaults: managed: true autoscaling: false spotInstances: false zoneRedundant: false properties: primaryNodeHighAvailability: type: "boolean" default: false instanceProvisioning: type: "enum" values: ["instance-groups", "instance-fleets"] default: "instance-groups" securityConfiguration: type: "boolean" default: false