This Guidance helps guide you through the process of building a design data management system in the cloud using a Design Data Management (SOS) environment. This includes setting up a Design Data Management (SOS) primary server and a network file system (NFS) server. By setting up this environment, you can provide your team with global access to design data. 

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

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.

  • You can use AWS CloudFormation and AMIs to quickly launch multiple environments across multiple AWS Regions. CloudFormation allows you to build repeatable design data management workflows on AWS. AMIs allow you to install and configure the entire environment, including Design Data Management (SOS)-configured NFS servers to suite large chip design workloads.

    Read the Operational Excellence whitepaper 
  • Engineers can use Client VPN to connect to the Design Data Management (SOS) environment on AWS. Client VPN secures both terminal sessions and custom VDI sessions. Client VPN also allows users to connect to the virtual environment using a VPN connection, which encrypts users’ data and identities.

    Read the Security whitepaper 
  • This Guidance uses Amazon S3 and Amazon EBS to create a short-term and long-term backup strategy. Your data will be stored on a reliable EBS volume that syncs the design database every hour. Backups are performed to an S3 bucket when changes are committed, which is either daily or when engineering change orders (ECOs) are complete.

    Read the Reliability whitepaper 
  • The IOPS required for front-end (logical) chip design demand instance types have local attached NVMe volumes. By leveraging EC2 instances that have local NVMe volumes, you can achieve local I/O performance of 3.3M IOPS. This makes these NVMe volumes well suited for the chip design workloads that will often require millions of IOPS for front-end design.

    Read the Performance Efficiency whitepaper 
  • CloudFormation enables customer to quickly launch and tear down environments, and Amazon S3 has multiple storage tiers based on access to help reduce customer cost. Since you will only need to have the design data available in an NFS when engineering teams are working, CloudFormation helps you launch an environment only when needed. By storing design data in inexpensive S3 tiers and copying only needed data to the NFS file system, you can save on costs compared to running an operational environment and storing data 24/7.

    Read the Cost Optimization whitepaper 
  • In this Guidance, CloudFormation reduces the amount of time that resources are in production, meaning the design data and the engineering environments are only available when engineers require them to be. This results in resources only being available during working hours and being shut down overnight and during weekends.

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.


Best Practices for Deploying ClioSoft SOS on AWS

This whitepaper demonstrates the advantages of and best practices for deploying the ClioSoft SOS design data management software on the AWS Cloud platform.


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?