[text]
This Guidance helps you build an environment in which operators and architects can create an Amazon FSx for NetApp ONTAP file system and configure the file system for multi-protocol access. This Guidance represents a workload that requires access from both Windows Desktop and Linux instances. The Linux instances read and create data that is then read by the Windows instance to load this data into an application. Amazon FSx for NetApp ONTAP offers high-performing storage with multiprotocol capabilities for simultaneous network file system (NFS) and server message block (SMB) access to the same file share, eliminating the need to duplicate data across storage services.
Please note: [Disclaimer]
Architecture Diagram
[text]
Step 1
Users invoke the AWS Lambda function for executing the Open Porous Media (OPM) Flow container using the AWS Management Console, application programming interfaces (APIs), or the AWS Command Line Interface (AWS CLI).
Step 2
The Lambda function invokes AWS Batch.
Step 3
AWS Batch starts the Amazon Elastic Container Service (Amazon ECS) flow application.
Step 4
Amazon ECS pulls containers from the registry and scales as needed through application parameters.
Step 5
NFS reads data and writes results to the Amazon FSx for NetApp ONTAP volume. SMB on Amazon WorkSpaces makes these files available for users to read.
Step 6
Written results in Amazon ECS are condensed into a single file and sent to Amazon Simple Storage Service (Amazon S3) Intelligent Tiering for long-term retention.
Step 7
WorkSpaces or Amazon Elastic Compute Cloud (Amazon EC2) Windows Instance with the ResInsight application displays results.
Step 8
AWS Managed Microsoft AD provides authentication and authorization for WorkSpaces and identity mapping for Amazon FSx for NetApp ONTAP file share.
Step 1
Users invoke the AWS Lambda function for executing the Open Porous Media (OPM) Flow container using the AWS Management Console, application programming interfaces (APIs), or the AWS Command Line Interface (AWS CLI).
Step 2
The Lambda function invokes AWS Batch.
Step 3
AWS Batch starts the Amazon Elastic Container Service (Amazon ECS) flow application.
Step 4
Amazon ECS pulls containers from the registry and scales as needed through application parameters.
Step 5
NFS reads data and writes results to the Amazon FSx for NetApp ONTAP volume. SMB on Amazon WorkSpaces makes these files available for users to read.
Step 6
Written results in Amazon ECS are condensed into a single file and sent to Amazon Simple Storage Service (Amazon S3) Intelligent Tiering for long-term retention.
Step 7
WorkSpaces or Amazon Elastic Compute Cloud (Amazon EC2) Windows Instance with the ResInsight application displays results.
Step 8
AWS Managed Microsoft AD provides authentication and authorization for WorkSpaces and identity mapping for Amazon FSx for NetApp ONTAP file share.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
AWS Batch integrates with Amazon ECS to provide autoscaling capabilities that respond to the invoked Lambda functions. These autoscaling capabilities support automated updates for the underlying containers run by AWS Batch.
-
SecurityRead the Security whitepaper
AWS Managed Microsoft AD provides an Active Directory (AD) for this Guidance. AD allows you to authenticate and authorize users with access for both WorkSpaces and the data tier shared by Amazon FSx for NetApp ONTAP through SMB. AD is commonly used as a standard for integrating multi-protocol access to files.
-
ReliabilityRead the Reliability whitepaper
Amazon FSx for NetApp ONTAP file systems are powered by two file servers in at least one Availability Zone and perform automatic synchronous replication of data for protection against failures. In the event of failure, Amazon FSx for NetApp ONTAP provides automated failover of services from one Availability Zone to another. Through these automated resiliency features, Amazon FSx for NetApp ONTAP relieves teams from having to deal with managing, operating, or updating the underlying infrastructure associated with this service.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
Amazon FSx for NetApp ONTAP allows you to scale throughput and Input/Output Operations per Second (IOPS) based on workflow requirements. This helps remove the additional time that is normally required for data copying between file services for Linux and Windows workloads.
-
Cost OptimizationRead the Cost Optimization whitepaper
Amazon FSx for NetApp ONTAP comes with a capacity pool tier, providing fully elastic storage that can scale to petabytes in size. This tier is most cost-effective for infrequently accessed data. Additionally, Amazon S3 Intelligent Tiering provides a cost-effective option for long-term retention of data. Amazon S3 Intelligent Tiering moves your data to the most cost-effective storage class based on historical usage, such as moving archival data to Amazon S3 Glacier Flexible Retrieval.
-
SustainabilityRead the Sustainability whitepaper
AWS Batch only provisions EC2 instances and containers when invoked by users to avoid actively running compute services when they’re not needed. WorkSpaces virtual desktops will sleep after pre-configured periods of inactivity. By only consuming resources when needed, these services help you reduce the overall carbon footprint of your operations.
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.
Related Content
Enhance your upstream workloads with Amazon FSx for NetApp ONTAP
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.