AWS Amplify/Lobby

Taha Saleh

@Tee88

Hello Everyone
I am currently working on a serverless backend using AWS Lambda and API Gateway. On the frontend side there are two developers, iOS and Android. I decided to use Cognito for our Auth and I am trying to provide the app developers with the correct documentation for them to follow. Also, I am trying to have minimum friction between the app developers and the backend.

Anyways, when I visit the AWS Mobile SDK Documentation page https://docs.aws.amazon.com/mobile-sdk/ , both the SDKs for iOS and Android redirect me to the AWS Amplify framework's website. I have previously used Amplify for a web based app and loved it. However, when I visit the iOS and Android "getting started" pages I find a note saying that Amplify iOS and Android are "in preview mode and not intended for production usage at this time". That said, When I went to the "Android/iOS SDK 2.0" pages I realised that one of the prerequisites is "installing and configuring Amplify CLI" .

My questions are:

What documentaion should both the iOS and Developers in my team follow? (must support production)
Why is the SDK dependant on the Amplify CLI? isn't that in preview mode?
Can the app developers use AWSMobileClient to integrate with Cognito? are they reliable for production?
https://aws-amplify.github.io/docs/sdk/ios/authentication
https://aws-amplify.github.io/docs/android/authentication

I would also appreciate if anyone could share a production-supported step-by-step tutorial for integrating iOS/Android with Cognito?

Thanks

Daniel S. Dantas

@dantasfiles

@Tee88

I would also appreciate if anyone could share a production-supported step-by-step tutorial for integrating iOS/Android with Cognito?

https://github.com/awslabs/aws-sdk-ios-samples
https://github.com/awslabs/aws-sdk-android-samples

Jun

@Jun711

Hi, should I import API using import API from '@aws-amplify/api'; or import API from 'aws-amplify';?

Jeff Finley

@quickliketurtle

aws-amplify is the full sdk, the @aws-amplify/*** is just the relevent bits. So if all you are using is api then you can just import that.

Brandon Shega

@BrandonShega

Does anyone here use SAML via Okta for the federated login? I'm trying to log users in, I get a token back but when I try to call Auth.federatedSignIn() I'm getting an error: NotAuthorizedException: "Invalid login token. Issuer doesn't match providerName"

This is how I'm calling it

      const user = {
        name: 'test',
        email: 'test@test.com'
      };
      await Auth.federatedSignIn('okta', { token: token, expires_in: expires_in }, user);

where okta is the name of the provider that is in the token.

token is the idtoken from okta

Taha Saleh

@Tee88

@dantasfiles Thank you, I will take a look at it :)

Daniel S. Dantas

@dantasfiles

I'm working with Amplify Auth lambda triggers, and looking at the documentation

Errors thrown by Lambda triggers will be visible directly to your end users if they are using Amazon Cognito Hosted UI as query parameters in the Callback URL. As a recommended best practice, end user facing errors should be thrown from the Lambda triggers and any sensitive or debugging information should be logged in the Lambda trigger itself.

I don't understand what that means. I'm looking at the example files, and they all do different things, some console.warn, some callback("error text");, some callback(new Error("error text", event); Can someone explain in simpler language what an end user facing error is?

Jun

@Jun711

aws-amplify is the full sdk, the @aws-amplify/*** is just the relevent bits. So if all you are using is api then you can just import that.

Thanks @quickliketurtle

When I import API from @aws-amplify/api and import Auth from @aws-amplify/auth, I get 'No credentials available, the request will be unsigned' when using API to send a post request to an API Gateway endpoint.

Jeff Finley

@quickliketurtle

You’ll need to add Auth.configure(); as well.

Jun

@Jun711

@quickliketurtle Yes, I have Auth.configure({ Auth: { identityPoolId: ... }}; and API.configure({ API: { endpoints: [...]}});

Daniel S. Dantas

@dantasfiles

the PreSignup example uses callback(new Error(Invalid email domain: ${domain}), event); so I guess that's the style I'm going to go with, though I wonder if I should do a console.log as well

Jeff Finley

@quickliketurtle

@dantasfiles I generally do both, so user friendly messsage in callback, and console.log developer friendly message / error message / stack tracks / etc…

Daniel S. Dantas

@dantasfiles

@quickliketurtle ok, thanks!

Nick Bagley

@timeconsumer_gitlab

Anyone else ever run into an issue where the amplify build when hooked into a git repo overwrites the environment variables specified in PreSignup, CustomMessage, ...etc lambdas on the build?

Kristine Olberg

@krisolberg_gitlab

Does the Amplify custom auth challenge support reCAPTCHA version 3? It wouldn't seem to since the documentation says, "VerifyAuthChallengeResponse will run when the Auth.sendCustomChallenge function is called with the data that is returned when the user interacts with the Google reCaptcha component." With reCAPTCHA version 3 there is no explicit user interaction with the component--it works behind the scenes. But am I missing something?

eliasericsson

@eliasericsson

Can anyone point me in the right direction to more information about how to use the ModelTodoFilterInput? @dantasfiles provided some links to Query and Scan, but I wasn't able to put it together.

What I have is a Storage.list -operation that returns an array of 5 object. Each of these has a key-value pair. I would like to filter the response, so that I only get the 4 objects where the value partially matches a given string.
Eg.

// Given string: "filename1"
{
key: "path/filename1.jpg"   // match
...
key: "path/filename2.jpg"   // no match
...
key: "path2/filename1.jpg"   // match
}

Expected response:

{
key: "path/filename1.jpg",
key: "path2/filename1.jpg"
}

@dantasfiles That's acceptable for my use case, thanks!

eliasericsson

@eliasericsson

@dantasfiles

onDelete(mykey) {
        console.log(mykey)
        Storage.list('', {
            level: 'protected',
            key: {contains: mykey}
        }).then( res => console.log(res) );
}

Still I get 5 in return when I expect 4. Just console.log(mykey) gives the expected string

I'll have a look at mock api

@dantasfiles I'm still very grateful!

eliasericsson

@eliasericsson

@dantasfiles I think the error is on my part. I keep mixing up API and Storage

Daniel S. Dantas

@dantasfiles

@eliasericsson storage.list returns a list of keys, right? so can you run something like res.filter(({key}) => key.match(regex)

Ranjith Ramesh

@ranjith8593

I am following amplify javascript to build react native app

i ran amplify init

amplify publish is failing saying that npm build script is not present

https://aws-amplify.github.io/docs/js/start?ref=amplify-rn-btn&platform=react-native

I exactly followed the same steps here . should we add any build script to package,json file

Jeff Finley

@quickliketurtle

When you run amplify init you are asked for a build command, the default is npm run-script build, but when using expo to create the app, there is not an npm script called ‘build’. So it sounds like that is the issue.

Since you are creating a react native app, you shouldn’t need to use amplify publish as you have no frontend to publish to s3. So you should be using amplify push to deploy your backend.

Ranjith Ramesh

@ranjith8593

Great. Thanks

Jun

@Jun711

@quickliketurtle I figured out the problem> it seems that it is a npm package manager issue that I had multiple copies of aws-amplify/auth in node_modules. I fixed it based on the steps listed here https://github.com/aws-amplify/amplify-js/issues/2098#issuecomment-439627717

Jeff Finley

@quickliketurtle

Nice, glad you got it figured out.

Kros21

@Kros21

How are you?

I have some questions now

When using aws-amplify, I am getting the following error.

"ProtoType value can only be an object or null"

Please help me, thanks

Wouter van den Broek

@wbroek

@rathoregee if you call Auth on Amplify Auth it should do the redirect, thats what the button also does in my opinion

Kros21

@Kros21

Thanks.
May I ask detailed content about this issue?

If needed, I can share my code.

Gino-Casolaro

@Gino-Casolaro

How would one implement handlebars with amplify can't seem to get it to load with .hbs files

Riccardo Sirigu

@ricsirigu

Hi everyone, I'm building a webapp with Amplify and I need a bucket with multiple folders.
Each folder must be accessible only by a specific Cognito group.

For example

Mybucket/firstClient
Mybucket/secondClient

And I have firstClient and secondClient cognito groups with multiple users inside.

Is there a way to model such a policy? Or is there another way to accomplish this?

Erich L Timkar

@erich-team

S3 doesn’t actually have folders. It may look like it in the web interface, but they don't . S3 just kindly translate any “/“ in the object keys as folders in the interface. It’s purely a display consideration.

Depending on the scenario, it might conceivably be possible to simulate something like it, but it seems like it would be a reallly difficult, would involve custom policies and maybe tags, and could likely be brittle.

Jeff Finley

@quickliketurtle

@ricsirigu Have you looked at Amplify Storage? that creates a few levels of folders (prefixes) and permissions. Including how you could use a users cognito identify to allow access. It doesn’t solve you specific ask directly, but will give you an idea of how to do this.

Erich L Timkar

@erich-team

Now, if didn’t only wanted to query S3 and return to firstClient the objects in "Mybucket/firstClient", but not actually formally restrict, you could filter by key.

Yeah, what Jeff said. :)

A decidedly more helpful anwer.

Where communities thrive

People

Repo info

Activity