-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(ecs): target a specific container and port for SRV service discovery #12796
Closed
1 of 2 tasks
misterjoshua opened this issue
Jan 31, 2021
· 1 comment
· Fixed by #12798, aws-iot-builder-tools/iot-reference-architectures#1801, aws-samples/keycloak-on-aws#44, aws-samples/keycloak-on-aws#46 or aws-samples/amazon-emr-with-juicefs#80
Closed
1 of 2 tasks
(ecs): target a specific container and port for SRV service discovery #12796
misterjoshua opened this issue
Jan 31, 2021
· 1 comment
· Fixed by #12798, aws-iot-builder-tools/iot-reference-architectures#1801, aws-samples/keycloak-on-aws#44, aws-samples/keycloak-on-aws#46 or aws-samples/amazon-emr-with-juicefs#80
Labels
@aws-cdk/aws-ecs
Related to Amazon Elastic Container
feature-request
A feature should be added or improved.
Comments
misterjoshua
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Jan 31, 2021
misterjoshua
changed the title
(ecs): provide more control over the cloudmap services
(ecs): target a specific container and port for SRV service discovery
Feb 1, 2021
mergify bot
pushed a commit
that referenced
this issue
Mar 4, 2021
…overy records (#12798) Adds `container` and `containerPort` as optional properties of `CloudMapOptions`. This change allows the user to select which container and container port the `SRV` record points to. Closes #12796 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
This was referenced Mar 6, 2021
Merged
Closed
Closed
This was referenced Mar 8, 2021
cornerwings
pushed a commit
to cornerwings/aws-cdk
that referenced
this issue
Mar 8, 2021
…overy records (aws#12798) Adds `container` and `containerPort` as optional properties of `CloudMapOptions`. This change allows the user to select which container and container port the `SRV` record points to. Closes aws#12796 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This was referenced Mar 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-ecs
Related to Amazon Elastic Container
feature-request
A feature should be added or improved.
I would like to point SRV service discovery records to specific ports on specific containers in tasks.
Use Case
When setting up a clustered Keycloak server, in addition to serving web traffic, the Keycloak instances need to talk among themselves using Infinispan/JGroups on a different port. The best way to accomplish this on ECS with bridge networking would be to use DNS-based service discovery, with the
SRV
record type. But this can only work if theSRV
records can point to the Infinispan ports and not the same port as the web traffic. Currently, CDK's ECS Service constructs want to use the default (web) port on the default container, but in my case, I'd likeSRV
records pointing at Infinispan ports.Proposed Solution
I would appreciate being able to tell service discovery which container and port to use for the SRV record. An interface like this would work:
Other
I have a PR linked to this issue.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: