Ryan Walters

@nc9 Great solution! This saved the day for us. Do you happen to know if there is any additional configuration needed to get this working with subscriptions?

I think it might be useful to allow people to set the type of stream, which would make this more flexible. Maybe something like: ```yml myTable: component: '@serverless/aws-dynamodb' inputs: attributeDefinitions:...

This works for us for the time being, thanks! Looking forward to v6, particularly if there's a tree shakeable way to incorporate Material Symbols into the package.

@cwomack Can someone from the Amplify team please confirm if Next.js server actions are still unsupported in v6 for commands like `signIn`, `signUp`, etc? From what I can tell, `@aws-amplify/auth/server`...

> What would be the use case? A common pattern, usually called "fanout", is to subscribe SQS queues to SNS topics. AWS documentation has a basic example of the pattern...

#195

> With the AuthUserPoolException error that you're experiencing, I believe that's being thrown because the code in your useAuth.ts file is going to be run server-side. If you're Next.JS but...

@cwomack The `Amplify.configure()` and token provider definitions can be found in the sample repo here: https://github.com/ryanwalters/amplify-6/blob/main/hooks/useAuth.ts#L12-L49 Let me know if you'd like me to paste them here instead. The output...

@cwomack Apologies for the delayed response. > @ryanwalters After looking again at the code example in your sample repo, you are configuring the `tokenProvider` and `credentialsProvider` for the server side...

I agree this would be a good feature! I am open to PRs, otherwise I will see what it would take to implement this, possibly in the upcoming v3 release...