-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route53 DNS-01 Across AWS Accounts #4928
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: