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

db_port not working as expected #120

Closed
User-nehag opened this issue Sep 21, 2021 · 2 comments · Fixed by #222
Closed

db_port not working as expected #120

User-nehag opened this issue Sep 21, 2021 · 2 comments · Fixed by #222
Labels
bug 🐛 An issue with the system

Comments

@User-nehag
Copy link

db_port = 5454
I have defined db_port value as 5454 in .hcl file but after applying, RDS Instances(reader and writer) are created with port 5432.
I am using below RDS configuration
engine = "aurora-postgresql"
engine_version = "10.14"
cluster_family = "aurora-postgresql10"

@User-nehag User-nehag added the bug 🐛 An issue with the system label Sep 21, 2021
@nitrocode
Copy link
Member

Can you try something like this ?

module "rds_cluster_aurora_postgres" {
  source = "cloudposse/rds-cluster/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version     = "x.x.x"

  name = "postgres"

  engine         = "aurora-postgresql"
  engine_version = "10.14"
  cluster_family = "aurora-postgresql10"
  db_port        = 5432
}

@ekristen
Copy link

@nitrocode db_port doesn't actually seem to modify the rds_cluster instance only the security groups.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
3 participants