Planning your Db2 on AWS configuration
Before you deploy Db2 on Amazon Web Services (AWS), you need to choose an AWS managed service option, as well as an Amazon EC2 instance type and cloud storage option that meet your needs.
Overview of a Db2 on AWS configuration
Deploying a Db2 instance on AWS can be summarized as follows:
- Your system administrator creates an AWS account and chooses a managed service platform for your
Db2 instance. You can run your Db2 instance on the following AWS managed services:
- Db2 on the Red Hat OpenShift Service on AWS (ROSA)
- Amazon Elastic Kubernetes Service (EKS)
- Using a series of command line tools, your administrator creates an AWS cluster based on your specific requirements. An EC2 instance is selected and a file system and storage class are created.
- Your administrator then runs the Db2 Operator and deploys your Db2 instance to your AWS cluster.
Once your Db2 instance is deployed, users can connect to a database in the instance in much the same way as they connect to an on-premise data source.

Choosing an Amazon EC2 instance type
Use the information in Table 1 to determine the size requirements of your Db2 on AWS system. Based on your selection, go to the list of Amazon EC2 instance types to find the AWS instance type that's right for your Db2 deployment. In addition to the sizing values shown in Table 1, the EC2 instance type list shows other factors to consider, such as cost and region.
Size | CPUs | Memory (GB) | AWS Instance Type (Suggested) | Description |
---|---|---|---|---|
Small | 7 | 98 |
|
|
Medium | 15 | 226 |
|
|
Large | 31 | 482 |
|
|
Choosing cloud storage
- For database storage, log storage, and use of temporary table spaces, use a block storage solution.
- For metadata and backup storage, use a shared file storage solution.
