Deployment Guide
Learn how to deploy Upsolver to a VPC in your AWS account.
Learn how to deploy Upsolver to a VPC in your AWS account.
To properly deploy Upsolver into your AWS account, you must have an AWS IAM user with permission to execute the actions listed below. You will use this IAM user to launch the CloudFormation stack created for you by Upsolver.
Create, launch, stop, and rollback CloudFormation stacks
Create and modify IAM users, roles, and policies
Create and modify Amazon S3 buckets and objects
Create and modify VPC, security groups, subnets, internet gateway, and route tables
The following table lists the types and quantities of resources Upsolver will consume when deploying Upsolver into your VPC. You must ensure that you have the required resources or the installation may fail.
The following resources are created when you deploy Upsolver to your AWS account:
UpsolverServerRole: This IAM role is attached to Upsolver EC2 servers and provides access to read and write data from S3 and communicate with other AWS resources.
UpsolverManagementRole: This IAM role is attached to the management plane servers used by Upsolver to create and manage data processing servers in your AWS account. It does not provide access to data; your data remains inaccessible from outside the account.
Default S3 Bucket: This bucket is used as the default output location for Upsolver jobs.
Kinesis Data Stream: Used for synchronization of pipeline operations across clusters and between data processing servers.
Elastic IP: An EIP is used to access the API server.
See AWS Role Permissions for a detailed description of the permissions given to each of the roles.
To deploy Upsolver in your AWS account, you first need to sign up and log in to the Upsolver Cloud. If you already have an account with Upsolver, log in via https://sqlake.upsolver.com and if you do not have an account, you can sign up at https://sqlake.upsolver.com/signup. After logging in, you can continue to the next step to initiate the integration.
If this is your first time signing in to Upsolver, you will be greeted with the screen shown below. Please navigate to the Settings tab of the console, as shown below:
On the Settings page, click Cloud Integration to display the following screen:
Then choose the Start Integration option.
The form that appears asks you to provide information specific to your target environment. In the majority of cases, the defaults can be used when deploying into a new VPC. If you are deploying into an existing VPC. you will need to update your specific VPC details.
This is the range of IPv4 addresses that will be used for Upsolver servers. You may want to change the CIDR block to meet your company's IP allocation guidelines, avoid conflict with other connected networks, or simply leave the default. Note, that if you anticipate running large Upsolver clusters, you will need sufficient IP addresses to support the number of expected nodes across all of your clusters.
A list of IP addresses (in CIDR range format) from which Upsolver (API server) will be reachable. We recommend restricting access to Upsolver for users accessing it from your corporate network or specific VPC IP addresses.
If you anticipate needing Upsolver’s help in troubleshooting and quickly resolving issues with your Upsolver environment, consider enabling this option. Enabling it will give Upsolver support engineers access to your API server, allowing them to inspect your data pipelines, access servers, and change configuration parameters. Upsolver does not have access to your actual data, only the SQL resources you create (connections, jobs, schemas) and associated metadata.
Disabling this option will not allow Upsolver to access your Upsolver environment (API server). You can enable and disable this option at a later time if requirements change.
Select the AWS region where Upsolver will be deployed. This is the region where the CloudFormation stack will execute and all the Upsolver resources will be deployed. You can only deploy into one region at a time. If you need to deploy Upsolver into multiple regions, you will need to follow this guide multiple times, once per region.
Currently, Upsolver supports deploying into AWS public cloud regions only, not including China.
By default, when deploying Upsolver, Upsolver will create a new VPC in your AWS account where all the resources will be deployed. You may choose to deploy Upsolver into an existing VPC by enabling this option.
When enabled, you will need to enter the target VPC ID. This can be found in the AWS console, from the VPC console.
After entering the VPC ID, enter the Subnets that the Upsolver servers will be deployed to. The Availability Zone and Subnet ID can be found in the Subnets section of the VPC console. You can either enter these into the deployment form manually or import them via a CSV file.
After you complete making the necessary changes to the configuration screen, click Next.
Before you can launch the CloudFormation stack, click the Launch CloudFormation button, which will redirect you to the AWS Console in a new browser window. Login using the IAM user you created as a prerequisite, with the required IAM permissions to launch the stack.
The CloudFormation stack is now created, and ready to be reviewed in the AWS console.
Scroll to the bottom of the page and check the box I acknowledge that AWS CloudFormation might create IAM resources with customer names. Then click the Create stack button.
The CloudFormation stack will now begin to run. If your logged-in IAM user does not have the required permissions to deploy all of the resources defined in the stack, you will receive a permission denied error message and will need to update your user permissions and rerun the stack.
The CloudFormation console will automatically refresh periodically updating you on its progress. You can track the detailed progress of each stage in the stack by clicking on the Events tab, and for quicker updates, manually refresh the page. You will see certain events in progress and others that have been completed.
For example:
If any errors are encountered during the deployment process, you will see them here and the stack will be rolled back. All resources that were previously created by the stack will be deleted, so there is no need for you to manually clean up any deployment that did not succeed. After the rollback is marked complete, you can fix any errors and try again.
For assistance in troubleshooting any failed stack deployment, please reach out to Upsolver Support or leave a comment in our Slack channel.
After the stack has deployed successfully, switch back to the Upsolver interface. Below is an example of a successful deployment.
Back in Upsolver, you will be greeted by a message that the integration was successful, followed by a screen detailing the remaining steps in the deployment, such as installing the Upsolver software and configuring the servers. This process should take between three and five minutes to complete.
That’s it! You are now ready to start using Upsolver within your own AWS account. You can begin building pipelines using your own data simply by browsing the template gallery and selecting one that matches the sources and targets you are looking for.
Item
Required
Default Limit
Comments
CloudFormation Stack
At least 1. One is required for every VPC integration
200
-
IAM Role
1
1000
-
IAM Instance Profile
1
1000
-
S3 Bucket
1
100
-
VPC
1
5
-
Internet Gateway
1
5
-
EC2 Elastic IPs
2
5
-
EC2 Spot Instances
2
Dynamic
Instance Types:
r4.large
m5.2xlarge
m5d.2xlarge
m5a.2xlarge
Kinesis Stream Shard
1
200
Upsolver uses Kinesis Data Streams to balance workload between servers
