Cannot subscribe to a Kinesis stream using the new Enhanced Fan-out feature

[codenaked]

From the changelog, it looks like SubscribeToShard support should have been added in version 3.3.6.0 of the Kinesis assembly, but it doesn't seem to be available.

Expected Behavior

I should be able to subscribe to a Kinesis stream using the new Enhanced Fan-out feature.

Current Behavior

I cannot subscribe to a Kinesis stream using the new Enhanced Fan-out feature because the methods/types/etc are missing.

Your Environment

AWSSDK.Kinesis Nuget version used: 3.3.6.2 Targeted .NET platform: 4.7.1

[klaytaybai]

Hi @codenaked, this is not supported within the .NET SDK right now. To the best of my understanding, it is a supported feature within the Java SDK. I will mark this as a .NET feature request for now.

We will also work on getting that changelog fixed up. Thank you for pointing that out.

[VladimirMakaev]

It's been a year since this had been reported. At this stage I'd expect feature parity at least at the SDK level. Any idea if this is being worked on?

[klaytaybai]

Thanks for checking back in. It has not been forgotten, but we have been prioritizing some other work at the moment. It is in our queue and regularly discussed.

[AlainH]

Is there perhaps an ETA on .NET SDK support for enhanced fan-out? We love the performance and throughput of fan-out and would like to be able to use it directly from .NET without having to use the KC.L

[evhen14]

I would rather have some update. Is it on the roadmap? Is this feature dead? What is required to have it implemented, etc? If there is no work planned, then close the issue with an explanation.

I definitely support the view that using KCL which requires Java runtime is a bad design and should be avoided and the second-best option for resuming consumption is SubscribeToShard which is not available in the SDK.

[pablocastilla]

Hi!

Any news about this? On the other hand, how do you see to connect to the rest endpoint by ourselves in plain c#?

Thanks

[jeremyssavage]

I'm also very eager to see this implemented!

[jpo-tu]

4 years later, how's this feature coming along?

[LarsAndreasEk]

Also waiting for this. Any update? :)

[FernandoMaiaSky]

5 years later, how's this feature coming along?

4 years later, how's this feature coming along?

[sumitvashistha]

We need this feature for the DotNet client. It's a major setback.

[alexjoybc]

Any update on this, when could we expect to have Enhanced Fan-out support?

[Simonl9l]

@normj - given your reply on this on AWS re:Post for about 2 years ago, is there any movement on this since HTTP/2 seem to have been available since .Net3.1?

https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#http2-support

[normj]

@Simonl9l It is on our backlog to take advantage of .NET's HTTP/2 support but we haven't been able to get to it yet.

[Simonl9l]

@normj -thanks for the timely reply!

Is there any timelines for this?

Net/Net need is to be able to consume data from a Kenesis Stream outside of AWS.

[normj]

@Simonl9l Sorry I don't have a timeline when we will get to HTTP2 support in the SDK. I'll bring this back up for discussion but I'll admit a big focus we are going to have for the next few months is cleaning up some of our technical debt we have accumulated for the 14 years of the SDK including the announcement today of removing .NET Framework 3.5 support. https://aws.amazon.com/blogs/developer/important-changes-coming-for-net-framework-3-5-and-4-5-targets-of-the-aws-sdk-for-net/

[Simonl9l]

@normj - Thanks for the continued replies on stuff!

Great to hear that y'all's are picking away at the Technical Debt pile! In early 2027 it seems you might be free of having to support .Net Framework entirely!

I'd really wonder how many .Net Frameworks active developments (that use AWS SDKs) are still out there!

I re-pinged this issue as it seem the other language SDK's have this support and it's a gap in the .Net SDK, and defer to you where that lines up vs. other priorities.

I'm not sure if I could commit to help fix this gap, but curious to see if such help is supported?

In the mean time it seems that there is a AWS labs repo that has something going in this regard - but not given it any close inspection - that may allows us to bridge, and possibly help others also.

[normj]

There is still a lot .NET Framework usage. and we have a really high bar to remove a platform hence we are just not removing .NET Framework 3.5. I wouldn't expect .NET Framework support to go away anytime soon.

It is a gap with the .NET SDK not having and is one I really want to fix. It is a matter of fighting through some many priorities to make time. We do take PRs but this feature would be pretty intensive because you have to dive deep into not just HTTP2 but how AWS event stream based services work and the SDKs code generator which is pretty low level.

[Simonl9l]

OK fair enough....we live in hope!

In the mean time as above we can poke around the AWS Labs sample and see if we can make that work. It has a commit from 3 months ago so that is promising.

[normj]

I know users have been successful with the labs project. It has been around for quite a few years and is pretty harden. It does require running a Java daemon that .NET interops with.

[Simonl9l]

Ah that's not going be very AoT able...

[svrx]

@normj, I'm also interested in this development. I understand that due to broad support for .Net Framework and .Net (Core) it's hard to balance this feature with the platform limitation. Although I'm wondering if support could be added as an extension to the SDK, similar to what was done to support S3 client side encryption?

[Usualdosage]

So here we are in (almost) October 2024 - Any movement on this? We're currently using the common workaround, but I would like to know if we can expect the SubscribeToShare API at any point in the near future for .NET?