[SEO Subhead]
This Guidance demonstrates how the Virtual Engineering Workbench (VEW) framework accelerates software development lifecycles and supports software-defined vehicles. VEW automates, virtualizes, and orchestrates processes to support the software development lifecycle, enabling original equipment manufacturers (OEMs) to reduce feedback cycle times. Using VEW, this Guidance implements automated testing, validation, and development processes, significantly reducing feature cycle time and increasing new feature throughput while maintaining consistent development environments.
Note: [Disclaimer]
Architecture Diagram
[Architecture diagram description]
Step 1
Connect to the VEW frontend through Amazon CloudFront backed by Amazon Simple Storage Service (Amazon S3), and select the workbench and virtual targets with which you’ll work. Manage user authentication with Amazon Cognito and secure access with AWS WAF.
Step 2
Amazon API Gateway and AWS Lambda handle frontend requests and trigger workbench and virtual target provisioning through Amazon EventBridge and AWS Step Functions. Store product metadata in Amazon DynamoDB.
Step 3
VEW manages its products (digital toolchains and virtual targets) in AWS Service Catalog. Store product dependencies like binaries or libraries in Amazon S3, and handle events using EventBridge, Amazon Simple Notification Service (Amazon SNS), and Lambda.
Step 4
VEW deploys workbenches and virtual targets as Amazon Elastic Compute Cloud (Amazon EC2) instances into product accounts using Service Catalog, from which they can be accessed by the user through Amazon DCV, remote desktop protocol (RDP), or SSH.
Step 5
Deploy a fully automated VEW product lifecycle pipeline using Amazon EC2 ImageBuilder, creating Amazon EC2 AMIs and storing assets on Amazon S3.
Step 6
With AWS Direct Connect, VEW can be integrated with customers’ corporate resources like identity providers, license servers, or code repositories.
Step 1
Connect to the VEW frontend through Amazon CloudFront backed by Amazon Simple Storage Service (Amazon S3), and select the workbench and virtual targets with which you’ll work. Manage user authentication with Amazon Cognito and secure access with AWS WAF.
Step 2
Amazon API Gateway and AWS Lambda handle frontend requests and trigger workbench and virtual target provisioning through Amazon EventBridge and AWS Step Functions. Store product metadata in Amazon DynamoDB.
Step 3
VEW manages its products (digital toolchains and virtual targets) in AWS Service Catalog. Store product dependencies like binaries or libraries in Amazon S3, and handle events using EventBridge, Amazon Simple Notification Service (Amazon SNS), and Lambda.
Step 4
VEW deploys workbenches and virtual targets as Amazon Elastic Compute Cloud (Amazon EC2) instances into product accounts using Service Catalog, from which they can be accessed by the user through Amazon DCV, remote desktop protocol (RDP), or SSH.
Step 5
Deploy a fully automated VEW product lifecycle pipeline using Amazon EC2 ImageBuilder, creating Amazon EC2 AMIs and storing assets on Amazon S3.
Step 6
With AWS Direct Connect, VEW can be integrated with customers’ corporate resources like identity providers, license servers, or code repositories.
Get Started
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
With Lambda, you can focus on building business logic while AWS manages the underlying infrastructure. Integrate API Gateway and EventBridge to create loosely coupled, event-driven architectures that are highly reliable. Amazon CloudWatch monitors, observes, and gains insights into your applications and services.
-
SecurityRead the Security whitepaper
Amazon Cognito enhances security through robust user authentication, authorization, and identity management. AWS WAF protects your applications from common web exploits and malicious traffic. Amazon CloudWatch monitors and logs security-related events, enabling threat detection and analysis.
-
ReliabilityRead the Reliability whitepaper
Achieve fault tolerance, automatic scaling, and robust event processing with Amazon EC2, EventBridge, and API Gateway. EC2 instances can be distributed across multiple Availability Zones and Regions, helping ensure high availability through failover strategies. EventBridge offers improved failure recovery with dead-letter queues and custom retry policies, while API Gateway minimizes infrastructure failure risks.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
CloudFront accelerates content delivery through its global edge network. Amazon EC2 offers scalable compute resources on-demand. Direct Connect provides dedicated, low-latency connectivity to AWS. Lambda@Edge enables real-time processing at the edge, reducing latency. These services address key aspects of application delivery and processing, including content caching, compute scaling, reliable connectivity, and dynamic edge processing, creating a robust infrastructure for delivering high-performance applications and content globally.
-
Cost OptimizationRead the Cost Optimization whitepaper
Analyze monthly spending, define budgets, and identify cost outliers with AWS Cost Explorer. Cost Explorer provides right-sizing recommendations to optimize your compute instances and improve cost transparency.
-
SustainabilityRead the Sustainability whitepaper
AWS Graviton instances use energy-efficient ARM-based processors, which help you increase your energy-to-compute power ratio. Provision EC2 instances on-demand to replace underutilized infrastructure and improve resource utilization. Implement serverless architectures with Lambda to minimize idle resources and reduce your environmental footprint.
Related Content
[Title]
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.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.