Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

EC2 Configuration

EC2 Configuration

The following table describes cloud provisioning configuration EC2 configuration properties:
Property
Description
EC2 Key Pair
EC2 key pair to enable communication with the EMR cluster master node.
Optional. This credential enables you to log into the cluster. Configure this property if you intend the cluster to be non-ephemeral.
EC2 Subnet
ID of the subnet on the VPC in which to create the cluster.
Use the subnet ID of the EC2 instance where the cluster runs.
Master Security Group
Optional. ID of the security group for the cluster master node. Acts as a virtual firewall to control inbound and outbound traffic to cluster nodes.
Security groups are created when the AWS administrator creates and configures a cluster in a VPC. In the AWS console, the property is equivalent to ElasticMapReduce-master.
You can use existing security groups, or the AWS administrator might create dedicated security groups for the ephemeral cluster.
If you do not specify a value, the cluster applies the default security group for the VPC.
Additional Master Security Groups
Optional. IDs of additional security groups to attach to the cluster master node. Use a comma-separated list of security group IDs.
Core and Task Security Group
Optional. ID of the security group for the cluster core and task nodes. When the AWS administrator creates and configures a cluster In the AWS console, the property is equivalent to the ElasticMapReduce-slave security group
If you do not specify a value, the cluster applies the default security group for the VPC.
Additional Core and Task Security Groups
Optional. IDs of additional security groups to attach to cluster core and task nodes. Use a comma-separated list of security group IDs.
Service Access Security Group
EMR managed security group for service access. Required when you provision an EMR cluster in a private subnet.


Updated September 28, 2020