| title | parent | tags | categories | thumbnail | date | description | author | mrm | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Getting Started with MySQL HeatWave for AWS on AWS |
|
|
|
assets/a-mysqglhw-devrel0622-thmb001.png |
2022-10-08 17:00 |
Setting up on AWS to connect to MySQL HeatWave on AWS. We'll create a database and endpoint. We also provision MySQL HeatWave on AWS. |
Victor Agreda |
WWMK220224P00058 |
If you're developing database applications on AWS and need a massively parallel, high performance, in-memory query accelerator for the MySQL Database Service, that's what MySQL HeatWave on AWS was built to do. Instead of crafting complicated ETL pipelines to move data around, HeatWave accelerates MySQL performance by orders of magnitude for combined analytics and transactional workloads (OLAP and OLTP). The MySQL Database Service is built on MySQL Enterprise Edition, which allows developers to quickly create and deploy secure cloud native applications using the world's most popular open source database.
HeatWave can perform analytics in real time, and MySQL HeatWave for Amazon Web Services (AWS) is a fully managed service, developed and supported by the MySQL team in Oracle.
One of the best things about Oracle MySQL HeatWave is the ability to run analytics directly against your existing transactional data, so there's no need to shuffle that data off to a separate system when you need to perform massively parallel analysis.
To get started, let's set up a MySQL database on AWS so we can connect to HeatWave for analysis.
{% imgx assets/aws-creatingdb-devrel0922.png %}
Note that HeatWave on AWS is integrated with OCI's Identity and Access Management system. When you sign up for HeatWave on AWS, you'll be directed to the OCI login page where you must sign in with an OCI Cloud Account. After signing in, you'll be directed to the OCI Console to complete the MySQL HeatWave on AWS sign-up process. When signing into the HeatWave Console, you are directed to OCI for authentication and then back to the HeatWave Console. To keep things simple, billing is still managed and monitored in OCI.
Since it's a multi-cloud world, in this article we're creating an AWS database we can connect to MySQL HeatWave on AWS.
- An Oracle Cloud Account name
- An AWS account and root user credentials
- A compatible browser (Chrome 69+, Safari 12.1+, or Firefox 62+ or any browser that is Oracle Jet-approved)
We are assuming you're creating the database and administering it, or at least getting the prep work done. Or maybe you've already set something up in AWS -- either way, this is a quick-and-dirty overview of getting started.
- IAM User Keys
- Create a VPC
- Create a database instance
- Connect to database
- Activate HeatWave on AWS
In our example, we’re using a quick and dirty approach to set things up to use HeatWave.
Basically we'll lean on the "easy mode" in AWS to create a Compute instance, network access, and database. Once we have the endpoint for our database we can activate MySQL HeatWave on AWS which we can use to run analytics. Easy!
-
Identity Access Management on AWS
If you've set up your own AWS account, you've already got admin access. Of course, for best practices we wouldn't want to do everything as root, so here we should go to Users and choose Add Users. Go ahead and create an Administrator account and check the box next to AWS Management Console access. Use a custom password.
Choose Next: Permissions. In Set permissions select Add user to group. You'll then Create group, and for the name let's be descriptive and call it Administrators.
Select filter policies and then AWS managed - job function. In that policy list, check Administrator Access. Now you can Create group!
You may need to refresh the page, but select this new group and choose Next: Tags. You can now add tags in much the same way as in OCI, helping you organize and manage projects.
Using Next: Review you can see the groups to be added for this new user -- so you're basically done and can click Create User.
AWS uses access keys similar to OCI when signing in with keys. To get the keys for this new user, go to the IAM console > Users > and choose the name of the new user. Choose the Security credentials tab. In the Access keys section, select Create access key.
Just like on OCI, you won't get another chance to grab the secret key, so select Show. You can now download the .csv file and close the dialog box. You're all set to use the key pair.
-
Create a a VPC and configure for database access
Now that we've created an admin, let's create a security group and some network access. You can read all about creating a new VPC here.
Much like OCI, this tool allows us to create and configure network access with full firewall controls so we can open up an endpoint for our database. But we'll also need to set up some security controls.
Head to the VPC console at console.aws.amazon.com/vpc.
In the upper-right corner you'll choose the region. MySQL HeatWave on AWS supports all availability zones within supported AWS regions, with the exception of those that do not support the Amazon EC2 instance types used by MySQL HeatWave on AWS.
The AWS regions where MySQL HeatWave on AWS is available include: US East (Northern Virginia) Region (us-east-1).
Now, in Navigation, choose Security Groups. Choose Create... and add the basic details as you see fit. Choose the VPC you want to create your database in.
For Inbound rules, choose Add rule, and for Type choose Custom TCP. Next is Port range, so enter the port value to use for your DB instance, and for Source, choose a security group name or type the IP address range (CIDR value) from where you access the DB instance. Choosing My IP, will allow access to the DB instance from the IP address detected in your browser.
If you need to add more IP addresses or different port ranges, choose Add rule and enter the information for the rule. In our case, we want to add some ingress rules needed to enable the right ports, 3306 and 33060. Here are the details:
Source CIDR: 0.0.0.0/0 Destination Port Range: 3306,33060 Description: MySQL Port(Optional) In Outbound rules, add rules for outbound traffic. By default, all outbound traffic is allowed.
Choose Create security group.
Looking good so far!
-
Create a MySQL database instance
In point of fact, you can create a VPC along with an EC2 instance and have connectivity along with a database in a few simple steps. Not only that, it'll be a MySQL database. The sticking point is that the VPC you create won't be configured to allow incoming external traffic. Thus, if you go the "easy" route, you'll need to edit the access list on the VPC it creates. That's not difficult, just be aware of the extra steps.
{% imgx assets/aws-dbchoices-panel-devrel0922.png %}
Instead, we'll leap straight into a MySQL database instance. Go to the RDS console, and choose the region you used above. Click Create Database and choose Standard Create. Choose MySQL (that seems obvious).
Configure the database ID and credentials -- you know how important these will be, as we'll use them to wire up our HeatWave cluster to the database.
In Additional conncectivity configurations, set Public Accessible to yes and the VPC security group will need to open Database port 3306.
We'll set the authentication to password auth, and enter a name for the initial database. The rest is largely set, so we can create our datbase now.
Don't forget that in our security group rules we should set CIDR inbound and outbound rules to 0.0.0.0/0.
It may take several minutes for this to finish setting up. Below is one example of a database configuration.
{% imgx assets/aws-hw-db-config-devrel0922.png %}
-
Connect to the database
Go to Databases on RDS. Click on your db instance to find your DB Endpoints in Connectivity & Security.
For the password, you should have this somewhere from when you created the instance. You may now use these credentials from within the MySQL HeatWave on AWS console, which we'll set up now. Just remember that your database will need some data in it!
Before proceeding, feel free to download some demo data and pop it in the database to play around on HeatWave -- the hard part is done!
In RDS > Databases > (your database) you'll find endpoint info under Connectivity & security. Of course, you'll need the DNS name, username, and password before activating HeatWave as you'll use those to connect.
-
Activate MySQL HeatWave on AWS
To connect our HeatWave cluster to our MySQL AWS database, we need to activate it.
Navigate your browser to http://cloud.mysql.com/.
Click Sign Up.
A field is displayed for entering your email address. Once you enter your email, you're directed to an Account Information page for creating an Oracle Cloud account, which is required to use MySQL HeatWave on AWS. Once you verify your email, you'll go to a page for verifying the email address and providing initial account information. Follow the prompts.
After providing the initial account information, you are directed to a Get Started page in the Oracle Cloud Infrastructure (OCI) Console. Click the Enable MySQL HeatWave on AWS link in the Quickstarts section of the page.
You are directed to a MySQL HeatWave on AWS Administration page where you'll see a dialog which will guide you through the setup process. Note that a paid account is required. Once your upgrade is complete you'll wind up on the OCI Console.
From the OCI Console navigation menu, select Databases. MySQL HeatWave on AWS appears on the Home tab under the Featured label.
Under MySQL HeatWave on AWS, click Administration.
Click Provision to provision MySQL HeatWave on AWS.
After the provisioning operation is completed, a message appears stating that MySQL HeatWave on AWS is ready and you're presented with options to open the MySQL HeatWave console, set up users, and view billing information.
Thus far we've created a MySQL database on AWS and activated an OCI account and MySQL HeatWave on AWS using our shiny new Oracle account. Using our login for our database, we can use this tool to run queries impossibly fast -- and we're just getting started!
Want to know more? Join the discussion in our public Slack channel!