This Guidance helps you enable trusted communication for intellectual property (IP) design and data exchange in a secure environment. It includes a high-level architecture for well-optimized design environments to facilitate collaboration with third-party companies. Third-party companies may include foundries, independent software vendors (ISVs), and outsourced design services.

Architecture Diagram

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.

  • Secure collaboration chambers allow the first-party company to work with numerous third-party companies so work can be done in parallel to achieve a faster time to market.

    Read the Operational Excellence whitepaper 
  • Collaboration on AWS allows customers to isolate design environments and separate third-party users. For example, if there is problem with an Electronic Design Automation (EDA) tool, a separate collaboration chamber is used to isolate access to only the data that is required to troubleshoot the problem with the EDA tool.

    Read the Security whitepaper 
  • Customers can launch multiple design environments for reliability and scalability. You can provide multiple teams with secure access to the data required for the entire design workflow, and resources in the environment will scale accordingly.

    Read the Reliability whitepaper 
  • Many hi-tech, electronics, and semiconductor customers have close relationships with third-party design companies and IP providers. The services in this architecture were selected to ensure collaboration across the entire workflow.  

    Read the Performance Efficiency whitepaper 
  • As you collaborate across multiple IP providers and third-party designers, you only have to launch the VPCs (or collaboration chambers) that are required to complete the design of the integrated circuit. Launching the minimum resources required can help you save on costs.

    Read the Cost Optimization whitepaper 
  • This architecture is scalable, allowing you to launch the exact number of collaboration chambers required to collaborate with third-party companies. This helps you avoid unused infrastructure and unnecessary resources. 

    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.

AWS Architecture


This post demonstrates how...


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?