Which of the following may be used to track down an amazon ec2 instances stopper

Define the Deployment

1. Configure the following properties:

   Define Deployment Property	Description
   Deployment Name	Name of the deployment. Use a brief name that informs your team of the deployment use case.
   Deployment Type	Select Amazon EC2.
   Environment	Active AWS environment where engine instances will be deployed.
   Engine Type	Type of engine to deploy: Data Collector Transformer
   Engine Version	Engine version to deploy.
   Deployment Tags	Optional tags that identify similar deployments within Control Hub. Use deployment tags to easily search and filter deployments. Enter nested tags using the following format: <tag1>/<tag2>/<tag3>

2. Click one of the following buttons:
   • Cancel - Cancels creating the deployment and exits the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure the Engine

1. Configure the following properties:

   Engine Property	Description
   Stage Libraries	Stage libraries to install on the engine. The available stage libraries depend on the selected engine type and version.
   Advanced Configuration	Access to advanced configuration properties to further customize the engine. As you get started with StreamSets, the default values should work in most cases. The available properties depend on the selected engine type.
   External Resource Source	Source of the external files and libraries, such as JDBC drivers, required by the engine: None - External resources are not defined in the deployment. Select when using a single engine instance to get started with StreamSets, or when your pipelines do not require external resources. Archive File - External resources are included in an archive file defined in the deployment. Select when the deployment launches multiple engine instances and when your pipelines require external resources.
   External Resource Location	Location of the archive file that contains the external resources used by the engine. The archive file must be in TGZ or ZIP format. Enter the location using one of the following formats: File path. For example: /mnt/shared/externalResources.tgz HTTP URL. For example, if the file is stored in an Amazon S3 bucket and the URL is shared publicly: https://<bucket name>.s3.<region>.amazonaws.com/externalResources.tgz Tip: Click the download icon to download a sample externalResources.tgz file to view the required directory structure. Available when using an archive file as the source for external resources.
   Engine Labels	Labels to assign to all engine instances launched for this deployment. Labels determine the group of engine instances that run a job. Default is the name of the deployment.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure the EC2 Autoscaling Group

1. Configure the following properties:

   EC2 Autoscaling Group Property	Description
   Engine Instances	Number of engine instances to deploy. For each engine instance, AWS CloudFormation provisions an EC2 instance in the VPC, and then deploys and launches one engine instance on each EC2 instance. Important: If your pipelines require external resources, you must set up an external resource archive that all engine instances can access before increasing the number of engine instances.
   EC2 Instance Type	Type of EC2 instance to provision. For more information about the types, see Amazon EC2 Instance Types.
   Instance Profile	Instance profile to associate with the provisioned EC2 instances. Enter the instance profile ARN of the instance profile created as a prerequisite by your AWS administrator, using the following format: arn:aws:iam::<account_id>:instance-profile/<role_name> If a default instance profile is defined for the AWS environment, the ARN of the default role is displayed. You can accept the default or override it with a different instance profile.
   AWS Tags	AWS tags to apply to all AWS resources provisioned for this deployment. Enter the tags as key-value pairs. For tag naming requirements, see the AWS documentation. You can define the tags using simple or bulk edit mode. In simple edit mode, click Add Another to define additional tags. In bulk edit mode, configure tags in JSON format. Important: These tags are applied to AWS resources, not to Control Hub deployments.
   Init Script	Initialization script to run on each provisioned instance. Use the script to set up provisioned instances with additional software as required by your organization. The script must be a valid shell script with a maximum size of 8 KB. Enter the script directly in the property or upload a shell script file that uses an .sh extension. After uploading, you can edit the contents of the script.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Configure EC2 SSH Access

1. Configure the following properties:

   EC2 SSH Access Property	Description
   SSH Key Source	Source for the SSH keys that can be used to connect to the provisioned EC2 instances: None - Does not associate an EC2 key pair with the instances. Existing SSH Key Pair Name - Associates an existing EC2 key pair with the instances.
   Key Pair Name	Name of the existing key pair to associate with each EC2 instance. Select the key pair created as a deployment prerequisite.

2. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Share the Deployment

1. In the Select Users and Groups field, type a user email address or a group name.
2. Select users or groups from the list, and then click Add.

   The added users and groups display in the User / Group table.

3. Modify permissions as needed. By default, each added user or group is granted the following permissions:
   • Read - View the details of the deployment and of all engines managed by the deployment. Restart or shut down individual engines managed by the deployment in the Engines view.
   • Write - Edit, start, stop, and delete the deployment. Delete engines managed by the deployment. Also requires read access on the parent environment.
   • Execute - Start jobs on engines managed by the deployment. Starting jobs also requires execute access on the job and read access on the pipeline.

   For more information, see Deployment Permissions.

4. Click one of the following buttons:
   • Back - Returns to the previous step in the wizard.
   • Save & Next - Saves the deployment and continues.
   • Save & Exit - Saves the deployment and exits the wizard, displaying the incomplete deployment in the Deployments view.

Review and Launch the Deployment

1. Click one of the following buttons:
   • Exit - Saves the deployment and exits the wizard, displaying the Deactivated deployment in the Deployments view. You can start the deployment at a later time.
   • Launch Deployment - Starts the deployment, provisions EC2 instances in your AWS account, and launches a StreamSets engine on each instance.
2. If the deployment launches a Transformer engine that works with a Spark cluster, you must grant the Spark cluster access to Transformer.

Auto Scaling Group

In the AWS CloudFormation stack details page, click the Resources tab and then click the ASG link.

The AWS Management Console displays details about the auto scaling group. Explore the following tabs to find information about the provisioned resources:

• Activity - Displays status messages.
• Instance management - Includes a link to each provisioned EC2 instance.

For example, the following image displays the Instance management tab that includes one EC2 instance with a Healthy status:

In the Instances section, click an instance ID to view specific details about the EC2 instance, such as the private IP address. For example, the following image displays a sample EC2 instance summary page: