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

Spinning up pangeo-forge Beam runner on AWS #6

Open
7 tasks done
alaws-USGS opened this issue Jul 15, 2023 · 3 comments
Open
7 tasks done

Spinning up pangeo-forge Beam runner on AWS #6

alaws-USGS opened this issue Jul 15, 2023 · 3 comments

Comments

@alaws-USGS
Copy link
Collaborator

alaws-USGS commented Jul 15, 2023

  • Install Terraform with conda-forge
  • Clone pangeo-forge-cloud-federation
  • Configured S3 bucket for Terraform
  • Update Terraform configuration in main.tf to point to bucket
  • Ran terraform init
  • terraform plan and instructions
  • terraform apply
  • [ ]
@lesliegarza
Copy link

Load "variables.tf" and append "default = "pangeo-forgery" to the "region" variable.

@rsignell-usgs
Copy link
Member

@yuvipanda merged a fix for the AWS flink deployment, so trying again:

$ terraform apply
var.cluster_name
  Name of EKS cluster to create

  Enter a value: esip-pangeo-forge
var.region
  AWS region to perform all our operations in.

  Enter a value: us-west-2

@yuvipanda
Copy link

@rsignell-usgs you can also copy the var file from here: https://github.com/yuvipanda/pangeo-forge-cloud-federation/blob/main/terraform/aws/bakeries/default-us-west-2.tfvars.

My original design thought was that multiple bakeries would be co-ordinated from that repo, as tfvars files. This is based off of the federated mybinder.org deploy model: https://github.com/jupyterhub/mybinder.org-deploy/tree/main/terraform. Allows all bakeries part of the federation to be kept in sync.

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

No branches or pull requests

4 participants