hi all,
thank you for your reply.
> Can’t you attach the cross account permission to the glue job role? Why
the detour via AssumeRole ?
yes Jorn, i also believe this is the best approach. but here we're dealing
with company policies and all the bureaucracy that comes along.
in parallel i'm trying
Hi Carlos!
Take a look at this project, it's 6 years old but the approach is still
valid:
https://github.com/zillow/aws-custom-credential-provider
The credential provider gets called each time an S3 or Glue Catalog is
accessed, and then you can decide whether to use a cached token or renew.
Bes
Can’t you attach the cross account permission to the glue job role? Why the
detour via AssumeRole ?
Assumerole can make sense if you use an AWS IAM user and STS authentication,
but this would make no sense within AWS for cross-account access as attaching
the permissions to the Glue job role is
