Skip to content
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

Support for Elastic IP or Multi-Account Route 53 DNS Record Creation #26

Open
loukandr opened this issue Oct 30, 2023 · 0 comments
Open

Comments

@loukandr
Copy link

I'm using this module to create a bastion host in my AWS environment. My setup involves having two separate AWS accounts: one for the environment resources (e.g. staging, production, including the bastion host) and another for management resources like Route 53.

Issue

The module, as currently designed, does not associate an Elastic IP with the bastion host, causing the public IP to be dynamic. Additionally, since the module attempts to create a Route 53 record in the same account as the bastion host, it doesn't fit well with my multi-account setup (AWS organisation) where Route 53 is hosted in a separate management account.

Desired Outcome

a. Add an option to associate an Elastic IP with the bastion host, or
b. Provide a way to specify a different AWS provider for creating the Route 53 A-record, so it can be created in a separate AWS account.

Would you consider adding these features? They'd be incredibly helpful for scenarios like mine.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant