2i2c-aws-us, showcase: fix bucket access after rename

2i2c-org · Jan 31, 2024 · f95c5fe · f95c5fe
1 parent 9d64489
commit f95c5fe
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/config/clusters/2i2c-aws-us/showcase.values.yaml b/config/clusters/2i2c-aws-us/showcase.values.yaml
@@ -4,7 +4,7 @@ basehub:
       # When we renamed this hub, we did so at a DNS level and not an infrastructure
       # level. No terraform config was touched. Hence the kubernetes annotations retain
       # the original hub name.
-      eks.amazonaws.com/role-arn: arn:aws:iam::790657130469:role/2i2c-aws-us-researchdelight
+      eks.amazonaws.com/role-arn: arn:aws:iam::790657130469:role/2i2c-aws-us-showcase
   jupyterhub:
     ingress:
       hosts: [showcase.2i2c.cloud]

diff --git a/terraform/aws/projects/2i2c-aws-us.tfvars b/terraform/aws/projects/2i2c-aws-us.tfvars
@@ -40,7 +40,7 @@ hub_cloud_permissions = {
     bucket_admin_access : ["scratch-dask-staging"],
     extra_iam_policy : ""
   },
-  "researchdelight" : {
+  "showcase" : {
     requestor_pays : true,
     bucket_admin_access : [
       "scratch-researchdelight",