This message was deleted.
# atlantis-communitys
Slackbot
06/12/2023, 11:21 AMThis message was deleted.
j
Jason Reslock
06/12/2023, 12:50 PMYou would likely need some sort of OIDC to set this up.
https://scalesec.com/blog/access-gcp-from-aws-using-workload-identity-federation/
c
Chastity Blackwell
06/12/2023, 1:29 PMYou can also just run another instance of Atlantis in GCP (which is what we do).
j
Jason Reslock
06/12/2023, 1:31 PM^ Honestly that is the "most accurate" answer. I think setting up OIDC between AWS and GCP would be a heavy handed approach to solving the problem.
n
Nour Eddine Rahou
06/12/2023, 1:54 PMThanks for your replies 🙂 This leads me to another question : if you run two instances of atlantis, how do you manage the wiring on your repositories ?
j
Jason Reslock
06/12/2023, 1:55 PMIt is just the webhook and secret that are different right?
Jason Reslock
06/12/2023, 1:56 PMYou create those with the repos? We manage all of our github repos with terraform so a new repo automatically gets a webhook set up for atlantis with a secret.
n
Nour Eddine Rahou
06/12/2023, 2:34 PMThe goal is to have one Atlantis instance that manages the resources on different cloud providers. I will take a look at oidc between AWS and GCP.
a
Andre Ziviani
06/12/2023, 2:35 PMI'm doing exactly that, works fine
n
Nour Eddine Rahou
06/12/2023, 3:36 PM@Andre Ziviani Are you also running atlantis on AWS Fargate ?
a
Andre Ziviani
06/12/2023, 3:40 PMsorry no, only AWS authenticating on GCP via OIDC
c
Chastity Blackwell
06/12/2023, 4:06 PMWe have a single repo, with multiple
atlantis-whatever.yamlChastity Blackwell
06/12/2023, 4:07 PMAnd multiple webhooks, one for each instance