-
Notifications
You must be signed in to change notification settings - Fork 256
Appsync Events implementation for flutter SDK #6106
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
Comments
I would also add that this would be very useful for us if it would be supported out of the box |
Hello @matta-pie, thanks for taking the time to open this issue. We will keep this open as a feature parity request, please give your description a thumbs to help us gauge community interest. In the meantime you might be able to use our aws_signature_v4 package to call AWS APIs Amplify doesn't covered yet. |
@tyllark could you explain more about the alternative solution you proposed? in particular i need to subscribe to an appsync event (namespace/channel) using JWT auth. (i guess auth type doesn't change much). from what im seeing, your proposed solution could work to send messages, not subscribing to events. |
Hello @matta-pie, I used an API key to test the following code, but you should be able to update the authorization mapping to match you preferred subprotocol format as documented here. While I used an API key for simplicity I recommend using Authorization in your production frontend code.
Your DNS Endpoints (and API key) can be found at
|
is correct to expose the |
Hello @abarone-btf, for production frontend code I recommend using authorization rather than an API key, which you can read more about here. The code snippet I provided is only intended as a proof of concept for using Appsync Events with our Sigv4 package and should not be treated as production ready. |
Would it be possible to add the implementation for publishing/subscribing to AWS AppSync Events endpoints?
There's already an implementation for all javascript based frameworks
javascript doc
The text was updated successfully, but these errors were encountered: