Hi, is it possible to configure Lemur to create Route53 DNS records in an AWS account different from the account where the Lemur EC2 instance is running from? If so, could you please advise how this is possible? There does not seem to be anything to configure apart from account ID.
My mistake, this does work. I just had my policy wrong.
For anyone else that might need it, you can even do an AssumeRoleWithWebIdentity if you specify an environment variable for AWS_WEB_IDENTITY_TOKEN_FILE.
Hi, is it possible to configure Lemur to create Route53 DNS records in an AWS account different from the account where the Lemur EC2 instance is running from? If so, could you please advise how this is possible? There does not seem to be anything to configure apart from account ID.