Release Notes

v8.3.26: (2/21/24)

Bug fixes

Migrated dedicated AWS deployments from gp2 to gp3 storage. (4580)
Added Auth0 authentication for ScaleGrid console. (4089)

v8.3.25: (2/7/24)

Bug fixes

Addressed a bug with SSL when trying to upgrade MongoDB to v.4.2. (4911)

v8.3.24: (1/24/24)

Bug fixes

Data encryption improvements and bug fixes. (4766)

v8.3.23: (1/11/24)

Bug fixes

Akamai updates and bug fixes. (4876)

v8.3.22: (12/26/23)

Bug fixes

VM cleanup and bug fixes. (4667)

v8.3.21: (12/13/23)

Bug fixes

Pen testing and library updates. (4539)

v8.3.20: (11/23/23)

Bug fixes

Bug fixes and improved backup functionality for MySQL. (4649)

v8.3.19: (11/8/23)

Linode - RabbitMQ Resilience Improvements

ScaleGrid introduces improvements to RabbitMQ resilience on Linode, focusing on quicker incident response, improved service-level monitoring, and robust network-level trace capabilities. This update streamlines the retry logic, integrates service observability with monitoring, and establishes a regional cluster for improved performance. Additionally, a new disaster recovery strategy with automated failover ensures high availability and minimal disruption. (4267)

v8.3.18: (11/2/23)

Enhanced Security for ScaleGrid Control Panel

Implemented improvements in the ScaleGrid control panel by updating the security algorithm to provide a safer environment for our users. (4535)

v8.3.17: (10/18/23)

Point in Time Restore (PITR) for PostgreSQL on AWS

ScaleGrid now supports the ability to restore PostgreSQL databases on AWS to a specific point in time for as long as the write ahead log (WAL). ScaleGrid will be rolling out support for all clouds and all databases as a theme over the next several releases. (3442)

v8.3.16: (10/4/23)

Compartment-level Granular Permissions for Oracle Cloud

ScaleGrid now supports much more granular permissions when configuring cloud profiles on Oracle Cloud. This allows an organization to limit ScaleGrid's visibility and scope to one or a specific set of compartments within their Oracle Cloud account organization. (4438)

v8.3.15: (9/20/23)

Improved Backups on MongoDB Sharded Clusters

Addressed an edge case where backups would fail no MongoDB v5 sharded deployments. (3599)

Operational Improvements

This release also focused on addressing numerous operational improvements to assist ScaleGrid's support organization and improve operational efficiency.

v8.3.14: (9/8/23)

Improved MongoDB Cluster restart for Sharded Deployments

Addressed an edge case where a sharded MongoDB cluster would not start all nodes from a failed state. (3168)

v8.3.13: (8/24/23)

Improved MongoDB Management Actions

Addressed edge case to properly update all nodes from requireSSL to allowSSL in a MongoDB replica set. (3945)

PostgreSQL Restore with PgBouncer fails intermittently

Improved reliability Restore within PostgreSQL when using pgBouncer (4328)

v8.3.12: (8/11/23)

“Bring Your Own Cloud” support for Akamai Cloud (formerly Linode)

Now, you can grant ScaleGrid management access to your Akamai Cloud (Linode) account. This lets ScaleGrid manage database deployments on Linodes directly within your Akamai Cloud account and have more granular control on networking, VM oversight, log access, and the ability to leverage any account discounts you may have on compute. (3696)

Support for AMD Based Oracle Compute Shapes

Maximize performance and value with support for Oracles E4 Compute Shapes. (3751)

v8.3.11: (7/27/23)

Point in Time Restore (PITR) for PostgreSQL on DigitalOcean

ScaleGrid gives customers more control over restore points and helps lower RPO and RTO metrics for their DR initiatives. (2036)

Support pgVector

ScaleGrid adds support for the pgVector PostgreSQL extension. Now ScaleGrid customers can manage their tensors and model weightings for their AI/ML initiatives. (3866)

v8.3.10: (7/11/23)

Improvement to Backup Process

Addressed edge case for failed backups on Akamai Cloud for cross-region clusters in the event of network instability. (4116)

MongoDB Migration Improvement

Addressed migration issue when migrating from MongoDB v5.x to v6. (4158)

v8.3.9: (6/28/23)

Support for Microsoft SQL Server

ScaleGrid announces DBaaS management for Microsoft SQL Server for Enterprise customers. (2028)

Add Akamai Cloud Stockholm Region

ScaleGrid adds support for managing deployments within Akamai Cloud’s Stockholm region.(4008)

Reliability Improvement

Bug addressed with Pacemaker configuration on new MySQL cluster deployments on AWS. (4111)

v8.3.8: (6/14/23)

Patch Management

ScaleGrid has made it easier than ever to easily track patch management across all your databases. ScaleGrid’s new feature lets you see all your deployments for all databases on one page and easily see if patches are available for a deployment. ScaleGrid gives you easy access to apply minor and major version updates based on a time that fits well for your applications with minimal downtime. (3144)

Support for Mongo v6.0.5

ScaleGrid add support for Mongo v6.0.5 making it simple for your organization to migrate from legacy versions of Mongo and reap the benefits of the latest v6 offering. (3384)

v8.3.7: (6/1/23)

Datacenter Expansion!

(3778) ScaleGrid continues to expand our cloud ecosystem with datacenter support in new regions helping you better locate your managed database close to your infrastructure and users. ScaleGrid adds support for Akamai Cloud (formerly Linode) regions in:

• Chicago
• Paris
• Seattle
• Chennai
• Milan
• Jakarta

v8.3.6: (5/18/23)

Utilize S3 storage for DO Snapshot Backup

ScaleGrid now uses S3 storage for more cost-efficient storage of backups for customers running on DigitalOcean. (3596)

Minor Platform Improvements and Bug Fixes

Minor improvements with server infrastructure, ScaleGrid agent performance, failure cases creating MongoDB clusters on Azure VMs. (3647, 3697, 3915)

v8.3.5: (5/4/23)

Improved Support for PostgreSQL on AWS

Addressed edge case with patchOS jobs on AWS PostgreSQL 14 clusters. (3185)

v8.3.4: (4/20/23)

Deprecate support for TLS 1.0 and 1.1 on Corp sites

While ScaleGrid supports use of TLS 1.2 for your deployments, you now have the option to disable support for TLS 1.0 and TLS 1.1. (3675)

v8.3.3: (4/5/23)

Role-Based Access Control (RBAC)

Now you can assign users to different permission sets within ScaleGrid. Easily manage permissions and better align with your company’s compliance standards. For example, allow a user to access development and performance tuning while withholding the ability to delete a database. (2526)

v8.3.2: (3/20/23)

Support for AWS gp3 and io2 drives

ScaleGrid added support for both gp3 and io2 drives allowing customers to leverage more performant and scalable storage options. This also supports databases larger than the gp2-limited 16TB. At this time io2 Block Express is available with C6in, C7g, M6in, M6idn, R5b, R6in, R6idn, Trn1, X2idn, and X2iedn instances only. (3338)

Improvements to ScaleGrid Enterprise Agent

Minor improvements to how the ScaleGrid agent updates itself for ScaleGrid Enterprise customer with on-premise implementations. (3589)

v8.3.1: (3/9/23)

Improved index build procedure for multi-node MongoDB Deployments

Minor improvements to the build index process for multi-node MongoDB deployments. (2978)

Disable TLS 1.0 and 1.1 for MongoDB

Customers can now disable TLS 1.0 and TLS 1.1 for MongoDB deployments. (3597)

Improved Credit Card Entry

Updated credit card entry screen for more intuitive entry and better field validation. (823)

Improved Configuration Admin

Improvements to the administration Config parameters screen clearly indicating # of configuration parameters modified since last change a (2097)

UX Improvements for Creating Cross-Region Clusters

Improved messaging in deployment wizard when creating a multi-node, cross-region deployment. The UX now shows warnings pertaining to replication settings and data bandwidth for databases using AWS BYOC. (2550)

Updated AWS Java SDK

Updated AWS Java SDK from 1.11 to 1.12. (3445)

Patching improvement for PostgreSQL 14.6 deployments on AWS

Fixed non-critical error when patching OS on AWS for PostgreSQL 14.6 deployments. (3592)

Fixed Upgrade Agent Process for MongoDB Clusters

Fixed an edge case that would prevent all the agents on each node of a MongoDB cluster from updating. (3593)

Improvement to VM Creation with AWS EC2

Patched a issue that would prevent creating a VM for a AWS BYOC customer on a new deployment. (3600)

v8.3.0: (2/27/23)

Updated MongoDB Follower Functionality

Addressed the case where a database defined in a follower state may keep the follower state after the source cluster is deleted. ScaleGrid now deletes all scheduled follower update jobs in addition to removing the follower state eliminating any job failure messages. (1920)

Support for Linode's new IAD Datacenter

Customers can now create deployments within Linode's new IAD datacenter. (3526)

Improved support for PostgreSQL Imports

Improved our migration process to more easily import databases from non-ScaleGrid deployments. (2490)

Improved conversion process from standalone to multi-node setup for PostgreSQL deployments

The ScaleGrid UX now supports a wizard to migrate a standalone PostgreSQL deployment to a cluster. (2277)

Improved Backup Name Field Validation

Ad Hoc backup allowed a user to enter a "-" which was a reserved character for some clouds causing an error when creating the backup on some clouds. This character is not blocked via field validation rules. (3315)

v8.3.2: (3/20/23)

Support for AWS gp3 and io2 drives

ScaleGrid added support for both gp3 and io2 drives allowing customers to leverage more performant and scalable storage options. This also supports databases larger than the gp2-limited 16TB. At this time io2 Block Express is available with C6in, C7g, M6in, M6idn, R5b, R6in, R6idn, Trn1, X2idn, and X2iedn instances only. (3338)

Improvements to ScaleGrid Enterprise Agent

Minor improvements to how the ScaleGrid agent updates itself for ScaleGrid Enterprise customer with on-premise implementations. (3589)

v8.3.1: (3/9/23)

Improved index build procedure for multi-node MongoDB Deployments

Minor improvements to the build index process for multi-node MongoDB deployments. (2978)

Disable TLS 1.0 and 1.1 for MongoDB

Customers can now disable TLS 1.0 and TLS 1.1 for MongoDB deployments. (3597)

Improved Credit Card Entry

Updated credit card entry screen for more intuitive entry and better field validation. (823)

Improved Configuration Admin

Improvements to the administration Config parameters screen clearly indicating # of configuration parameters modified since last change a (2097)

UX Improvements for Creating Cross-Region Clusters

Improved messaging in deployment wizard when creating a multi-node, cross-region deployment. The UX now shows warnings pertaining to replication settings and data bandwidth for databases using AWS BYOC. (2550)

Updated AWS Java SDK

Updated AWS Java SDK from 1.11 to 1.12. (3445)

Patching improvement for PostgreSQL 14.6 deployments on AWS

Fixed non-critical error when patching OS on AWS for PostgreSQL 14.6 deployments. (3592)

Fixed Upgrade Agent Process for MongoDB Clusters

Fixed an edge case that would prevent all the agents on each node of a MongoDB cluster from updating. (3593)

Improvement to VM Creation with AWS EC2

Patched a issue that would prevent creating a VM for a AWS BYOC customer on a new deployment. (3600)

v8.3.0: (2/27/23)

Updated MongoDB Follower Functionality

Addressed the case where a database defined in a follower state may keep the follower state after the source dcluster is deleted. ScaleGrid now deletes all scheduled follower update jobs in addition to removing the follower state eliminating any job failure messages. (1920)

Support for Linode's new IAD Datacenter

Customers can now create deployments within Linode's new IAD datacenter. (3526)

Improved support for PostgreSQL Imports

Improved our migration process to more easily import databases from non-ScaleGrid deployments. (2490)

Improved conversion process from standalone to multi-node setup for PostgreSQL deployments

The ScaleGrid UX now supports a wizard to migrate a standalone PostgreSQL deployment to a cluster. (2277)

Improved Backup Name Field Validation

Ad Hoc backup allowed a user to enter a "-" which was a reserved character for some clouds causing an error when creating the backup on some clouds. This character is not blocked via field validation rules. (3315)