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

Create AWS permissions required to deploy the model-output transform lambda from GitHub Actions #39

Open
2 tasks
bsweger opened this issue May 2, 2024 · 2 comments
Assignees

Comments

@bsweger
Copy link
Collaborator

bsweger commented May 2, 2024

Background

This is related to (and a pre-requisite for) hubverse-org/hubverse-transform#6

The hubverse-transform repo will have a GitHub action that deploys an AWS Lambda package by creating the package and writing it to an S3 bucket (hubverse-assets).

Thus, that repo's GitHub actions will need to assume an AWS IAM role that has permissions to write to hubverse-assets.

Definition of done

  • The Pulumi code base creates an IAM role with a resource policy that specifies list/get/delete/write access to s3://hubverse-assets
  • The new role's trust policy specifies that the role can be assumed only via GitHub OIDC provider and only by the main branch of the hubverse-transform repo
@bsweger bsweger converted this from a draft issue May 2, 2024
@bsweger bsweger added this to the hubverse cloud sync milestone May 2, 2024
@bsweger
Copy link
Collaborator Author

bsweger commented May 2, 2024

We should be able to copy and re-purpose some existing code to do this. See the first 3 functions of iam.py: https://github.com/Infectious-Disease-Modeling-Hubs/hubverse-infrastructure/blob/main/src/hubverse_infrastructure/hubs/iam.py#L5

@bsweger
Copy link
Collaborator Author

bsweger commented May 23, 2024

Because we're getting close to the Hubverse's GitHub org name change, will plan to hold off on this work until that's completed (because the trust policy is based on GitHub org and repo name).

@bsweger bsweger self-assigned this Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant