Caution
The contents of the docs folder have been moved to the docs-internal-orchestration repository. Please update this documentation in that repository instead.
To view the Scalar Kubernetes documentation, visit the documentation site for the product you are using:
This guide explains how to set up a database for ScalarDB/ScalarDL deployment on AWS.
When you use DynamoDB, you must set REGION, ACCESS_KEY_ID, and SECRET_ACCESS_KEY in the ScalarDB/ScalarDL properties file as follows.
scalar.db.contact_points=<REGION>
scalar.db.username=<ACCESS_KEY_ID>
scalar.db.password=<SECRET_ACCESS_KEY>
scalar.db.storage=dynamoPlease refer to the following document for more details on the properties for DynamoDB.
DynamoDB is available for use in AWS by default. You do not need to set up anything manually to use it.
You can enable PITR as a backup/restore method for DynamoDB. If you use ScalarDB Schema Loader for creating schema, it enables the PITR feature for tables by default. Please refer to the official document for more details.
It is recommended since the point-in-time recovery feature automatically and continuously takes backups so that you can reduce downtime (pause duration) for backup operations. Please refer to the following document for more details on how to backup/restore Scalar product data.
You can configure the monitoring and logging of DynamoDB using its native feature. Please refer to the official document for more details.
It is recommended since the metrics and logs help you to investigate some issues in the production environment when they happen.
// Note that We have not yet tested this feature with Scalar products.
// TODO: We need to test this feature with Scalar products.
It is recommended since the private internal connections not via WAN can make a system more secure.
You can configure the Read/Write Capacity of DynamoDB tables based on your requirements. Please refer to the official document for more details on Read/Write Capacity.
You can configure Read/Write Capacity using ScalarDB/DL Schema Loader when you create a table. Please refer to the following document for more details on how to configure Read/Write Capacity (RU) using ScalarDB/DL Schema Loader.
When you use RDS, you must set JDBC_URL, USERNAME, and PASSWORD in the ScalarDB/ScalarDL properties file as follows.
scalar.db.contact_points=<JDBC_URL>
scalar.db.username=<USERNAME>
scalar.db.password=<PASSWORD>
scalar.db.storage=jdbcPlease refer to the following document for more details on the properties for RDS (JDBC databases).
You must create an RDS database instance. Please refer to the official document for more details.
You can enable automated backups. Please refer to the official document for more details.
It is recommended since the automated backups feature enables a point-in-time recovery feature. It can recover data to a specific point in time. It can reduce downtime (pause duration) for backup operations when you use multi databases under Scalar products. Please refer to the following document for more details on how to backup/restore the Scalar product data.
You can configure the monitoring and logging of RDS using its native feature. Please refer to the official documents for more details.
- Monitoring metrics in an Amazon RDS instance
- Monitoring events, logs, and streams in an Amazon RDS DB instance
It is recommended since the metrics and logs help you to investigate some issues in the production environment when they happen.
Public access is disabled by default. You can access the RDS database instance from the Scalar product pods on your EKS cluster as follows.
- Create the RDS database instance on the same VPC as your EKS cluster.
- Connect the VPC for the RDS and the VPC for the EKS cluster for the Scalar product deployment using VPC peering. (// TODO: We need to test this feature with Scalar products.)
It is recommended since the private internal connections not via WAN can make a system more secure.
When you use Amazon Aurora, you must set JDBC_URL, USERNAME, and PASSWORD in the ScalarDB/ScalarDL properties file as follows.
scalar.db.contact_points=<JDBC_URL>
scalar.db.username=<USERNAME>
scalar.db.password=<PASSWORD>
scalar.db.storage=jdbcPlease refer to the following document for more details on the properties for Amazon Aurora (JDBC databases).
You must create an Amazon Aurora DB cluster. Please refer to the official document for more details.
Amazon Aurora automatically gets a backup by default. You do not need to enable the backup feature manually.
If you want to change some backup configurations like the backup retention period and backup window, you can configure them. Please refer to the official document for more details.
Please refer to the following document for more details on how to backup/restore the Scalar product data.
You can configure the monitoring and logging of Amazon Aurora using its native feature. Please refer to the official documents for more details.
- Monitoring metrics in an Amazon Aurora cluster
- Monitoring events, logs, and streams in an Amazon Aurora DB cluster
It is recommended since the metrics and logs help you to investigate some issues in the production environment when they happen.
Public access is disabled by default. You can access the Amazon Aurora DB cluster from the Scalar product pods on your EKS cluster as follows.
- Create the Amazon Aurora DB cluster on the same VPC as your EKS cluster.
- Connect the VPC for the Amazon Aurora DB cluster and the VPC for the EKS cluster for the Scalar product deployment using VPC peering. (// TODO: We need to test this feature with Scalar products.)
It is recommended since the private internal connections not via WAN can make a system more secure.