SWIFT Alliance Lite2 on Azure

This example is of a Cloud Network Architecture Diagram, typically used by network engineers, system architects, and IT infrastructure teams. It’s essential when designing cloud-based services, helping to visualize how different services, applications, and network components communicate in the cloud. These diagrams are useful during the planning phase of a project or when documenting an existing system for reference.

Who Typically Uses It:

1. System Architects: To design and represent the system before it is built.
2. Network Engineers: To configure networks based on the diagram.
3. Developers & Operations Teams: To understand how their components fit into the larger infrastructure.
4. Business Stakeholders: To get a high-level view of how services are connected and secured.

When & Where to Use:

1. During the Planning Phase: When you need to design the infrastructure and ensure all components interact as intended.
2. For Documentation: To ensure everyone in the organization understands the architecture.
3. Troubleshooting & Auditing: To check for misconfigurations or network issues.

In this example architecture diagram, we are looking at an enterprise-level cloud infrastructure using Azure services. This architecture diagram is designed to show a secure and scalable network infrastructure, connecting business users, back-office applications, and external services like SWIFTNet, using virtual networks, VPN, and ExpressRoute.

Components:

1. Customer Premises (Left Side): This represents the business users and back-office applications that need to connect to the cloud services. These connections are established via VPN or ExpressRoute.

2. AutoClient Subscription (Center): This is the heart of the system where two virtual networks—Hub and AutoClient Spoke—are peered.

1. Hub Virtual Network contains critical security components like the Azure Firewall and Azure Bastion.
2. Spoke Virtual Network hosts application VMs for business operations, designed with high availability (HA) in mind. Network Security Groups (NSGs) are in place for controlling access.
3. Customization Tip: If your architecture focuses on different workloads, you can modify these components or add additional layers of security to reflect your needs.

3. Alliance Connect Virtual Subscription (Right Side): This area of the diagram shows another set of virtual networks responsible for connecting to third-party services via secured routes like ExpressRoute or the Internet. SWIFTNet is used here for financial communications.

1. Customization Tip: If you're integrating external services, ensure proper routes and gateways are represented.

This diagram is an excellent starting point for designing cloud infrastructure with a focus on network security, scalability, and connectivity. You can use it as a foundation and tailor it to your specific needs using MockFlow IdeaBoard's diagramming packs and features. With drag-and-drop icons, editable networks, and custom architecture tools, IdeaBoard helps your team stay aligned and your system thoroughly documented.

Once you're ready to expand or refine your design, this diagram can be quickly adjusted, ensuring the flexibility needed for cloud environments.