You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- EMR clusters using instance fleets or instance groups deployed in public or private subnets
9
10
- EMR Virtual clusters that run on Amazon EKS
10
11
- EMR Serverless clusters
@@ -13,7 +14,8 @@ This module supports the creation of:
13
14
- Security group for EMR `service` to support private clusters
14
15
- IAM roles for autoscaling, EMR `service`, and EC2 instance profiles
15
16
16
-
:information_source: The appropriate resources have been tagged with `{ "for-use-with-amazon-emr-managed-policies" = true }` to support the use of the recommended IAM policy `"arn:aws:iam::aws:policy/service-role/AmazonEMRServicePolicy_v2"`. Users are required to tag the appropriate VPC resources (VPC and subnets) as needed. See [here](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-iam-policies.html) for more details regarding v2 of managed EMR policies and their usage requirements.
17
+
> [!IMPORTANT]
18
+
> The appropriate resources have been tagged with `{ "for-use-with-amazon-emr-managed-policies" = true }` to support the use of the recommended IAM policy `"arn:aws:iam::aws:policy/service-role/AmazonEMRServicePolicy_v2"`. Users are required to tag the appropriate VPC resources (VPC and subnets) as needed. See [here](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-iam-policies.html) for more details regarding v2 of managed EMR policies and their usage requirements.
@@ -62,7 +62,6 @@ Note that this example may create resources which will incur monetary charges on
62
62
|[aws_iam_policy_document.assume](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document)| data source |
63
63
|[aws_iam_policy_document.autoscaling](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document)| data source |
64
64
|[aws_partition.current](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/partition)| data source |
65
-
|[aws_region.current](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/region)| data source |
Copy file name to clipboardExpand all lines: examples/virtual-cluster/README.md
+9-16Lines changed: 9 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,10 @@
1
1
# AWS EMR Virtual Cluster Example
2
2
3
-
This example shows how to provision a serverless cluster (serverless data plane) using Fargate Profiles to support EMR on EKS virtual clusters.
4
-
5
-
There are two Fargate profiles created:
6
-
1.`kube-system` to support core Kubernetes components such as CoreDNS
7
-
2.`emr-wildcard` which supports any namespaces that begin with `emr-*`; this allows for creating multiple virtual clusters without having to create additional Fargate profiles for each new cluster.
3
+
This example shows how to provision a serverless cluster (serverless data plane) using EKS Auto Mode to support EMR on EKS virtual clusters.
8
4
9
5
The resources created by the `virtual-cluster` module include:
6
+
10
7
- Kubernetes namespace, role, and role binding; existing or externally created namespace and role can be utilized as well
11
-
- IAM role for service account (IRSA) used by for job execution. Users can scope access to the appropriate S3 bucket and path via `s3_bucket_arns`, use for both accessing job data as well as writing out results. The bare minimum permissions have been provided for the job execution role; users can provide additional permissions by passing in additional policies to attach to the role via `iam_role_additional_policies`
12
8
- CloudWatch log group for task execution logs. Log streams are created by the job itself and not via Terraform
13
9
- EMR managed security group for the virtual cluster
14
10
- EMR virtual cluster scoped to the namespace created/provided
@@ -18,9 +14,9 @@ The resources created by the `virtual-cluster` module include:
18
14
To run this example you need to execute:
19
15
20
16
```bash
21
-
$ terraform init
22
-
$ terraform plan
23
-
$ terraform apply
17
+
terraform init
18
+
terraform plan
19
+
terraform apply
24
20
```
25
21
26
22
Note that this example may create resources which will incur monetary charges on your AWS bill. Run `terraform destroy` when you no longer need these resources.
0 commit comments