Tmax Tibero on AWS

Partner Solution Deployment Guide

QS

July 2022
Sungyong Cho, Dongkeun Choi, and Eugene Sim, TmaxSoft
Battulga Purevragchaa, AWS Workload Migration Program
Troy Ameigh, AWS Integration & Automation team

Refer to the GitHub repository to view source files, report bugs, submit feature ideas, and post feedback about this Partner Solution. To comment on the documentation, refer to Feedback.

This Partner Solution was created by TmaxSoft in collaboration with Amazon Web Services (AWS). Partner Solutions are automated reference deployments that help people deploy popular technologies on AWS according to AWS best practices. If you’re unfamiliar with AWS Partner Solutions, refer to the AWS Partner Solution General Information Guide.

Overview

This Quick Start deploys Tmax Tibero on the AWS Cloud. This guide covers the steps necessary to deploy this Quick Start. For more information, refer to the Tibero product page.

Costs and licenses

There is no cost to use this Quick Start, but you will be billed for any AWS services or resources that this Quick Start deploys. For more information, refer to the AWS Quick Start General Information Guide.

Before deploying this Quick Start, you must obtain a license for Tibero 6 Enterprise Edition (Cloud Edition) and subscriptions to two Amazon Machine Images (AMIs) in the AWS Marketplace: Tibero 6 Enterprise Edition and Red Hat Enterprise Linux (RHEL) version 8 operating system. For details, refer to Predeployment steps later in this guide.

Architecture

Deploying this Quick Start with default parameters builds the following Tibero environment in the AWS Cloud.

Architecture
Figure 1. Quick Start architecture for Tibero on AWS

As shown in Figure 1, the Quick Start sets up the following:

  • A highly available architecture that spans three Availability Zones.

  • A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*

  • In the public subnets:

    • Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets. Database instances use the NAT gateways to securely download the operating-system packages required to install Tibero.*

    • A Linux bastion host in an Auto Scaling group to allow inbound SSH (Secure Shell) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.*

  • In the private subnets:

    • A Tibero Standby Cluster (TSC), which comprises two EC2 instances in the first two Availability Zones. Each EC2 instance is attached to an Amazon Elastic Block Store (Amazon EBS) volume. These volumes house your primary and standby databases.

    • An EC2 instance in the third Availability Zone—the Tibero observer instance—to detect failure in the primary database.

  • Amazon EventBridge and AWS Lambda to maintain TSC mode by automatically booting the failed primary database in nonactive mode (standby mode) or the failed observer process.

  • An Amazon Simple Storage Service (Amazon S3) bucket that stores the installation files that are used when you deploy the Quick Start.

* The template that deploys this Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

Deployment options

This Quick Start provides the following deployment options:

  • Deploy Tibero into a new VPC. This option builds a new AWS environment that consists of the VPC, subnets, NAT gateways, bastion hosts, and other infrastructure components. It then deploys Tibero into this new VPC.

  • Deploy Tibero into an existing VPC. This option provisions Tibero in your existing AWS infrastructure.

This Quick Start provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and Tibero settings.

Predeployment steps

  1. If you don’t already have one, create an account with Tmax TechNet.

  2. Obtain a license for Tibero 6 Enterprise Edition (Cloud Edition) as follows:

  3. In AWS Marketplace, subscribe to the AMI for Tibero 6 Enterprise Edition.

  4. In AWS Marketplace, subscribe to the AMI for Red Hat Enterprise Linux 8.

Do not to install Red Hat Enterprise Linux. This Quick Start installs it for you.

Deployment steps

  1. Sign in to your AWS account, and launch this Partner Solution, as described under Deployment options. The AWS CloudFormation console opens with a prepopulated template.

  2. Choose the correct AWS Region, and then choose Next.

  3. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  4. On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. When you finish reviewing and customizing the parameters, choose Next.

    Unless you’re customizing the Partner Solution templates or are instructed otherwise in this guide’s Predeployment section, don’t change the default settings for the following parameters: QSS3BucketName, QSS3BucketRegion, and QSS3KeyPrefix. Changing the values of these parameters will modify code references that point to the Amazon Simple Storage Service (Amazon S3) bucket name and key prefix. For more information, refer to the AWS Partner Solutions Contributor’s Guide.

  5. On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.

  6. On the Review page, review and confirm the template settings. Under Capabilities, select all of the check boxes to acknowledge that the template creates AWS Identity and Access Management (IAM) resources that might require the ability to automatically expand macros.

  7. Choose Create stack. The stack takes about 60 minutes to deploy.

  8. Monitor the stack’s status, and when the status is CREATE_COMPLETE, the Tmax Tibero deployment is ready.

  9. To view the created resources, choose the Outputs tab.

Resources

AWS services

AWS CloudFormation

Amazon Elastic Block Store (Amazon EBS)

AWS Command Line Interface (AWS CLI)

AWS CLI User Guide for Version 2

Amazon EC2

Amazon EC2 User Guide for Linux Instances

Amazon Route 53

Amazon Route 53 Documentation

Amazon S3

Amazon Simple Storage Service Documentation

Amazon VPC

Amazon Virtual Private Cloud Documentation

Tibero

Tibero Database Installation Guide

Troubleshooting

You can post questions for Tibero technical support engineers on the TechNet Technical Q&A/Forum.

For troubleshooting common Quick Start issues, refer to the AWS Quick Start General Information Guide and Troubleshooting CloudFormation.

Customer responsibility

After you deploy a Partner Solution, confirm that your resources and services are updated and configured—including any required patches—to meet your security and other needs. For more information, refer to the Shared Responsibility Model.

Feedback

To submit feature ideas and report bugs, use the Issues section of the GitHub repository for this Partner Solution. To submit code, refer to the Partner Solution Contributor’s Guide. To submit feedback on this deployment guide, use the following GitHub links:

Notices

This document is provided for informational purposes only. It represents current AWS product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided "as is" without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at https://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "as is" basis, without warranties or conditions of any kind, either expressed or implied. Refer to the License for specific language governing permissions and limitations.