Contact your SimuTech account manager for additional resources or to setup a demo and see AWS Gateway in action.

Sign Up for a Webinar

General Resources

• Ansys Announces the Launch of Ansys Gateway
• Ansys Gateway Product Overview Page
• Ansys Gateway How To's based on Role/Engineer
• AWS Marketplace Information on Ansys Gateway
• Ansys Gateway Infographic
• Ansys Gateway Datasheet

Case Studies

• Ansys + Emirates Team New Zealand | Case Study
• Turntide Optimizes Smart Motor System Designs 7x Faster with Ansys

Technical Resources

• Overview and Prerequisites
• Documentation & Installation Instructions
• Getting Started with Ansys Gateway - YouTube Videos
• AWS Marketplace Information on Ansys Gateway 
• Ansys Gateway Architecture & Design - AWS Partner Network Blog Post

Initial configuration of Ansys Gateway will need to performed by an IT Administrator with knowledge of AWS and Active Directory and who has access to your IT environment. This guided process can take ~10-15hrs to complete. The resources below will guide you through this process.

If you need help with configuration, please Contact your account manager for more information regarding Ansys Gateway configuration services.

• Overview and Prerequisites
• Documentation & Installation Instructions
• Getting Started with Ansys Gateway - YouTube Videos
• AWS Marketplace Information on Ansys Gateway 
• Ansys Gateway Architecture & Design - AWS Partner Network Blog Post

Prerequisites

• A pre-existing AWS account.
• IT administrators familiar with AWS and Microsoft Active Directory administration.
• A secured server hosting Active Directory.  
  • This server can be hosted locally (on-premises) or in a cloud (for example, Amazon or Microsoft Azure) provided that it can reached by the AD Connector.
• A Secured Server to host the Ansys Gateway powered by AWS AD Connector service. 
  • The server can be hosted locally (on-premises) or in an Amazon Virtual Private Cloud (VPC).
• An Ansys license server with Ansys licenses, LST license server, elastic licensing, or user-based subscriptions.
• Established network connectivity between the license server and the Amazon VPC.
• To avoid latency in communication, Ansys recommends that the server hosting AD and the server hosting the AD Connector service have close physical proximity to each other.

* For up to date prerequisites, please visit the Ansys Help page - Requirements for Integrating with Ansys Gateway powered by AWS

Ansys designed Ansys Gateway to be primarily self-supported through documentation and the Ansys Learning Forum community, where you can post questions and get answers directly from Ansys.

• Self-Support Documentation
• Ansys Learning Forum

In addition to the cost of the AWS instances/storage you are running, all instances provisioned via Ansys Gateway are billed at a $/host/hr rate.  All billing and transactions related to AWS costs are between you and AWS.  Ansys and SimuTech Group are not involved with the billing of either.

For up to date pricing for Ansys Gateway and AWS Instance Pricing see:

• Ansys Gateway Pricing
• EC2 On-Demand Instance Pricing

Ansys Gateway is a stand-alone product that is purchased through the AWS Marketplace.  It is not purchased from Ansys, SimuTech, or any channel partner.

Ansys Cloud Direct is a fully managed cloud service running on Ansys's Cloud (which runs on Azure) that allows you to run your entire Ansys prep, post and simulation workflow in the cloud, where you have access to 100's of cores on demand, without having to invest in your own hardware.  When used in conjunction with Ansys Elastic Currency, Ansys Cloud Direct requires zero setup or interaction with your organization's IT department. 

Ansys Gateway also allows you to run your entire Ansys prep, post and simulation workflow in the cloud, where you have access to 100's of cores on demand, without having to invest in your own hardware but it's running on your own AWS cloud account. This allows organizations to be in full control of their data, integrate and provide access control using existing Active Directory user credentials and allows them to negotiate pricing directly with AWS.  Ansys Gateway will require your IT Department to be involved in the setup and configuration of Ansys Gateway. 

No.  Licensing is provided by your organization via either your organization's on-premises license server with BYOL (Bring-Your-Own-Licensing) or your organization's elastic licensing entitlement.

Users simply login to your Ansys Gateway Web Portal with their company credentials. These credentials are managed in your organizations local Active Directory via security groups.  From there, they can create and launch their Cloud PC and clusters.

*Ansys Account credentials may be required as part of the sign in process for each user in the future.

At this time, Yes.  The first 30 days of usage for Ansys Gateway are free.  This starts from the time you connect your first availability zone to Ansys Gateway, which occurs during configuration.  

Note - This free trial only covers the cost of Ansys Gateway and not the AWS instances and usage costs deployed using AWS Gateway. 

Please check the Ansys Gateway page in AWS Marketplace for up to date information on this policy.

Using a single 192 vCPU machine deployed independent of Ansys Gateway is an option for smaller simulations, however, there are several performance and manageability considerations you should be aware of.

• Limited number of cores/RAM
  • Single instances have limited CPU/RAM hardware configurations.
  • Ansys Gateway can easily scale up to 100's of physical cores and TB's of RAM
• 192 vCPU's = 96 Physical Cores
  • vCPU count includes hyperthreaded cores.  The 192 vCPU AWS instance (seen below) is actually dual socket 48 core CPU which has a total of 96 physical cores.  
  • Ansys Gateway can easily scale up to 100's of physical cores. 
• More cores per CPU = slower CPU clock speeds
  • The more physical cores there are on a CPU, the lower the rated base/boost clock speeds, thus lowering total performance/solve time.  A
  • Ansys Gateway solves this problem by scaling across multiple nodes, allowing you to cluster many lower core count, but faster clock rates machines together - achieving the same number of cores, but with faster clock speeds.
• More cores per CPU = increased CPU throttling
  • In addition to lower rated clock speeds, the more cores that are in use, the lower the CPU clock speeds will be under load.  More throttling occurs when each core has a lower number of watts available to it.   The relationship that best indicates this is by looking at watts/core.  The higher the watts/core, the higher the CPU will be able to boost clock speeds.
  • Ansys Gateway again solves this problem by scaling across multiple nodes, allowing you to use lower core count instances that have more watts/core.  This achieves the same number of cores, however, they will run at higher clock speeds for increased performance.
• IT will need to configure and deploy machines to users
  • Unless you can give engineers administrative access to AWS and they are familiar with how to deploy instances, they will not be able to create and deploy instances on their own.  This also poses a security risk to your AWS environment.
  • Ansys Gateway empowers users to configure and deploy machines as they need, as well as the built-in security controls to manage who has access to what resources.
• No built-in cost controls
  • AWS does not allow you to set budgets and cost controls like AWS gateway, which may lead to a large, unexpected, costs.
• No Auto-Shutdown Timers
  • AWS instances do not have the built in option to shut down automatically when not being used, which can lead to large and unexpected costs
  • With a simple checkbox, Ansys Gateway can be configured to auto-shutdown instances that sit idle after a certain time.

Recommend Ansys Gateway Instances/Hardware

• Recommended Hardware for HPC Workflows
• Recommended Hardware for VDI Workflows

• Recommended Hardware for HPC Workflows
• Recommended Hardware for VDI Workflows
• Related - How HPC and Amazon EC2 Hpc6a Instances Are Accelerating Engineering Innovation

Yes, Ansys Gateway allows users to install and integrate third-party CAD/CAE tools into their individual Windows or Linux cloud virtual machine that user's remote desktop into in order to perform their prep/pos work and submit simulations from. 

Yes.  AWS Gateway currently relies on Active Directory to function.  If your company does not have an Active Directory deployment, you will need to deploy an AD server in your AWS or local environment. 

However, Ansys is aware that customers would like an option that doesn't require AD and is considering how to eliminate this dependency to simplify the deployment process.

Not at this time.  Jobs must be submitted by connecting to your Cloud Prep/Post computer.

However, Ansys is aware of this desired workflow and is considering on how to implement this ability in future versions. 

Ansys Gateway manages costs in a few ways:

• Project space budgets - sets a maximum monthly spending amount for a project space.  Resources are shut down once the budget is utilized.
• Resource timers - automatically stops a resource after a set period of low usage, for example cpu usage under a certain percentage for a sustained period.
• AWS Reporting - Advanced users can utilize AWS Cost Explorer and Budgets tools to track and manage usage costs.

Ansys Gateway was launched and first available to customer son October 31st, 2022. 

Ansys Announces the Launch of Ansys Gateway powered by AWS

Visit - Release Notes for Ansys Gateway powered by AWS

Please see the following blog post for detailed design architecuture.

Accelerate Your Ansys Simulations with Ansys Gateway Powered by AWS | AWS Partner Network (APN) Blog (amazon.com)

There is no limit to the number of cores , RAM or nodes that you can deploy imposed by Ansys Gateway.

The largest core count cluster we have seen in use to date is a 60 node hpc6a.48xlarge (48core/384GB) cluster.  2880 cores / 22.5TB of RAM in total.