Cosmos DB account automatic failover is disabled Affecting CosmosDB (DocumentDB) service in Azure
Severity Framework
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Snyk CCSS
Rule category
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Availability/ Redundancy
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
CIS-ControlsCSA-CCMGDPRHIPAAISO-27001NIST-800-53SOC-2
- Snyk IDSNYK-CC-00521
- creditSnyk Research Team
Description
Account will experience loss of write availability for the duration of the write region outage.
How to fix?
Set properties.enableAutomaticFailover to true.
Set enable_automatic_failover attribute to true.
Example Configuration
resource "azurerm_cosmosdb_account" "allow" {
name = "tfex-cosmos-db-${random_integer.ri.result}"
location = azurerm_resource_group.example521.location
resource_group_name = azurerm_resource_group.example521.name
offer_type = "Standard"
kind = "MongoDB"
enable_automatic_failover = true
capabilities {
name = "EnableAggregationPipeline"
}
capabilities {
name = "mongoEnableDocLevelTTL"
}
capabilities {
name = "MongoDBv3.4"
}
capabilities {
name = "EnableMongo"
}
consistency_policy {
consistency_level = "BoundedStaleness"
max_interval_in_seconds = 300
max_staleness_prefix = 100000
}
geo_location {
location = "eastus"
failover_priority = 1
}
geo_location {
location = "westus"
failover_priority = 0
}
}