OpenText Analytics Database 26.2.x – OpenText Analytics Database on Amazon Web Services

Setup: Supported AWS instance types

Mon, 01 Jan 0001 00:00:00 +0000

OpenText™ Analytics Database supports a range of Amazon Web Services instance types, each optimized for different purposes. Choose the instance type that best matches your requirements. The two tables below list the AWS instance types that the database supports for database cluster hosts, and for use in MC. For more information, see the Amazon Web Services documentation on instance types and volumes.

Important

If you plan to use an Amazon Machine Image (AMI) on multiple AWS accounts, make sure to subscribe to the image on all your accounts. This allows you to access an image even when it is delisted from the AWS Marketplace.

Instance types for database cluster hosts

Each Amazon EC2 Instance type natively provides one of the following storage options:

Elastic Block Store (EBS) provides durable storage: Data files stored on instance persist after instance is stopped.
Instance Store provides temporary storage: Data files stored on instance are lost when instance is stopped.

OpenText™ Analytics Database AMIs can use either the Instance Metadata Service Version 1 (IMDSv1) or the Instance Metadata Service Version 2 (IMDSv2) to authenticate to AWS services, including S3.

For more information about storage configuration in AWS, see Configure storage.

Note

Instance types that support EBS volumes support encrypting.

Optimization	Instance Types Using Only EBS Volumes (Durable)	Instance Types Using Instance Store Volumes (Temporary)
General purpose	m4.4xlarge m4.10xlarge m5.4xlarge m5.8xlarge m5.12xlarge	m5d.4xlarge m5d.8xlarge m5d.12xlarge
Compute	c4.4xlarge c4.8xlarge c5.4xlarge c5.9xlarge c6i.4xlarge c6i.8xlarge c6i.12xlarge c6i.16xlarge c6i.24xlarge c6i.32xlarge	c3.4xlarge c3.8xlarge c5d.4xlarge c5d.9xlarge
Memory	r4.4xlarge r4.8xlarge r4.16xlarge r5.4xlarge r5.8xlarge r5.12xlarge r6i.4xlarge r6i.8xlarge r6i.12xlarge r6i.16xlarge r6i.24xlarge r6i.32xlarge	r3.4xlarge r3.8xlarge r5d.4xlarge r5d.8xlarge r5d.12xlarge
Storage		d2.4xlarge d2.8xlarge i3.4xlarge i3.8xlarge i3.16xlarge i3en.3xlarge i3en.6xlarge i3en.12xlarge i4i.4xlarge i4i.8xlarge i4i.16xlarge

Note

By default, the c4.8xlarge, d2.8xlarge, and m4.10xlarge instances have their processor C-states set to a value of 1 in the OpenText™ Analytics Database AMI. This measure is meant to improve performance by limiting the sleep states that an instance running the database uses.

For more information about sleep states, visit the AWS Documentation.

Instance types available for MC hosts

Optimization	Type	Supports EBS Storage (Durable)	Supports Ephemeral Storage (Temporary)
Computing	c4.large c4.xlarge c5.large c5.xlarge	Yes Yes Yes Yes	No No No No

Optimization

Type

Supports EBS Storage (Durable)

Supports Ephemeral Storage (Temporary)

Computing

c4.large

c4.xlarge

c5.large

c5.xlarge

Yes

Choosing AWS Eon Mode instance types

When running an Eon Mode database in AWS, choose instance types that support ephemeral instance storage or EBS volumes for your depot, depending on cost and availability. OpenText recommends either r4 or i3 instances for production clusters. It is not mandatory to have an EBS-backed depot, because in Eon Mode, a copy of the data is safely stored in communal storage. However, you must have an EBS-backed catalog for Eon Mode databases.

The following table provides information to help you make a decision on how to pick instances with ephemeral instance storage or EBS only storage. Check with Amazon Web Services for the latest cost per hour.

Important

If you select instances that use instance store, if you then terminate those instances there is the potential for data loss. For Eon mode, MC displays an alert to inform the user of the potential data loss when terminating instances that support instance store.

Storage Type	Instance Type	Pros/Cons
Instance storage	i3.8xlarge	Instance storage offers better performance than EBS attached storage through multiple EBS volumes. Instance storage can be striped (RAIDed) together to increase throughput and load balance I/O. Data stored in instance-store volumes is not persistent through instance stops, terminations, or hardware failures.
EBS-only storage	r4.8xlarge with 600 GB EBS volume attached	Newer instance types from AWS have only the EBS option. In most AWS regions, it's easier to provision a large number of instances. You can terminate an instance but leave the EBS volume around for faster revive. Perserving the EBS will preserve the depot. While some of the cached files might have become stale, they will be ignored and evicted. Much of the cached data will not be stale. It will save time when the node revives and warms its depot. Take advantage of full-volume encryption.

Storage Type

Instance Type

Pros/Cons

Instance storage

i3.8xlarge

Instance storage offers better performance than EBS attached storage through multiple EBS volumes. Instance storage can be striped (RAIDed) together to increase throughput and load balance I/O.

Data stored in instance-store volumes is not persistent through instance stops, terminations, or hardware failures.

EBS-only storage

r4.8xlarge with 600 GB

EBS volume attached

Newer instance types from AWS have only the EBS option. In most AWS regions, it's easier to provision a large number of instances.

You can terminate an instance but leave the EBS volume around for faster revive. Perserving the EBS will preserve the depot. While some of the cached files might have become stale, they will be ignored and evicted. Much of the cached data will not be stale. It will save time when the node revives and warms its depot.

Take advantage of full-volume encryption.

More information

For more information about Amazon cluster instances and their limitations, see Manage Clusters in the Amazon Web Services documentation.

Setup: AWS authentication

Mon, 01 Jan 0001 00:00:00 +0000

Amazon defines two ways to control access to AWS resources such as S3: IAM roles and the combination of id, secrets, and (optionally) session tokens. For long-term access to non-communal storage buckets, you should use IAM roles for access control centralization. You do not need to change your application's configuration if you want to change its access settings. You just alter the IAM role applied to your EC2 instances.

However, for one-time tasks like backing up and restoring the database or loading data to and from non-communal storage buckets, you should use an AWS access key.

OpenText™ Analytics Database uses both of these authentication methods to support different features and use cases:

An Eon Mode database's access to S3 for communal and catalog storage must always use IAM role authentication. IAM roles are the default access control method for AWS resources. The database uses this method if you do not configure the legacy access control session parameters.
Individual users can read data from S3 storage locations other than the ones the database uses for communal storage. For example, users can use COPY to load data into the database from an S3 bucket or query an external table stored on S3. If the IAM role assigned to the database nodes does not have access to this external S3 data, the user must set an id, secret, and optionally an access token in session variables to authorize access to it. These session variables override the IAM role set on the server. See S3 parameters for a list of these session parameters.
Individual users can export data to S3 using file export. File export cannot use IAM authorization. Users who want to export data to S3 must set id, secret, and optionally access token values in session variables.

Important

If the database is running in Eon Mode, using id and secret authentication is more complex. In addition to having access to the external S3 data, any id that a user sets must be authorized to read from and write to the S3 storage locations that the database uses to store communal and catalog data. The queries that the user executes uses this id for all storage requests, not just those for accessing external S3 data. If the id does not have access to the catalog and communal storage, the user cannot execute queries.

Configuring an IAM role

To configure an IAM role to grant the database access AWS resources you must:

Create an IAM role to allow EC2 instances to access the specific resources.
Grant that role permission to access your resources.
Attach this IAM role to each EC2 instance in the database cluster.

To see an example of IAM roles for the database cluster, look at the roles defined in one of the Cloud Formation Templates provided by OpenText. You can download these templates from any of the OpenText™ Analytics Database entries in the Amazon Marketplace. Under each entry's Usage Information section, click the View CloudFormation Template link, then click Download CloudFormation Template.

For more information about IAM roles, see IAM Roles for Amazon EC2 in the AWS documentation.

Setup: Deploy OpenText Analytics Database using CloudFormation templates

Mon, 01 Jan 0001 00:00:00 +0000

OpenText™ Analytics Database provides CloudFormation Templates (CFTs) on the AWS Marketplace that allow you to get a cluster up and running quickly. Using the template allows you to automatically provision your AWS resources and launch a database cluster and Management Console, with minimal configuration required.

If you prefer to deploy a VPC, instances, and related resources manually, see Manually deploy OpenText Analytics Database on AWS.

For details about creating an Eon Mode or Enterprise Mode database after you create a cluster with CFTs, see Amazon Web Services in MC.

Setup: Manually deploy OpenText Analytics Database on AWS

Mon, 01 Jan 0001 00:00:00 +0000

OpenText™ Analytics Database provides tested and pre-configured Amazon Machine Images (AMIs) to deploy cluster hosts or MC hosts on AWS. When you create an EC2 instance on AWS using an OpenText™ Analytics Database AMI, the instance includes the database software and the recommended configuration. The OpenText™ Analytics Database AMI acts as a template, requiring fewer configuration steps.

This section will guide you through configuring your network settings on AWS, launching and preparing EC2 instances using the OpenText™ Analytics Database AMI, and creating a database cluster on those EC2 instances.

Choose this method of installation if you are familiar with configuring AWS and have many specific AWS configuration needs. To automatically deploy AWS resources and a database cluster instead, see Deploy OpenText Analytics Database using CloudFormation templates.