This message was deleted.
# atlantis-community
s
This message was deleted.
👀 1
n
I had a massive issue trying to get atlantis to read data outputs cross-state, I was not able to set it up, and I just found a way to work around it… I tried all the different s3 ACL/access combinations, nothing helped…
s
im running atlantis on k8s, so this may not be relevant but the way i've got it to work for cross state data outputs is... the atlantis service account(not the provider role) needs to have read permissions to those cross state buckets, and the buckets themselves need to allow the atlantis account read perms.
n
hey, I had state files in the same bucket, just different location/folders… And I was not able to get it to work 😄 So atlantis is able to write in each of those state files separately, but when I try to read a data output cross-state, I was not able to get it to work…
s
ok, so you have a state bucket, and it can
init
fine, but on
plan
if it tried to read a data `terraform remote state" resource it would fail?
n
yup, 401 if i remember correctly, it was couple months ago…
s
yeah i was getting a 403
access denied
but it was because the role that was running atlantis didn't have read permissions to those buckets
as soon as i gave it read perms it worked.
remember, the account for the aws provider is not the one reading data sources for remote state.
that's what tripped me up
n
i will have that in mind when I try something similar again… thanks…
s
👍🏼 👍🏼 👍🏼 👍🏼 👍🏼