Skip to main content
Last updated on
Version: 1.0.0

ePlatform Deployment on Azure Container Apps — Overview

This repository provides a repeatable, script-based deployment framework for deploying the ePlatform into an Azure Container Apps (ACA) environment.

The framework supports multiple environments and product branches using the same scripts, driven entirely by configuration.

Environment names like EQ-QA and EQ-PROD are examples only.
The scripts are environment-agnostic — configuration drives the deployment behavior.

📚 Documentation Map​

Use these documents together:

🎯 Objectives​

  • Standardize how ePlatform infrastructure is deployed
  • Make deployments reproducible and auditable
  • Minimize manual Azure Portal operations
  • Support private networking and enterprise security patterns
  • Allow incremental execution and safe recovery

📂 Deployment Scripts​

All automation scripts live in:

👉 ./scripts/

Execution order:

  1. 00_config.sh
  2. 01_rg.sh
  3. 02_storage.sh
  4. 03_keyvault.sh
  5. 04_acr.sh
  6. 05_vnet_subnets.sh
  7. 06_log_aca_env.sh
  8. 07_storage_share.sh
  9. 08a_azure_cache_for_redis.sh
  10. 08b_redis_enterprise.sh
  11. 09_mongo_vcore.sh
  12. 10_containerapps_create.sh
  13. 11_identities_and_acr_pull.sh
  14. 12_apps_update_images_envs.sh
  15. 13_appgw_create.sh
  16. 14_appgw_config_backend.sh
  17. 15_appgw_url_path_map.sh

🔒 Security Principles​

  • No secrets are committed to git
  • Secrets should be injected at runtime (pipeline or secure store)
  • Private networking by default
  • Minimal public exposure (only Application Gateway)

🌱 Meaning of BRANCH and ENV​

  • BRANCH = product line / major release / customer variant (examples: EQ, P2P, ACME)
  • ENV = environment stage (examples: DEV, QA, STAGE, PROD)

Most resource names are derived from:

<branch>-<env>

Example:

EQ + PROD  →  eq-prod
P2P + QA   →  p2p-qa

Global resources (ACR, Storage) remain explicitly configured.

Last updated on