I'm looking to be putting out more videos now so it shouldn't be long!

Thanks for the support Ernie

Glad you liked it!

Thanks for the sub!

My pleasure. I'm glad it was useful

Glad it was helpful!

Have fun!

Haha. Glad I could help!

Thanks for the sub!

Happy to help!

Glad it helped!

Glad you liked it!

That's the plan! Amplify allows you to connect directly to Dynamo

Glad you found it useful

Awesome, thank you!

It's amazing how easy login and authentication becomes with cognito

@@CompleteCoding Does it cost any money to use the forgot login functionality where AWS sends you a verification code in an email?

@@jamesbotwina8744 I don't think that it does cost to send those emails. AWS SES has a free tier of 62,000 emails per month

@@CompleteCoding wow, very nice. Looks like you can get a lot done with the free tier. I've also been looking into AWS Activate for a startup idea I have. $1000 in credits is huge!

@@jamesbotwina8744 Yes, I think I use a few dollars a month on all of my projects combined. Even getting one or two paying users covers the AWS costs.

No problem 👍 glad you found it useful

Glad you liked it!

Not directly with the Amplify CLI but I have used MFA on Cognito

Glad it was useful

You're welcome!

Glad to hear it!

Glad it helped!

Thanks, I'm glad you like the videos

This video was made before the latest version of the Amplify UI Library came out. You code is more up to date than this video now.

Thanks!

Glad it helped!

Really interesting idea. You could do it by creating an 'approved reader' table. Each row has a primary key of the reader's userID and a range key of the articleID as well as a secondary index with primary of authorID and range key of articleID + reader userID. You'd then create a query called 'getArticles' which would query the approved readers table. That would return a list of article IDs. You'd then use those to get the articles. The owner of the article would be able to query all of the users for a given article. They could then add and remove rows from that table to allow or disallow readers.

Yes you can! You need to set up cognito so that it doesn't authenticate the user on phone or email. This way the user will be be signed up but not authenticated so will not be able to sign in. To allow a user to access the app, the cognito admin needs to approve the user. You could do this by cognito console or by cognito admin APIs.

Really glad that you liked the video

There are loads of videos on youtube about this. It can be a complex topic with all of the different payment types and I'm not an expert in Stripe

Amplify has an inbuilt hosting solution (which used s3 behind the scenes) I also have a video on this with the serverless framework kzfaq.info/get/bejne/qbOKoJt5prmvnIE.html

Yes I do kzfaq.info/get/bejne/qbOKoJt5prmvnIE.html This also covers Cloudfront. If you don't need that you can just do the S3 and s3Sync parts to see it online

hello I am beginner to aws.. i hv done everything what u said in video.. but once i closed everything ..how do i again access my created page or deployed react app.. i checked with npm start it showing error.. plz help me for this

@@hareeshbadiger8167 If you go into your AWS account and search for "clioudfront". In there you should see your new distribution which points to your S3 bucket. It will have a URL like d111111abcdef8.cloudfront.net/index.html

That depends on what permissions the AWS Admin has given to the role that you are assuming in AWS. Sometimes you may need to ask them to add a certain permission to your role if you hit a permissions issue. I don't think that using SAML2AWS credentials will make any difference, but I've not tested that.

@@CompleteCoding yes got your point, Thanks!

I'm using Monokai Pro theme. It is a paid theme ($10 I think) but I really like it and have used it for years now.

Glad you liked it

I think the best way to customise the signout (or signin) is to create your own component and just call the Amplify methods for signing in and out. docs.amplify.aws/lib/auth/emailpassword/q/platform/js#sign-out

I was planning to do a custom cognito setup (using the last video) but realised that this wasn't the easiest way to do things so went with just using amplify instead.

You can change the settings so that users aren't able to sign themselves up. This is a setting called "Only allow administrators to create users" You can then create users from within the Cognito Console.

Thanks

My pleasure. There are functions that you can call on the amplify sdk like "Auth.signIn" which you can wrap in your own actions to be used in a custom login screen. The Amplify docs are actually really good. docs.amplify.aws/lib/auth/emailpassword/q/platform/js

I now use the amplify auth package to manage the login to cognito and adding auth to all of the api requests. I don't use amplify for deploying any resources.

Happy to help

Thanks for the visit

Amplify creates it's own cognito user pool. Yes, knowing those details doesn't give anyone access to anything. It just tells them where to log in to. They could in theory use them to create their own login page but that wouldn't be much use

Keep watching the playlist and we get onto changing the home page very soon. kzfaq.info/sun/PLmexTtcbIn_hvPcUm3oAufCtH7dwNAC-g

Use react router dom and set the home page of path (/) and use redirect method to send to it welcom page

Yes, there are some parameters that you can pass into the configuration for amplify to remove those buttons. You could also use the amplify auth functions and attach those to your own custom login screen if you want full control over your UI

did you run npm install -g @aws-amplify/cli You may need to restart your terminal

I've not worked with native apps so I've not used the push notification system before. I would think that you could still send a notification to an app that doesn't have an authenticated user. As long as you know the deviceID that you want to notify. As I said, I've not worked with Native or push notifications so this may not be the way it all works

@@CompleteCoding Thank you so much for replying

@@sachinbhatt1519 No problem!

Amplify has published a V2 of their npm package and it has a lot of changes. If you want to get it working you can just install v1 npm i @aws-amplify/ui-react@1.2.26 The other option is just creating a button that when clicked calls Auth.signOut() docs.amplify.aws/lib/auth/emailpassword/q/platform/js/#sign-out Or looking at the v2 docs and changing it to work with that

You can see all your users in cognito in the AWS console. There are also apis for cognito of you wanted to build a 'users' view in your app

@@CompleteCoding thank you so much!!!

You shouldn't be paying any more to use Amplify. You only pay for the services that it uses. If you are talking about the amplify hosting then you don't have to use that. You can use the amplify SDK and then host the website in S3 yourself (Like I'm doing) If you really don't want to use amplify you can do everything without it. You can set up cognito and then use it as an authorisers on your APIs. You would have to create your own login and signup processes to securely work with Cognito

I'm not sure if you can do that in the default UI but you can always create a custom UI, do all your own validation and then call the Amplify methods to set/reset the password and other fields.

Yes, just build your react app and then host it wherever you want.

I'll look into making a video showing you how to do that. Keep your eyes peeled for that.

Yes, you could add a new model in amplify for a user. You can then get and update the user as you have got and updated songs. Have a React hook that triggers once when the app loads to get the user.

It looks like, behind the scenes, they are doing the same thing. It looks like you may be able to use the hosted login UI in some other ways too.

I've got a video on that coming out tomorrow

I don't know if you can. You could have different deployments of the same app that point at different user pools, but I don't think you can have one app point at two pools.

I am looking into using amplify and cognito for my project because I want to learn AWS. Can you mention which part is outdated so I can look for an alternative or should I switch to a different tutorial series?

Does the file exist? If not then you need to make sure you've done the Amplify init and setup. That will generate that file for you

@@CompleteCoding it was directly put under gitignore.

I don't think you can do this with amplify. If you find out how to then let us all know

Glad you liked it!

Yes, You can manually add any of the config files you want.