Repository navigation
AWS ECS Fargate private zone dns resolution not working #13970
ivan-navi-studios
started this conversation in
Archive
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am in the process of provisioning keycloak on AWS ECS using Fargate launch type. I have encountered some strange behaviour when iterating over v17, v18 and v19. This is using the provided docker images.
On Version 17 DNS resolution works perfectly and I can easily configure the database connections to use a private hosted zone. Jgroups also seamlessly integrates
On version 18 keycloak can no longer resolve the provided hostname for RDS. However the JGroups JDBC_PING still manages to connect to the same RDS using the same environment variables.
On version 19... Nothing works
So yeah. I am slightly confused 😄
All reactions