Versions Compared

Old Version 2

changes.mady.by.user Juliane Wetzel

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Install a Datameer X Enterprise clustered instance from Amazon Marketplace. 

...

This guide steps through the requirements and process for installing Datameer X Enterprise from the Amazon Marketplace.  

Overview

Datameer X is a cloud-native analytic lifecycle platform that enables the transformation of raw data into analytics-ready datasets—without hours of engineering time. It leverages the power of AWS EMR compute clusters to handle the scale, volume, and complexity of big data and heavy-duty enterprise workloads. Datameer's intuitive spreadsheet-like interface enables analysis of the raw data on-the-fly, while built-in connectors allow for easy integration of data from a variety of data sources - including S3 and Redshift. 

Datameer X Enterprise, available in the AWS Marketplace, utilizes the AWS CloudFormation Template (CFT) for launching a Datameer X instance alongside relevant resources - VPC, Availability Zones, Subnets, ELB, Security Groups, Datameer X EC2 instances, EMR, S3 bucket. 

...

Review the product information and pricing by visiting Datameer X Enterprise on AWS Marketplace.

Learn more about Datameer X for Amazon Web Services.


Follow the comprehensive Step-by-Step Guide to deploy Datameer X in your AWS account within a few minutes. 

If you experience problems with launching via CFT, please contact Datameer X Support at support@datameer.com.

...

  • A valid AWS account is required for deploying Datameer X Enterprise with abilities to create VPC, Security Groups, S3, EC2 and EMR assets.
  • Familiarity with the stack creation process using CloudFormation Templates.
  • A basic understanding of the purpose and function of Amazon Elastic MapReduce (EMR).

...

By default CloudFormation uses permissions based on your user credentials to create, modify, or delete resources in the stack. Optionally, when configuring stack parameters, you can choose an IAM role to explicitly define how CloudFormation can manage stack resources. For more information see Controlling Access with AWS Identity and Access Management. 

Datameer X Enterprise stack provides an option to enable secure access to the Datameer X instance via HTTPS (port 443). You will be required to provide security certificate that can be created via AWS Certificate Manager. 

...

Once the stack is created and the Datameer X instance is launched, it can be accessed via the web browser using default credentials. See Accessing Datameer X Enterprise. By default the instance is not reachable via public Internet. This can be changed during the stack creation by enabling Auto-assign Public IP option.

Within the Datameer X application, user authentication and authorization can be handled via the Admin interface. Datameer X Enterprise offers both Internal User Management and Remote Authentication (Active Directory and LDAP) options. 

Anchor
sizing
sizing
Sizing 

Datameer X Enterprise can be deployed on AWS using different types of EC2 instances. During the stack creation process you can select which type you would like to use for the Datameer X instance as well as for the creation of the EMR cluster. The following instance type families are supported for deployments: 

...

Various instance types offer different combinations of the number of vCPU per instance, memory, and network performance - this affects job execution/data processing in Datameer X Enterprise. For example, an EMR cluster of 6 instances using the recommended m4.4xlarge type (16 vCPU, 64GiB per instance) processes a medium workload of 1.5GB (100MM records) in approximately 10 minutes. Processing of the same workload can be expedited to ~6 minutes by doubling the infrastructure to 12 m4.4xlarge instances. 

Warning

Datameer Enterprise supports deployment on AWS EMR cluster with up to 48 total vCPU (equivalent to 3 m4.4xlarge nodes) - this is suitable for most workloads.

Note: An EMR cluster is created with a single "master" instance and x number of "worker" instances. When configuring your Datameer X stack, the "Number of EC2 instances in the EMR cluster" defines the number of "worker" instances. For example, leaving this setting with the default value of 2 will trigger creation of the EMR cluster with total of 3 instances of the same type (1 "master" and 2 "worker"). 

Costs 

Datameer X Enterprise is offered with the 14-day free trial. During the trial period you will only be responsible for the AWS services and infrastructure costs. 

After the trial period ends, Datameer X Enterprise is available at a fixed hourly price irrespective of the instance type or deployment region. The total cost of running Datameer X Enterprise on AWS is calculated as following: 

Panel
Total Deployment Cost = Datameer X Enterprise Software Cost + AWS Services & Infrastructure Cost


The Datameer X CloudFormation Template exposes stack configuration parameters (e.g., instance type, number of EC2 instances in the EMR cluster) that you can customize. Some of these settings, such as instance type and the number of instances in the EMR cluster, will affect the total cost of the deployment. For AWS infrastructure cost estimates see AWS Pricing Calculator.

Installation Steps

Anchor
install
install
Launching Datameer X Enterprise from AWS 

  1. Locate and select Datameer X Enterprise from the AWS Marketplace.
  2. From the Datameer X Enterprise product page, select Continue to Subscribe.



  3. After accepting the EULA, select Continue to Configuration.
  4. Select Datameer X Enterprise Clustered Edition fulfillment option, the desired product version, and the region in which to launch the product. 
  5. Select Continue to Launch.

    It is recommended for customers to select the most recent version of the product and the region in which they reside.



  6. On the Launch this Software page, review your configuration, select Launch CloudFormation action, and click Launch.

...

  1. Stack creation starts with specifying the source of the CloudFormation Template (CFT). The Amazon S3 URL field is pre-populated with a URL to the corresponding CFT.



  2. Click Next to navigate to specify stack details.
  3. Enter the Stack Name.



  4. Select a Datameer X Instance Type. See the list of recommended types (see sizing recommendations above).



  5. Configure admin password for Amazon Relational Database Service (RDS) . Password must contain 8 to 41 any alpha-numeric characters, except "/", """, or "@".



  6. Setting EMR cluster parameters:
    1. Enter an Instance Count - a number in the range from 1 - 20 of EC2 instances for the "worker" nodes in the EMR cluster. A single "master" node is created by default in addition to "worker" nodes (e.g., if you entered 3 for the Instance Count setting, the total number of instances created will be 4. There will be 1 "master" node + 3 "worker" nodes.)
    2. Select the Instance Type - the EMR cluster EC2 instance type. See the list of recommended type sizing recommendations above.
    3. Enter a S3 Bucket Name - the name of the S3 bucket used for EMR related storage. It defaults to aws-datameer-bucket. Datameer X CFT automatically appends unique identifier to the entered bucket name to ensure its uniqueness across all regions.



  7. Specify Networking and Security parameters:
    1. Provide the Amazon Resource Name (ARN) of the security certificate to enable HTTPS access to Datameer X Enterprise instance (optional). Security certificate can be created via AWS Certificate Manager. If you do not provide the certificate, the Datameer X Enterprise instance will be accessible via HTTP on port 80. 



    2. Enter the VPC IPv4 Addresses Range - the IPv4 addresses range in the form of Classless Inter-Domain Routing (CIDR) block. See VPCs and Subnets AWS documentation for guidance. 
    3. Specify the the public subnet CIDR block for 2 Public Subnets. The CIDR block must be within the VPC CIDR range.

    4. Select Availability Zones (AZ) for each of the 2 subnets. The AZ must be within the current region.

      Warning

      Availability Zones, subnets must be different from each other. There can only be one subnet per AZ.





    5. Configure Keypair Name - the name of the existing EC2 Keypair to authorize SSH access to the instances. If you don't already have a key pair, refer to Amazon EC2 Key Pair documentation on how to create new key pair. 
    6. Specify SSH Addresses Range in the form of CIDR block. This enables SSH access to the Datameer X EC2 instance. 
    7. Enable Auto-assign Public IP, if you want Datameer X instance to be accessible over the Internet.



    8. Click Next.
  8. Configure advanced Stack Options (optional). We recommend taking default values for all parameters. 
  9. Click Next.
  10. Review the stack configuration, click Create Stack.
  11. The stack configuration is now complete. Stack creation process is initiated and the new stack appears in the list of stacks in the CloudFormation console with CREATE_IN_PROGRESS status.



  12. Once all stack components are created, the status will change to CREATE_COMPLETE.



  13. Now that the Datameer X instance is up and running, you can access it via a web browser. 

Anchor
access
access
Accessing Datameer X Enterprise

  1. Navigate to the CloudFormation Console and locate your Datameer X stack. 

  2. Outputs panel of the Stack details provides parameters needed for accessing your Datameer X instance.


  3. Access Datameer X Enterprise using a web browser.
    • Enter the Datameer X URL in the browser address bar (the URL is provided in the Stack Outputs panel).
  4. On the Datameer X login screen, enter the following credentials:
    1. Username: admin
    2. Password: <cluster ID - obtained from the Stack Outputs panel>



  5. Navigate to View > Admin Tab in the application menu to configure the platform (including user management).



  6. To change the default Admin password, navigate to the Users module under the Admin tab. For more details see Managing User Accounts.

...