I'm experimenting with AWSSDK.Extensions.CognitoAuthentication (https://aws.amazon.com/blogs/developer/cognitoauthentication-extension-library-developer-preview/) because I need Cognito User Pool authentication in C# and AWS SDK for .NET does not support that out-of the box.
Unfortunately that extension seems to be flawed. It does not seem to provide a way to pass the User Pool Client Secret (or it's hash), I get "NotAuthorizedException: Unable to verify secret hash for client" when I call CognitoUser.StartWithSrpAuthAsync
I am trying to get list of ListTranscriptionJobs or StartTranscriptionJob using Amazon.TranscribeService but getting exception Authentication failed because the remote party has closed the transport stream.
At the same time from same PC and using same key I am able to access above methods from amazon cli and python code.
Hi, I submitted a pull request about adding a ServiceCollection extension method for supporting TryAddAWSService (aws/aws-sdk-net#935) Could I get some feedback on it?
If it's something that you don't want in the library for one reason or another, or maybe I could see the functionality merged in in the future?
It would be very useful to have this functionality for me personally, so would be good to know if I could potentially get it from the SDK or should I just implement it in my own apps.
Hello. I have an issue with refreshing tokens on Cognito User Pool. I use the example from documentation to log - in. After a successful login (SessionTokens of user object is filled) I try to refresh the token using :
AuthFlowType = AuthFlowType.REFRESH_TOKEN_AUTH,
Unfortunately the call results in Invalid RefreshToken exception. This is in my test application, In which i do it immedietly after login, in a production app I will be refreshing the token only if needed.
Am I doin sth wrong here, or this is a bug ?
Any tips on how to make lambda handler c# code more efficient from .NET perspective?
Some of the example questions I am trying to address:
1) WIll making lambda functions static increase reuse of Lambda context and improve performance?
2) If I make Functions class ( which has all lambda handlers) singleton class, will it improve performance?
3) If I make constant/readonly variables and share it across lambda functions, will it improve performance?
If anyone has any information, please suggest
Hi guys, I'm new to AWS and I've been trying to fix an issue I have with the appsettings.json... been looking for a fix for 3days now ..
I just wanted to know if there is a way to specify which Appsettings to use when deploying a .Net Core application? I have (Dev, Staging and Production) I'm using the Publish to Elastic Beanstalk in my Visual Studio 2017.