-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
elbv2: LoadBalancer.fromLookup() #6803
Comments
Hey! It looks like you're describing a solution rather than a problem. Please describe your situation, what you're trying to achieve, and why you are having trouble achieving what you'd like to achieve. We then we will decide how to best solve the problem considering your use case and other use cases we'd like to enable. This could be using the solution you suggested, but it could also be another solution altogether. For example, what if you didn't have to implement the interface at all, but we provided a class for you that did what you needed it to? Would you still care that its properties are required? |
In this particular case, by the way, these is no way around specifying the two pieces of information we need, because that's simply what route53 requires and there's no way to derive them. The alias target needs the hosted zone ID and the hosted zone name, which you are expected to supply when calling I will interpret this as a request for a |
Hi @rix0rrr good morning. thanks for the reply. yes, the particular scenario/steps I'm describing may or may not be a bug. my goal is, "to create an Alias record on Route53 with an ALB target". (it seems) the api clearly provides a way to do this, e.g., using it can be achieved in many different ways. but, in my view, the original api designer intended to use this particular apis for this particular purpose. that's why, I think, he/she introduced all these elaborate constructs like Again, I'm not insisting on a solution. The possible solution/steps I provided was based on my (limited) understanding of the api. I would probably consult with the original designer/implementer as to why he/she defined Thanks! |
Any update on this? Facing the same issue. |
@realharry were you able to do this using any work around? Would be of great help. |
Any update on this? |
This does seem like a bug. If I look up a load balancer using any method, I should get a consistent load balancer object that I can use in any way a load balancer can be used. I'm sure there is much more to it under the hood, but from a user perspective, this is a bug. |
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
In order to be able to create an Alias record on Route53 with an ALB target, one needs to use the
ILoadBalancerV2
interface. However, currently all fields ofILoadBalancerV2
are required, which makes it difficult to use.Reproduction Steps
ARecord
targeting an existing application load balancer (e.g., with dns name something likeabc.region.elb.amazonaws.com
).ARecord
constructor requirestarget
field of typeRecordTarget
.RecordTarget
constructor takes a field,aliasTarget
, of typeIAliasRecordTarget
.LoadBalancerTarget
, which implementsIAliasRecordTarget
, requires an argument of type,ILoadBalancerV2
.object with
loadBalancerCanonicalHostedZoneId` or `loadBalancerDnsName`.Error Log
N/A
Environment
Other
This is needed, among other things, to support naked domains (zone apex record) pointing to the application load balancer.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: