Overview
We will be upgrading our Amazon Aurora MySQL database service from version 5.7 to 8.0 to ensure continued optimal performance and security of your applications. This upgrade is mandatory as MySQL 5.7 has reached the end of standard support on Amazon Aurora service.
Why This Upgrade Is Necessary
- MySQL 5.7 has entered extended support phase on Amazon Aurora
- Continued use of MySQL 5.7 incurs additional costs and reduced support coverage
- The upgrade ensures your applications remain on a fully supported database platform
- It provides access to the latest security updates and performance improvements
Benefits of MySQL 8.0
- Improved performance and scalability
- Enhanced security features
- Better JSON document support
- Improved charset and collation handling
- Window functions for advanced analytics
- Enhanced optimizer features for better query performance
- Atomic DDL operations for improved reliability
Timeline and Impact
- Testing Period Start: January 2025
- Production Upgrade Deadline: April 29, 2025
- Your Action Required: Testing period of 2-4 weeks for your application
- Expected Downtime: Minimal (using blue-green deployment approach)
What You Need to Do
- Review Documentation: Examine the upgrade testing guide we'll provide
- Schedule Testing: Allocate time for testing your application with MySQL 8.0
- Perform Testing: Test your application in a dedicated testing environment
- Report Issues: Immediately report any issues discovered during testing
- Approve Migration: Provide sign-off for production upgrade after successful testing
Testing Process
- We will provide a testing environment with MySQL 8.0
- You'll need to verify your application's:
- Basic functionality
- Database connections
- Query performance
- Data integrity
- Character encoding
- Backup and restore procedures
Frequently Asked Questions
Q: Is this upgrade optional?
No, this upgrade is mandatory as MySQL 5.7 has reached the end of standard support on Amazon Aurora service. We must complete the upgrade before the end of February 2025 to ensure continued support and security updates.
Q: Are there any costs associated with this upgrade?
No, this is a mandatory infrastructure upgrade and is not billable to customers. The upgrade is being performed to maintain service quality and security, and all associated costs are covered by us.
Q: Will projects be upgraded individually or all at once?
All projects will be upgraded simultaneously as part of our infrastructure upgrade. This approach ensures consistency across our platform and minimizes the complexity of maintaining multiple database versions.
Q: Will there be any downtime during the upgrade?
We are using a blue-green deployment approach which minimizes downtime. Your application may experience a brief interruption (typically seconds) during the final switchover.
Q: What if we discover issues during testing?
Our technical team will be available to help resolve any issues discovered during testing. Please report any problems immediately through our support channels.
Q: What happens if we don't upgrade?
Remaining on MySQL 5.7 will result in:
- Increased operational costs due to extended support fees
- Reduced support coverage
- Potential security vulnerabilities
- Missing out on performance improvements
Q: Do we need to make any application changes?
Most applications will work without changes, but we recommend thorough testing to ensure compatibility. Pay special attention to:
- Database connection settings
- Character set and collation configurations
- Scaffold changes to support MySQL 8.0 - compatible docker image
Q: What support will be available during the upgrade?
We provide:
- Detailed testing documentation
- Technical support throughout the testing phase
- Assistance with troubleshooting
- Dedicated support during the production upgrade
Q: Can we choose our upgrade date?
Since this upgrade affects our entire database cluster, all projects will be migrated simultaneously on a single cut-over date. If you have any events planned for the migration date, please:
- Review the support ticket we've created for your project
- Inform us of any scheduling conflicts via that ticket
- Plan ahead to reschedule any events that coincide with the cut-over date
We will provide advance notice of the final migration date to allow for proper planning.
Q: What if my application uses non-standard collations?
We’ve added safeguards to enforce utf8mb4_general_ci. If your app uses custom collations, contact our team for a compatibility check.
Q: How are backups handled during the migration?
Backups will be taken before and after the migration.
We’ll verify backup compatibility between MySQL 5.7 and 8.0.
Q: What if I find issues during testing?
Report issues immediately via our support channels. We’ll prioritize fixes and provide rollback options if needed.
Q: Can I delay the migration?
No. AWS will deprecate MySQL 5.7, making delayed migrations risky and unsupported.
Q: How will communications about the upgrade be handled?
We have created individual support tickets for each customer using our hosting platform. All communications regarding the MySQL 8.0 upgrade must be handled through your dedicated support ticket. This ensures:
- Centralized tracking of all upgrade-related communications
- Proper documentation of your specific requirements and concerns
- Quick access to your project's upgrade status
- Streamlined coordination with our technical team
- Clear history of all decisions and discussions
Please use your dedicated support ticket for all upgrade-related queries and communications rather than email or other channels.
Support and Contact
For any questions or concerns about this upgrade:
- Support Portal: https://servicedesk.salsadigital.com.au
Next Steps
- Review this documentation thoroughly
- Schedule your testing period
- Begin preparing your test plans
- Contact our support team with any immediate questions
We are committed to making this upgrade process as smooth as possible and will provide support throughout the entire process.