Each Octopus Server node stores project, environment, and deployment-related data in a shared Microsoft SQL Server Database. Since this database is shared, it’s important that the database server is also highly available. To host the Octopus SQL database in AWS, there are two options to consider:
- SQL Server on EC2 - To run SQL Server on a VM, please refer to our self-managed SQL Server guide.
- AWS RDS for SQL Server
High Availability
The database is a critical component of Octopus Deploy. If the database is lost or destroyed all your configuration will be lost with it. We highly recommend leveraging a combination of backups and SQL Server’s high availability functionality.
We recommend using Multi-AZ with RDS to ensure the resilience and availability of your Octopus database. This will ensure that your data is replicated across multiple availability zones (Multi-AZ) within your region. In the event of a failure of the primary zone, Multi-AZ automatically switches to the secondary zone. Multi-AZ supports SQL Server Database Mirroring (DBM) or Always On Availability Groups (AG), refer to to Multi-AZ deployments for Amazon RDS for Microsoft SQL Server for more details.
Disaster Recovery
Amazon provides several mechanisms for Disaster Recovery (DR) should an entire region fail. We recommend reviewing the DR solution matrix to determine which method best suits your organizations needs.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Wednesday, May 22, 2024