Skip to main content

AWS Solutions Library

Guidance for Model-Based Design Environment (MBDE) on AWS

Overview

This Guidance shows how you can streamline and accelerate product development by building an MBDE for engineering and design. Using AWS as the foundation, you can create a modern cloud computing platform that is more secure, agile, and lightweight than on-premises document-based engineering environments. You can also use MBDE-generated models and data to build advanced analytics and generative models for predicting system behavior. The MBDE approach centralizes management of your tools, helping you identify product development risks early, improve overall development performance, and streamline collaboration with stakeholders. 

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

This Guidance uses CloudFormation to deploy engineering resources through RES so you can build a centralized design environment. It models a collection of resources as a single unit, so you don’t have to manage resources individually. Additionally, AppStream 2.0 launches a fresh virtual desktop upon user login for consistent application settings and storage connections, and you can use WorkSpaces to centrally manage your persistent cloud desktops.

Read the Operational Excellence whitepaper 

This Guidance uses AWS Identity and Access Managementfor fine-grained permissions and role-based access. AWS Key Management Service (AWS KMS)  gives you centralized control over the cryptographic keys used to protect your data.

Read the Security whitepaper 

This Guidance uses managed services for compute needs such as Lambda, Step Functions, and AWS Glue crawlers. These services support fault tolerance by automatically detecting and replacing unhealthy compute instances and scaling as the workload demand grows. Similarly, this Guidance also uses managed services for storage such as Amazon S3, Neptune, OpenSearch Service, and DynamoDB, which are designed to be highly reliable, available, and durable for mission critical workloads. These services offer multi-Availability Zone (AZ) deployment, read replicas, minimal downtime for software updates and upgrades, fault-tolerant storage, and continuous and incremental backups for point-in-time recovery.

Read the Reliability whitepaper 

This Guidance uses EventBridge to build event-driven architectures and create point-to-point integrations without writing custom code or managing servers. You can use Step Functions to automate processes and orchestrate microservices and AWS IoT TwinMaker to create digital twins of real-world systems without needing to re-ingest or move data. Finally, Amazon SQS provides capacity planning and infrastructure maintenance.

Read the Performance Efficiency whitepaper 

With Lambda, you pay only for requests served and the compute time required to run your code. AppStream 2.0 lets you pay only for the desktop-as-a-service (DaaS) resources that you provision, plus a small monthly fee per end user, depending on the operating system. The fees for WorkSpaces include both infrastructure and the software applications listed in the bundle.

Read the Cost Optimization whitepaper 

DynamoDB automatically scales tables to reduce resource usage, and Amazon S3 supports sustainability through optimized access patterns and storage tiers. Tiered storage allows you to store data based on how frequently you need to access it. For example, archived data will require fewer storage resources, which helps you minimize your workload's overall environmental impact.

Read the Sustainability whitepaper 

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.