⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 Azure → 📁 PostgreSQL Database

🛡️ Azure PostgreSQL Server is located in a less cost-effective region🟢

• Contextual name: 🛡️ Server is located in a less cost-effective region🟢
• ID: /ce/ca/azure/postgresql-database/server-cost-effective-region
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure PostgreSQL Server
  • 🔌 Azure PostgreSQL Server - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Azure PostgreSQL Database that are provisioned in Azure regions known to have higher pricing compared to nearby alternatives.

Rationale

Selecting the appropriate Azure region is essential for optimizing both cost and performance. Service pricing can vary across regions due to factors such as infrastructure expenses, energy costs, and local taxes. Deploying workloads in cost-efficient regions can result in substantial savings on monthly Azure expenditures.

Impact

Migrating workloads to different regions requires careful planning to avoid service disruptions and to ensure latency, compliance, and data sovereignty requirements continue to be met.

Audit

This policy flagged an Azure PostgreSQL Database as INCOMPLIANT if it is running in one of the following regions identified as less cost-efficient:

Region	Recommended Alternative

... see more

Remediation

Open File

Remediation

Migrate Azure Cosmos DB for PostgreSQL Server to Another Region with Read Replicas

Workflow Summary

1. Create a read replica in the target region via the Azure portal.
2. Configure firewall rules and virtual network settings for the read replica.
3. Monitor replication status to ensure data synchronization.
4. Promote the read replica to become the new primary cluster in the target region.
5. Decommission the original primary cluster in the source region.

1. Create a Read Replica in the Target Region

• In the Azure portal, navigate to the primary cluster.
• Under Cluster management, select Replicate data globally.
• Click Add replica, provide a name for the read replica, and select the target region.
• Click OK to initiate creation.

2. Configure Firewall Rules and Networking

• Manually configure firewall rules and virtual network settings on the read replica to allow application access.
• Confirm that the replica inherits admin and user accounts from the primary cluster.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Resource Optimization			23		no data