This Guidance demonstrates how teams of engineers, scientists, and researchers with a cloud environment can host licensed engineering tools required for comprehensive product development workloads. It shows how, in a matter of hours, engineering application teams can deploy scalable engineering collaboration chambers customized to meet organizational security requirements for joint development with trusted suppliers. With this Guidance, engineers can interact with a familiar catalog of tools, seamlessly integrated into an intuitive web portal.

Note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Get Started

Deploy this Guidance

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.

  • OpenSearch Service automatically ingests and retains critical cluster and job metadata, enabling long-term data analysis and business recommendations. Amazon CloudWatch monitors HPC and visualization node metrics in near real-time, empowering the detection of anomalies and optimization of system performance. Visualization of job information, including runtime, license utilization, pricing, and resource allocation, optimizes compute infrastructure.

    Read the Operational Excellence whitepaper 

  • Scoped IAM policies help ensure minimum required permissions for a secure environment. Multiple Amazon EC2 security groups limit network traffic and enhance protection. Sensitive information, such as HTTPS certificates and directory service credentials, is securely stored in ACM and Secrets Manager, respectively. If single sign-on (SSO) is enabled, SAML authentication is offloaded to Amazon Cognito, providing a secure and scalable authentication solution.

    Read the Security whitepaper 

  • ELB distributes traffic across multiple Availability Zones, enhancing the reliability of HPC and virtual desktop infrastructure (VDI) workloads. Deployment of the virtual private clouds (VPCs) with multiple subnets provides high availability and access to Amazon EC2 capacity, mitigating the risk of capacity constraints that could impact tightly coupled jobs.

    Read the Reliability whitepaper 

  • Optimal AWS infrastructure, including compute, storage, and networking, accommodates the unique performance requirements of computer-aided engineering (CAE) simulations. Elastic Fabric Adapter (EFA) optimizes inter-node latency communication for large-scale HPC workloads. High-performance or parallel file systems, such as Amazon FSx for Lustre, handle I/O-intensive workloads. Leveraging the high-performance remote display protocol of Amazon DCV helps you optimize existing experience with graphically intensive workloads, such as CAD.

    Read the Performance Efficiency whitepaper 

  • AWS Budgets provides guardrails to prevent over-provisioning of compute and storage resources beyond the allocated budget threshold. This service is tightly integrated with HPC job submission queues, so that allocated budget per queue or project cannot exceed customer-defined thresholds. AWS cost allocation tags provide administrators with visibility into current spend at the project, team, user, or service level to help ensure accurate accounting across AWS resources.

    Read the Cost Optimization whitepaper 

  • Amazon EFS automatically transitions infrequent access data to a lower storage tier, reducing your system footprint and associated costs. EC2 Auto Scaling Groups replace persistent EC2 instances, minimizing wasted compute. Additionally, the breadth of Amazon EC2 compute options allows you to optimize per application, further reducing your carbon footprint.

    Read the Sustainability whitepaper 

Related Content

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.

Was this page helpful?

 Feedback