Azure Database SQL Failover Group

This page shows how to write Terraform for Database SQL Failover Group and write them securely.

azurerm_sql_failover_group (Terraform)

The SQL Failover Group in Database can be configured in Terraform with the resource name azurerm_sql_failover_group. The following sections describe 10 examples of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L1
resource "azurerm_sql_failover_group" "terraformsqlFailover" {
  name                = var.sqlFailover_Name
  resource_group_name = var.sqlFailover_RG_Name
  server_name         = var.sqlFailover_Primary_Server
  databases           = [var.sqlFailover_DB_ID]
  tags                = var.sqlFailover_Tag
failovergroup.tf#L1
resource "azurerm_sql_failover_group" "sql_failover_group" {
    name                = format("sqlfailovergroup-%s-%s", var.environment,var.application_name)
    resource_group_name = azurerm_resource_group.rg_subscription_bzunit_env_region["pri"].name
    server_name         = azurerm_sql_server.sql_subscription_bzunit_env_region["pri"].name
    databases           = [azurerm_sql_database.sql-database["pri"].id]
    partner_servers {
failover_group.tf#L11
resource "azurerm_sql_failover_group" "failover_group" {
  name                = azurecaf_name.failover_group.result
  resource_group_name = var.resource_group_name
  server_name         = var.primary_server_name
  databases           = local.databases

failover_group.tf#L11
resource "azurerm_sql_failover_group" "failover_group" {
  name                = azurecaf_name.failover_group.result
  resource_group_name = var.resource_group_name
  server_name         = var.primary_server_name
  databases           = local.databases

failover_group.tf#L11
resource "azurerm_sql_failover_group" "failover_group" {
  name                = azurecaf_name.failover_group.result
  resource_group_name = var.resource_group_name
  server_name         = var.primary_server_name
  databases           = local.databases

main.tf#L25
resource "azurerm_sql_failover_group" "failoverpolicy" {
  name                = "sql-database-failover123"
  resource_group_name = var.resource_group
  server_name         = azurerm_sql_server.primary.name
  databases           = [azurerm_sql_database.db1.id]
  partner_servers {
main.tf#L42
resource "azurerm_sql_failover_group" "example" {
  name                = "sqlpoc-failover-group"
  resource_group_name = azurerm_sql_server.primary.resource_group_name
  server_name         = azurerm_sql_server.primary.name
  databases           = [azurerm_sql_database.db1.id]
  partner_servers {
failover_group.tf#L11
resource "azurerm_sql_failover_group" "failover_group" {
  name                = azurecaf_name.failover_group.result
  resource_group_name = var.resource_group_name
  server_name         = var.primary_server_name
  databases           = local.databases

main.tf#L7
resource "azurerm_sql_failover_group" "this" {
  databases           = var.databases
  name                = var.name
  resource_group_name = var.resource_group_name
  server_name         = var.server_name
  tags                = var.tags
main.tf#L7
resource "azurerm_sql_failover_group" "this" {
  databases           = var.databases
  name                = var.name
  resource_group_name = var.resource_group_name
  server_name         = var.server_name
  tags                = var.tags

Review your Terraform file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

Explanation in Terraform Registry

Create a failover group of databases on a collection of Azure SQL servers.

Tips: Best Practices for The Other Azure Database Resources

In addition to the azurerm_mariadb_firewall_rule, Azure Database has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

risk-label

azurerm_mariadb_firewall_rule

Ensure database firewalls do not permit public access

It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.

risk-label

azurerm_mariadb_server

Ensure that access to Azure SQL Database is restricted

It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.

risk-label

azurerm_mssql_database_extended_auditing_policy

Ensure to configure retention periods of database auditing to enough duration

It is better to configure retention periods of database auditing to enough duration. It would be better to set greater than at least 90 days.

risk-label

azurerm_mssql_server

Ensure to enable auditing on Azure SQL databases

It is better to enable auditing on Azure SQL databases. It helps you maintain regulatory compliance, monitor the activities indicating unexpected incidents or suspected security violations.

risk-label

azurerm_mssql_server_security_alert_policy

Ensure to configure at least one email address for threat alerts

It is better to configure at least one email address for threat alerts. SQL Server is able to send alerts for threat detection via emails and it could support us to notice the incident on time.

risk-label

azurerm_mysql_firewall_rule

Ensure database firewalls do not permit public access

It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.

risk-label

azurerm_mysql_server

Ensure to disable public access to database

It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.

risk-label

azurerm_postgresql_firewall_rule

Ensure database firewalls do not permit public access

It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.

risk-label

azurerm_postgresql_server

Ensure to disable public access to database

It is better to disable public access to the database to avoid unwilling communications with unknown services if not required.

risk-label

azurerm_sql_firewall_rule

Ensure database firewalls do not permit public access

It is better to restrict IP address ranges that can access the database by firewall rules. If both start_ip_address and end_ip_address are set to 0.0.0.0, it blocks connections from the Internet and accepts connections from all Azure datacenter IP addresses.

risk-label

azurerm_sql_server

Ensure to enable auditing on Azure SQL databases

It is better to enable auditing on Azure SQL databases. It helps you maintain regulatory compliance, monitor the activities indicating unexpected incidents or suspected security violations.

Review your Azure Database settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

Azure Resource Manager Example

Azure Resource Manager code does not have the related resource.

Frequently asked questions

What is Azure Database SQL Failover Group?

Azure Database SQL Failover Group is a resource for Database of Microsoft Azure. Settings can be wrote in Terraform.

Where can I find the example code for the Azure Database SQL Failover Group?

For Terraform, the OT-terraform-azure-modules/terraform-SqlFailover, vjavle/drdemo and anmoltoppo/Terraform source code examples are useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.