Sean Smith
Sean Smith
Thanks for pointing out this issue, we'll fix it asap. Until then you can add a line to the very bottom indented to the same level as DataCompressionType: ```bash PerUnitStorageThroughput...
This should work, I have a `3.0.0`, `3.0.3` and `3.1.1` stack running simultaneously.
ah you mean update the existing stack. One of the issues here is when you update you lose the ability to interact with existing prior version clusters. Ideally you'd have...
Would be curious to hear your thoughts on this
Hi Stephen another workaround until we fix the issue is to add the `AmazonS3ReadOnlyAccess` managed policy to the cluster, this is what we do in the weather workshop. It's allowed...
Closing this in favor of next pcluster release
A few notes here: * There's no way to specify the user to connect as when you run `SessionManagerRunShell` - the default is ssm-user * There's also no way to...
This is also true for clusters created within pcluster manager.
To elaborate - this is caused by the ParallelCluster API, it limits the IAM policies you can attach to the instances to the following list: ```json { "Condition": { "ArnLike":...
I should add, if you want to scope this down to just `iam:AttachRolePolicy` and `iam:DetachRolePolicy` you can add a policy like: ```json { "Version": "2012-10-17", "Statement": [ { "Action": [...