aws-samples/amazon-fsx-workshop

A workshop for Amazon FSx - designed to help you better understand how to setup, configure, and get the best performance from an Amazon FSx file storage services (FSx for Lustre, FSx for Windows File Server, FSx for NetApp ONTAP, FSx for OpenZFS)

amazon-fsx-workshop's Issues

JP version is gone

Can you please retrieve the Japanese version? https://github.com/aws-samples/amazon-fsx-workshop/tree/master/netapp-ontap/JP
it shows 404 error.

Various Lustre workshop S3 URLs are expired

Various Lustre workshop S3 URLs are expired in the demo

Ex:

Resources:
  Vpc:
    Type: AWS::CloudFormation::Stack
    Properties:
      Parameters:
        AZ0:
          !Select [ 0, !Ref AvailabilityZones ]
        AZ1:
          !Select [ 1, !Ref AvailabilityZones ]
        VpcCidr:
          !Ref VpcCidr
      TemplateURL: https://lustre-workshop-03filesystem.s3.us-east-1.amazonaws.com/01-vpc.yaml?response-content-disposition=inline&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEOH%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJIMEYCIQCpwHgZwYILT8sxP3Y3AyqlhuOQ%2F08Y7apsZkBtgcS6zgIhAJITz0WB%2F8VnxsHjj26joG76IHSKNO%2Fwz4fkZ0yRKrW2KuUCCGoQABoMNjQ5NjYwMjQ4NTEyIgw9yRairzmgKaXFdW0qwgJL0ZYNDYhhjSqBEJoBr9PMv1Y7V%2Fp%2BW%2B84xWChw947Mytb62j%2Bi6HcCez%2B3DjQwcOc8ulmYY4NP4T2VuFPJO7WnLDOXZGaFtL16djXllZjOelMJhaHIa8H716ZFaDs6%2Fyid8tCv0IO1L5mHMfRcTLhT2kwp%2FJNkNWRXflvwudtFq5EfdfrfrExwZWMiXhGBtTH19QjRS4JN4EGSgTM3DTGHTr2fKlR8fbCTxJW14PPulZf01xUNDNUoYpVPNW8Dw6pbuOCtfy4tfsjijY0VUZmlMDGBZ3ZFA7LsE7Qf2ZRQYnmMr78Dpjc5jcL8mioyZ0G1gpGkGJuKFzX8JazEHfb77VpZ23LtdyBlO7anKkjrn5TKI4l4Rt%2Fdzjvw0tOOo8ZFx5RsrD0oEQHaV9jsosOpZIvH%2Fw0kFTLv1h68BgFhgX%2FMIbYi58GOoYC84kASEwYcjMNh69wRe7bldowY2n4UYDp7kFrbVQtBoa%2BDYsUNsO6DQYazsNNwew3RSrn29f7vUHgchvNDKTRArG05pBbaKbRwpNRC%2BwlZDWsUW9vfjRLrLH3GagvpizbAr8XjDNlImNre9aYVbHiPI0kxuvoGZ4Ae%2FjskdxRA6GaYrVvBkukBdhiByIO90BuWQkeE4Tq%2FzhlVQ6CuS%2BC8nw%2BrNe%2F8lqMnUgJ3PAEK1zlJtmgAaa3sg1oyCrjD6Dhc442QIY5P2HU3QJ%2FWXH4Iu2ai4%2BDmSYgatqO9RmXSVjhgzXGIbpru9oXlzR1KTaIHWj8XBVL3wgFWU%2BD2Y5zrn1suq4YEw%3D%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20230208T004705Z&X-Amz-SignedHeaders=host&X-Amz-Expires=28800&X-Amz-Credential=ASIAZOQWEWHAL62KOBXK%2F20230208%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=04ef69306b2261deaae6b2cb8b7dfd58b9ac1ef7c4d860f0ee0f7fbe842096c1

The script to install ior, fio, smallfile looks broken for RHEL 7.6 ami (ami-011b3ccf1bd6db744)

Errors that I got after running script-

#python ~/smallfile/smallfile_cli.py
ERROR: you must ensure that shared directory /var/tmp/smf is accessible from this host and every remote host in test

#ior
bash: ior: command not found

fio also failed to install but I fixed it using --skip-broken

Lustre on 18.04 LTS from aws

Can we get a lustre client for 18.04LTS. At this point lustre only works on 16.04 on aws - which is EOL.

[netapp-ontap] Refactor CloudFormation stacks to use native AWS::FSx::* resources

CloudFormation support now launched for FSx for ONTAP. https://aws.amazon.com/about-aws/whats-new/2021/12/amazon-fsx-netapp-ontap-aws-cloudformation/

Putting this as a placeholder to refactor the custom resources (where possible) to leverage native CFN resources for FSx.

[netapp-ontap] Issue resolving file system management endpoint hostname

When trying to SSH to the management endpoint from the Linux instance in the section 03-managing-ontap-resources - Step-by-step Guide (ONTAP CLI), the hostname resolution fails. The management IP address works when trying to SSH.
This is probably due to the VPC's DHCP options being changed to work with the AD deployment instead of the default options set. Need to make a note in the instructions to SSH using the management IP address instead of the hostname.

[[windows-file-server] deploy-od-environment Cloudformation not working now due to same failed information from CF as below, same issue happened in region east-1, west-2.

[[windows-file-server] deploy-od-environment Cloudformation not working now due to same failed information from CF as below, same issue happened in region east-1, west-2.

2022-10-22T10:50:32.077Z b480fcd2-78a7-4008-832f-f0c21f0ba38c INFO RESPONSE BODY:
{
"Status": "FAILED",
"Reason": "See the details in CloudWatch Log Stream: 2022/10/22/[$LATEST]db9059c9867b4bbfb5d28697b66aa770",
"PhysicalResourceId": "2022/10/22/[$LATEST]db9059c9867b4bbfb5d28697b66aa770",
"StackId": "arn:aws:cloudformation:us-east-1:153705321444:stack/fsx-windows-workshop/a9b09c20-51f3-11ed-94cd-0e8c5bbec55b",
"RequestId": "524bda57-9799-4322-b1dc-2659cb6a257d",
"LogicalResourceId": "LinuxAmiInfo",
"Data": {}
}

Issue CF:
https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=fsx-windows-workshop&templateURL=https://s3.amazonaws.com/amazon-fsx/workshop/windows-file-server/templates/fsx-windows-od-workshop.yaml

Elastic Tiering definition is wrong

Can you please change the definition of the Elastic Tiering type of NONE to read something like... No data movement. All data is stored in primary tier?

ActiveDirectoryFunction Node version no longer support

Lambda node12 runtime is deprecated. should be upgrade 18 or higher.

Cfn template couldn't be deployed.
Resource handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs18.x) while creating or updating functions.

DiskSpd tool not present (zip file corrupted)

Hi,

It looks like the Windows EC2 instance provisioning fails to properly download the DiskSpd tool. The zip file is there but seems to be corrupted and thus fails to uncompress. The .zip file on disk is about 20 KB, but the DiskSpd available on the internet is about ~300 KB.

In order to reproduce, launch the CloudFormation stack and connect to the Windows EC2 instance using Remote Desktop. Then go to the folder where the tool should be.

[netapp-ontap] Network credentials required to map dirve

In Section 4 of the netapp-ontap workshop, the Service Account credentials are required to map the CIFS share.

The instructions to do so are not mentioned in the section, which may be confusing. Adding an additional step to show how to retrieve the Secrets from the Secrets Manager will be helpful.