Command line call for CloudFormation in "Quick Start - EKS" is not working properly

[ezimele-aws]

Running the 'main' branch command line results in errors:

# Deploy complete EKS-based HyperPod infrastructure
aws cloudformation create-stack \
--stack-name hyperpod-eks-main-stack \
--template-url https://aws-sagemaker-hyperpod-cluster-setup-us-west-2-prod.s3.us-west-2.amazonaws.com/templates/main-stack-eks-based-template.yaml \
--parameters ParameterKey=ResourceNamePrefix,ParameterValue=my-hyperpod \
ParameterKey=AvailabilityZoneIds,ParameterValue="usw2-az1,usw2-az2" \
ParameterKey=HyperPodClusterName,ParameterValue=ml-cluster \
--capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM

Parameter validation failed:
Invalid type for parameter Parameters[1].ParameterValue, value: ['usw2-az1', 'usw2-az2'], type: <class 'list'>, valid types: <class 'str'>

If fixed through this new cli call:

 aws cloudformation create-stack \
  --stack-name hyperpod-eks-main-stack \
  --template-url https://aws-sagemaker-hyperpod-cluster-setup-us-west-2-prod.s3.us-west-2.amazonaws.com/templates/main-stack-eks-based-template.yaml \
  --parameters \
    ParameterKey=ResourceNamePrefix,ParameterValue=my-hyperpod \
    ParameterKey=AvailabilityZoneIds,ParameterValue=\"usw2-az1,usw2-az2\" \
    ParameterKey=HyperPodClusterName,ParameterValue=ml-cluster \
  --capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM


An error occurred (InsufficientCapabilitiesException) when calling the CreateStack operation: Requires capabilities : [CAPABILITY_AUTO_EXPAND]

Adding up, it also sets an cloudformation error of existing bucket name, specifically the AccessLogsBucket that has value as (line 2120 to 2129 in main stack):

[...]
        BucketName:
          Fn::If:
            - CreateS3BucketStackCondition
            - Fn::GetAtt:
                - S3BucketStack
                - Outputs.S3LogsBucketName
            - Fn::Sub:AccessLogs
                - ${ResourceNamePrefix}-logs
                - ResourceNamePrefix:
                    Ref: ResourceNamePrefix
[...]

I'll working on a fix in my forked repo, will get back with PR, generating issue to track in branch