Skip to content
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.

Add HeadNode:Iam:S3Access option to the wizard #269

Open
stephenmsachs opened this issue Aug 22, 2022 · 4 comments
Open

Add HeadNode:Iam:S3Access option to the wizard #269

stephenmsachs opened this issue Aug 22, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@stephenmsachs
Copy link
Contributor

While HeadNode:CustomActions:OnNodeStart:Script can be pointed to an s3 location in the wizard, there is currently no mechanism to add the pre-requisite HeadNode:Iam:S3Access. This results in an error trying to use the s3 location as script. S3Access can be granted by hand in the yaml file, but you need to know a few things about pcluster to know where to add the optiion.

@mendaomn
Copy link
Contributor

Good point, thank you. We'll investigate the issue and see if there's a better approach

@mendaomn mendaomn added enhancement New feature or request bug Something isn't working and removed enhancement New feature or request labels Aug 22, 2022
@mendaomn mendaomn assigned mendaomn and unassigned mendaomn Aug 23, 2022
@eantonin eantonin self-assigned this Aug 23, 2022
@eantonin eantonin added enhancement New feature or request and removed bug Something isn't working labels Aug 23, 2022
@eantonin
Copy link
Contributor

eantonin commented Aug 23, 2022

We reproduced the issue and put the feature in our roadmap, cannot give a precise ECD yet

@sean-smith
Copy link
Contributor

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 without any modification to pcluster manager:

https://weather.hpcworkshops.com/template/cluster-config.yaml

@stephenmsachs
Copy link
Contributor Author

Yes, thanks Sean. That's what I am doing for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants