Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make pClientAmiId parameter optional as per the docs #29

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vlas-sokolov
Copy link

The docs suggest that two subnet parameters and one VPC are enough for the quick start of the template. However, when I create a stack from cloudhsm.yml template file, with the following parameters:

[
  {
    "ParameterKey": "pSubnets",
    "ParameterValue": "subnet-00000000000000000"
  },
  {
    "ParameterKey": "pClientVpcId",
    "ParameterValue": "vpc-00000000000000000"
  },
  {
    "ParameterKey": "pClientSubnet",
    "ParameterValue": "subnet-00000000000000000"
  }
]

, I'm getting the following error An error occurred (ValidationError) when calling the CreateStack operation: Parameters: [pClientAmiId] must have values. It appears that the pClientAmiId is the only parameter that is marked as optional but doesn't get its own default value. This PR adds it to be a blank string as line 147 seems to require. I deployed the stack afterwards and it seems to proceed normally for a while (for proper deployment I did have to set a pClientAmiId value but that's because the region I use doesn't have t3a instance family so I had to set manual values for type and ami).

@vlas-sokolov
Copy link
Author

Maybe should add that the stack deployment command I used was
aws cloudformation create-stack --template-url https://some-private-bucket-uri/cloudhsm.yml --stack-name CloudHSMStack --parameters file://cfn_params.json --capabilities CAPABILITY_NAMED_IAM, where cfn_params.json file contents were the parameters I pasted in the first message.

@Roedy13
Copy link

Roedy13 commented Feb 16, 2024

+1 on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants