In this demonstration, we will explore how AWS FSX for NetApp on AWS's fastest growing storage solution and Cadence's logic simulator Exelium can be combined to deliver a powerful hybrid EDA cloud bursting use case. The ability to leverage the public cloud for EDA workloads has become a requirement for many semiconductor companies. 5nanometer and 3nanometer design processes require four to six times more computing power and as much as four times more storage than prior processes, placing strains on existing engineering resources, people, and licenses. The demands of new AIdriven EDA workflows make the availability of ondemand cloud scale a necessity during peak design periods. This demonstration will walk you through the experience with Cadence's Excelium and the verification IP catalog suite in an AWS cloud environment. Let's get started.We can see that the EDA tools origin volume is located in region A and the EDA tools flex cache is located in region B. And we see that the origin volume for scratch is located in region B and the flex cache volume is located in region A creating a birectional flex cache setup. We will discuss why this is important later in the demonstration. For this to be functional the origin volume and flex cache volume need to be set up in FSX for NetApp ontap file system. So let's log into the ONAP command line interface or CLI and take a look at how this is set up. In order to create a flex cache relationship between two ONTAP file systems, you must make sure that the systems are peered, which you can see they are. Next, the storage virtual machines or SVMs must then be peered. As you can see, the SVMs are peered. Now that the peering relationships are set up correctly, we can verify the flex cache volumes are available. Now that we have verified the flex cache volumes are properly set up, we can see the details of those flex cache volumes. Let's take a look at those details. Now that we have seen those details from the flex cache volumes, let's install and run cadence exelium in the tools directory in region A. With Cadence Excelium installed, we can now run the simulation job which uses IBM LSF to create AWS EC2 instances in region B to complete the simulation. By doing this, we are caching the data from region A to region B, making it closer to the compute that IBM LSF has deployed in region B. We can see that the cadence exilian job has been kicked off and running on provisioned AWS EC2 instances by IBM LSF. here we can see details regarding the data written to the scratch volume in region Audio. by logging back into the fsx for NetApp on file system in region A. We can see the NetApp flex cache volume scratch cached has increased in size as the data was written back to the cache volume from region B. The takeaways from the demonstration are you get the data where you need it when you need it there. Near limitless compute inside of AWS and accelerate your time to market with the industry-leading partnership between Cadence, NetApp, and AWS. Thank you very much.