Create AWS infrastructure for hosting variant-nowcast-hub #63
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We briefly discussed the S3 bucket name ("hub" in the
hubs.yaml file) here:
https://reichlab.slack.com/archives/C06ESFN6Y79/p1731532728001529
|
🍹 The Update (preview) for hubverse/hubverse-aws/hubverse was successful. Resource Changes Name Type Operation
+ covid-variant-nowcast-hub-read-bucket-policy aws:s3/bucketPolicy:BucketPolicy create
+ covid-variant-nowcast-hub aws:iam/rolePolicyAttachment:RolePolicyAttachment create
+ covid-variant-nowcast-hub-write-bucket-policy aws:iam/policy:Policy create
+ covid-variant-nowcast-hub-allow aws:lambda/permission:Permission create
+ covid-variant-nowcast-hub-bucket-cors-config aws:s3/bucketCorsConfigurationV2:BucketCorsConfigurationV2 create
+ covid-variant-nowcast-hub aws:iam/role:Role create
+ covid-variant-nowcast-hub aws:s3/bucket:Bucket create
+ covid-variant-nowcast-hub-public-access-block aws:s3/bucketPublicAccessBlock:BucketPublicAccessBlock create
+ covid-variant-nowcast-hub-transform-model-output-lambda aws:iam/rolePolicyAttachment:RolePolicyAttachment create
+ covid-variant-nowcast-hub-create-notification aws:s3/bucketNotification:BucketNotification create
|
🍹
|
bsweger
added a commit
to reichlab/variant-nowcast-hub
that referenced
this pull request
Nov 14, 2024
This is the companion PR to hubverse-org/hubverse-infrastructure#63, which has to be merged first (because it providions the AWS infrastructure that must be in place before the hub begins syncing data) Once this is merged, the new hubverse-aws-upload GitHub action will sync existing data to S3. Going forward, it will automatically sync any new or updated data that is merged into the auxiliary-data, hub-config, model-metadata, and model-output directories (and also target-data, once we add that)
nickreich
approved these changes
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We briefly discussed the S3 bucket name ("hub" in the hubs.yaml file) here:
https://reichlab.slack.com/archives/C06ESFN6Y79/p1731532728001529
I added the
-hubsuffix to our agreed-upon name for consistency with other hubs we're hosting on AWS but can remove that if people object.