reference deployment

Tmax Tibero on AWS

Deploys a relational database using a Tibero Standby Cluster in an Amazon EC2 environment

View deployment guide

This Quick Start deploys a Tibero relational database to the Amazon Web Services (AWS) Cloud. With this architecture, database administrators, enterprise architects, system administrators, and developers can run Tibero in a highly available Amazon Elastic Compute Cloud (Amazon EC2) environment using a Tibero Standby Cluster (TSC). If the primary EC2 instance fails, it fails over to a standby instance.

This deployment installs the Red Hat Enterprise Linux (RHEL) operating system version 8.

duo logo

This Quick Start was developed by TmaxSoft in collaboration with AWS. TmaxSoft is an AWS Partner.

  •  What you'll build

  • This 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 EC2 instances in public and private subnets.*
    • In the private subnets:
      • A Tibero Standby Cluster, 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 dead primary database in nonactive mode (standby mode) or the dead 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 the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy

  • To deploy this Quick Start, follow the steps in the deployment guide, which includes these steps. The stack takes about 60 minutes to launch.

    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).
    3. In the AWS Marketplace, subscribe to the Amazon Machine Images (AMIs) for Tibero 6 Enterprise Edition and Red Hat Enterprise Linux 8. You don't need to install Red Hat Enterprise Linux; this Quick Start installs it for you.
    4. Sign in to your AWS account. If you don't have an account, sign up at https://aws.amazon.com. 
    5. Launch the Quick Start. Before you create the stack, choose the AWS Region from the top toolbar. Choose one of the following options:

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

    View deployment guide for details
  •  Cost and licenses

  • You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    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 8. For details, see the deployment guide.

    The AWS CloudFormation templates for Quick Starts include configuration parameters that you can customize. Some of the settings, such as the instance type, affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy the Quick Start, create AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information about the report, see What are AWS Cost and Usage Reports?