Periodic update - 01/06/23-07:09am PST

Author: Kari Stromsland

doc_source/HeadNode-v3.md

@@ -66,7 +66,7 @@ HeadNode:
 Specifies the instance type for the head node\.  
 Specifies the Amazon EC2 instance type that's used for the head node\. The architecture of the instance type must be the same as the architecture used for the AWS Batch [`InstanceType`](Scheduling-v3.md#yaml-Scheduling-AwsBatchQueues-ComputeResources-InstanceTypes) or Slurm [`InstanceType`](Scheduling-v3.md#yaml-Scheduling-SlurmQueues-ComputeResources-InstanceType) setting\.  
 AWS ParallelCluster doesn't support the following instance types for the `HeadNode` setting\.  
-
++ hpc6id
 If you define a p4d instance type or another instance type that has multiple network interfaces or a network interface card, you must set [`ElasticIp`](#yaml-HeadNode-Networking-ElasticIp) to `true` to provide public access\. AWS public IPs can only be assigned to instances launched with a single network interface\. For this case, we recommend that you use a [NAT gateway](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html) to provide public access to the cluster compute nodes\. For more information, see [Assign a public IPv4 address during instance launch](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#public-ip-addresses) in the *Amazon EC2 User Guide for Linux Instances*\.  
 [Update policy: If this setting is changed, the update is not allowed.](using-pcluster-update-cluster-v3.md#update-policy-fail-v3)
 
@@ -449,4 +449,4 @@ For example, if a custom AMI has an encrypted snapshot associated with it, the f
   }
 ```
 To troubleshoot custom AMI validation warnings, see [Troubleshooting custom AMI issues](troubleshooting-v3.md#troubleshooting-v3-custom-amis)\.  
-[Update policy: If this setting is changed, the update is not allowed.](using-pcluster-update-cluster-v3.md#update-policy-fail-v3)
+[Update policy: If this setting is changed, the update is not allowed.](using-pcluster-update-cluster-v3.md#update-policy-fail-v3)

doc_source/network-configuration-v3.md

@@ -305,4 +305,4 @@ Scheduling:
   1. Connect over DCV to the proxy EC2 instance\.
 
   1. Use the `pcluster dcv-connect` command on the proxy instance to connect to the cluster inside the subnet without internet access\.
-+ *Interacting with other AWS services:* Only services strictly required by AWS ParallelCluster are listed above\. If your cluster must interact with other services, create the corresponding VPC endpoints\.
++ *Interacting with other AWS services:* Only services strictly required by AWS ParallelCluster are listed above\. If your cluster must interact with other services, create the corresponding VPC endpoints\.

doc_source/security-compliance-validation.md

@@ -8,7 +8,7 @@ You can download third\-party audit reports using the AWS Artifact\. For more in
 
 Your compliance responsibility when using AWS ParallelCluster is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations\. AWS provides the following resources to help with compliance:
 + [Security and compliance quick start guides](http://aws.amazon.com/quickstart/?awsf.quickstart-homepage-filter=categories%23security-identity-compliance) – These deployment guides discuss architectural considerations and provide steps for deploying security\- and compliance\-focused baseline environments on AWS\.
-+ [Architecting for HIPAA security and compliance whitepaper ](https://d0.awsstatic.com/whitepapers/compliance/AWS_HIPAA_Compliance_Whitepaper.pdf) – This whitepaper describes how companies can use AWS to create HIPAA\-compliant applications\.
++ [Architecting for HIPAA security and Compliance on Amazon Web Services AWS Whitepaper ](https://docs.aws.amazon.com/pdfs/whitepapers/latest/architecting-hipaa-security-and-compliance-on-aws/architecting-hipaa-security-and-compliance-on-aws.pdf) – This whitepaper describes how companies can use AWS to create HIPAA\-compliant applications\.
 + [AWS compliance resources](http://aws.amazon.com/compliance/resources/) – This collection of workbooks and guides might apply to your industry and location\.
 + [Evaluating resources with rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *AWS Config Developer Guide* – The AWS Config service assesses how well your resource configurations comply with internal practices, industry guidelines, and regulations\.
 + [AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html) – This AWS service provides a comprehensive view of your security state within AWS that helps you check your compliance with security industry standards and best practices\.

doc_source/slurm-workload-manager-v3.md

@@ -5,7 +5,7 @@ For information about Slurm, see [https://slurm\.schedmd\.com](https://slurm.sch
 
 | AWS ParallelCluster version\(s\) | Supported Slurm version | 
 | --- | --- | 
-|  3\.4\.0  |  22\.05\.6  | 
+|  3\.4\.0  |  22\.05\.7  | 
 |  3\.3\.0  |  22\.05\.5  | 
 |  3\.1\.4, 3\.1\.5, 3\.2\.0, 3\.2\.1  |  21\.08\.8\-2  | 
 |  3\.1\.2, 3\.1\.3  |  21\.08\.6  | 

doc_source/tutorials_05_multi-user-ad.md

@@ -11,6 +11,12 @@ After you create these resources, proceed to configure and create your cluster i
 
 This tutorial covers how to create an environment that supports multiple user access to clusters\. This tutorial doesn't cover how you create and use an AWS Directory Service AD\. The steps that you take to set up an AWS Managed Microsoft AD in this tutorial are provided for testing purposes only\. They *aren't* provided to replace the official documentation and best practices you can find at [AWS Managed Microsoft AD](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/directory_microsoft_ad.html) and [Simple AD](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/directory_simple_ad.html) in the *AWS Directory Service Administration Guide*\.
 
+**Note**  
+Directory user passwords expire according to the directory password policy property definitions\. For more information see [Supported policy settings](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/supportedpolicysettings)\. To reset directory passwords with AWS ParallelCluster, see [How to reset a user password and expired passwords](troubleshooting-v3.md#troubleshooting-v3-multi-user-reset-passwd)\.
+
+**Note**  
+The directory domain controller IP addresses can change due to domain controller changes and directory maintenance\. If you chose the automated quick create method to create the directory infrastructure, you must manually align the load balancer in front of the directory controllers when the directory IP addresses change\. If you use the quick create method, the directory IP addresses aren't automatically aligned with the load balancers\.
+
 **Prerequisites**
 + AWS ParallelCluster [is installed](install-v3-parallelcluster.md)\.
 + The AWS CLI [is installed and configured\.](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)