You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: