AWS Microfrontend Portal - Multi-AZ Architecture

AWSArchitectureadvanced
AWS Microfrontend Portal - Multi-AZ Architecture — AWS architecture diagram

About This Architecture

Multi-AZ microfrontend portal architecture leveraging AWS Route 53, CloudFront CDN, WAF, and Shield for global distribution and DDoS protection. MFE Shell App runs on ECS Fargate across two availability zones with dedicated ALBs, while 11 specialized microfrontends (Login, Dashboard, Policy Tracker, Commission Data, Quote Mgmt, RMD Policies, and others) are independently deployed and versioned in ECR. Backend services scale via Lambda-based BFFs (Policy, User, Commission, Document, Notification) orchestrated by Step Functions, with RDS Aurora Multi-AZ primary-standby, DynamoDB Global Tables, ElastiCache Redis replication, and async messaging through SQS and SNS. Cognito handles authentication, Secrets Manager and KMS secure credentials, and CloudWatch, X-Ray, CloudTrail provide observability across both AZ-1 and AZ-2. Fork this diagram to customize for your PAS integrations (LifePro, FAST, Life 70), billing systems, and document management backends.

People also ask

How do I architect a highly available microfrontend portal on AWS across multiple availability zones?

This diagram shows a production-grade multi-AZ microfrontend portal using ECS Fargate for the MFE Shell App, 11 independent microfrontends in ECR, and Lambda-based BFFs for Policy, User, Commission, Document, and Notification services. RDS Aurora Multi-AZ with primary-standby, DynamoDB Global Tables, and ElastiCache Redis replicas ensure data consistency and failover across AZ-1 and AZ-2, while Cl

AWSmicrofrontendmulti-AZECS FargateLambdaRDS Aurora
Domain:
Cloud Aws
Audience:
AWS solutions architects designing multi-tenant, multi-AZ microfrontend portals

Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.

Generate your own architecture diagram →

About This Architecture

Multi-AZ microfrontend portal architecture leveraging AWS Route 53, CloudFront CDN, WAF, and Shield for global distribution and DDoS protection. MFE Shell App runs on ECS Fargate across two availability zones with dedicated ALBs, while 11 specialized microfrontends (Login, Dashboard, Policy Tracker, Commission Data, Quote Mgmt, RMD Policies, and others) are independently deployed and versioned in ECR. Backend services scale via Lambda-based BFFs (Policy, User, Commission, Document, Notification) orchestrated by Step Functions, with RDS Aurora Multi-AZ primary-standby, DynamoDB Global Tables, ElastiCache Redis replication, and async messaging through SQS and SNS. Cognito handles authentication, Secrets Manager and KMS secure credentials, and CloudWatch, X-Ray, CloudTrail provide observability across both AZ-1 and AZ-2. Fork this diagram to customize for your PAS integrations (LifePro, FAST, Life 70), billing systems, and document management backends.

People also ask

How do I architect a highly available microfrontend portal on AWS across multiple availability zones?

This diagram shows a production-grade multi-AZ microfrontend portal using ECS Fargate for the MFE Shell App, 11 independent microfrontends in ECR, and Lambda-based BFFs for Policy, User, Commission, Document, and Notification services. RDS Aurora Multi-AZ with primary-standby, DynamoDB Global Tables, and ElastiCache Redis replicas ensure data consistency and failover across AZ-1 and AZ-2, while Cl

AWS Microfrontend Portal - Multi-AZ Architecture

AWSadvancedmicrofrontendmulti-AZECS FargateLambdaRDS Aurora
Domain: Cloud AwsAudience: AWS solutions architects designing multi-tenant, multi-AZ microfrontend portals
0 views0 favoritesPublic

Created by

May 8, 2026

Updated

May 8, 2026 at 12:06 PM

Type

architecture

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI