feat(infrastructure): update description and references for AWS/Azure infrastructure diagram

Author: stefaniuk

.github/prompts/architecture.06-infrastructure-diagram.prompt.md

@@ -1,22 +1,22 @@
 ---
 agent: agent
-description: Produce AWS infrastructure diagram from Terraform (evidence-first, consistent with C4 container naming)
+description: Produce AWS/Azure infrastructure diagram from Terraform (evidence-first, consistent with C4 container naming)
 ---
 
 **Mandatory preparation:** read [architecture overview](../instructions/includes/architecture-baseline.include.md) instructions in full and follow strictly its rules before executing any step below.
 
 ## Goal 🎯
 
-Create (or update) the [AWS infrastructure page](../../docs/architecture/aws-infrastructure.md) and [AWS infrastructure diagram](../../docs/architecture/aws-infrastructure.drawio), then export the diagram to PNG once complete.
+Create (or update) the [AWS/Azure infrastructure page](../../docs/architecture/cloud-infrastructure.md) and [AWS/Azure infrastructure diagram](../../docs/architecture/cloud-infrastructure.drawio), then export the diagram to PNG once complete.
 
 Also ensure this work is linked from: [architecture overview](../../docs/architecture/README.md) output.
 
 Constraints:
 
 - Derive every element from Terraform/IaC code (no speculation)
-- Use AWS architecture styling, icons, and colour palette as provided by the official AWS icon set packaged in Draw.io
+- Use AWS/Azure architecture styling, icons, and colour palette as provided by the official AWS/Azure icon sets packaged in Draw.io
 - Keep diagram layers/groups consistent (e.g. networking, compute, data stores)
-- Label AWS accounts/regions when known
+- Label AWS/Azure accounts/regions when known
 - Keep names consistent with the C4 Container diagram where possible (service/container names), without inventing mappings
 
 ---
@@ -33,7 +33,7 @@ Constraints:
 
 For each Terraform root/module:
 
-1. List AWS providers and aliases in use.
+1. List AWS/Azure providers and aliases in use.
 2. Capture declared resources/data sources grouped by capability:
    - Network & security (VPC, subnets, routing, security groups, Network ACLs, Load Balancers, API Gateway, WAF)
    - Compute & container (EC2, ASG, ECS, EKS, Lambda, Batch)
@@ -56,7 +56,7 @@ For each Terraform root/module:
 
 ### 1) Build the infrastructure inventory
 
-1. Create a tabular summary (working notes) of every AWS service present, including:
+1. Create a tabular summary (working notes) of every AWS/Azure service present, including:
    - Resource name/id pattern
    - Module/source file path
    - Environment/region/account (if available)
@@ -70,7 +70,7 @@ For each Terraform root/module:
 
 ### 2) Define diagram layers and grouping rules
 
-1. Use AWS architecture best practices:
+1. Use AWS/Azure architecture best practices:
    - Group resources inside VPC/availability-zone containers
    - Separate networking, compute, data, and shared services layers
    - Annotate security boundaries (public subnet, private subnet, on-prem, third-party)
@@ -79,33 +79,33 @@ For each Terraform root/module:
 
 ### 3) Create or update draw.io diagram
 
-1. Open `aws-infrastructure.drawio`.
+1. Open `cloud-infrastructure.drawio`.
 2. Reproduce the infrastructure based on Terraform evidence:
-   - Place AWS icons for each major resource (ALB, ECS Service, RDS, etc.)
+   - Place AWS/Azure icons for each major resource (ALB, ECS Service, RDS, etc.)
    - Connect components to show traffic/data direction (ingress → compute → data)
    - Annotate connections with protocols/ports if Terraform security groups or listeners provide that info
 3. Use Draw.io layers or groups to represent environments if multiple share the same page; otherwise create duplicate pages per environment.
 4. Record unresolved items in a dedicated **Unknown from code** sticky note inside the diagram (non-exporting layer) to maintain transparency.
-5. Where you can map an AWS "compute" resource to a deployable unit in the repo (from `repository-map.md` / C4 container diagram), label it accordingly and include a short evidence pointer. If you cannot map it, keep the label Terraform-derived and record **Unknown from code – map resource to deployable**.
+5. Where you can map an AWS/Azure "compute" resource to a deployable unit in the repo (from `repository-map.md` / C4 container diagram), label it accordingly and include a short evidence pointer. If you cannot map it, keep the label Terraform-derived and record **Unknown from code – map resource to deployable**.
 
 ### 4) Document evidence and outputs
 
 1. Update [architecture overview](../../docs/architecture/README.md) with:
    - Link to the draw.io file (and PNG/SVG if exported)
    - Short summary of what the diagram covers (environments, date of last refresh)
-   - Instructions to regenerate (e.g. "Open in draw.io desktop/web and refresh AWS icons from Terraform module XYZ")
-2. Add an **Evidence** section to `aws-infrastructure.md`, referencing Terraform files for each major diagram element.
+   - Instructions to regenerate (e.g. "Open in draw.io desktop/web and refresh AWS/Azure icons from Terraform module XYZ")
+2. Add an **Evidence** section to `cloud-infrastructure.md`, referencing Terraform files for each major diagram element.
 3. If automation or scripts exist for exporting diagrams, document usage (command, output path) or record **Unknown from code – locate diagram export tooling**.
 
 ---
 
 ## Diagram style requirements
 
-- Use the official AWS 2024 icon set within Draw.io (available via _Arrange → Insert → Advanced → AWS Architecture_ if not already loaded).
+- Use the official AWS/Azure 2024 icon set within Draw.io (available via _Arrange → Insert → Advanced → AWS/Azure Architecture_ if not already loaded).
 - Maintain consistent sizing and spacing; align elements using Draw.io guides.
 - Label subnets, route tables, and security zones directly on the canvas.
 - Use muted background colours for groups (VPC, AZ) to keep icons readable.
-- For external systems or SaaS providers not in AWS, use generic grey boxes with clear labels.
+- For external systems or SaaS providers not in AWS/Azure, use generic grey boxes with clear labels.
 
 ### Mandatory naming and labelling conventions
 
@@ -114,7 +114,7 @@ Every infrastructure diagram must follow these naming rules verbatim (update exi
 1. **Resource nodes:** Use lowercase kebab-case `{service}-{role}-{scope}`, e.g. `alb-public-edge`, `ecs-task-api`, `rds-primary-app`. Names must map to Terraform modules, resource blocks, or tags so reviewers can trace them back.
 2. **Environment overlays:** Prefix or suffix with the environment name when multiple environments appear on the same page, e.g. `vpc-app-prod`, `ecs-service-orders-stg`.
 3. **Subnet and security groups:** Name subnets and zones as `{visibility}-subnet-{az}` (`public-subnet-a`, `private-subnet-b`) and security zones as `{zone}-security-zone`.
-4. **Accounts and regions:** Label AWS accounts with friendly name plus account ID (`acct-core (123456789012)`) and regions as `region-<code>` (`region-eu-west-2`). Place these labels on grouping containers.
+4. **Accounts and regions:** Label AWS/Azure accounts with friendly name plus account ID (`acct-core (123456789012)`) and regions as `region-<code>` (`region-eu-west-2`). Place these labels on grouping containers.
 5. **Arrow titles:** Label every arrow with `{protocol}/{port}` or `{action}` (e.g. `HTTPS/443`, `Publish events`, `Read replicas`). If both apply, prefer `HTTPS/443 – public ingress`.
 6. **Legend:** Include a small legend per diagram page describing arrow colours, border styles, and environment colouring (e.g. "orange arrows = ingress traffic", "blue arrows = data writes").
 7. **Unknowns:** Any placeholder or dotted element must be suffixed with `-pending` and accompanied by an **Unknown from code** sticky note referencing the missing evidence.
@@ -123,7 +123,7 @@ Every infrastructure diagram must follow these naming rules verbatim (update exi
 
 ## Quality gates
 
-1. Validate the Draw.io file opens without errors (use the Draw.io desktop/web validator) and retains AWS icon library references.
+1. Validate the Draw.io file opens without errors (use the Draw.io desktop/web validator) and retains AWS/Azure icon library references.
 2. If a PNG/SVG export is stored, ensure it updates after modifications.
 3. Confirm Terraform formatting via `terraform fmt -check` in any touched directories when the prompt automation makes code changes (if part of its workflow).
 4. Ensure README links render correctly in Markdown (relative paths).
@@ -144,7 +144,7 @@ For every logical cluster (networking, compute, data, integration):
 Example evidence snippet:
 
 ```markdown
-### AWS Infrastructure
+### Cloud Infrastructure
 
 ## Diagram
 
@@ -162,5 +162,5 @@ Example evidence snippet:
 
 ---
 
-> **Version**: 1.1.3
-> **Last Amended**: 2026-01-17
+> **Version**: 1.1.4
+> **Last Amended**: 2026-02-19