Actual AWS engineering conversation: "So how will people debug these things?" "We're Amazon; we don't debug anything and neither should anyone else." "I'm sold. Ship it."
Hello from the year 2022! at around +27:55, my setup triggers a deprecation warning. To fix it, I did this import { Amplify } from 'aws-amplify'; take care and best wishes future internet person :)
I followed the tutorial and my app.js in the backend has the 'Enable CORS for all methods' block of code, however it is still being blocked because of cors - it says 'Access-Control-Allow-Origin' header is not present - nothing seems to solve and each attempt I have to amplify push and wait
@@ttngocthao when you create a path in your api , for example /people using aws console , you SHOULD write code in your app.js using /people in the ligne app.get('/people', async function (req, res) {. In other words , if you add a new path , for example /birds, in the app.js code , you have then to create this path using the command line 'amplify add api' and declare a new path /birds. Respect the path name. Regards,
Amplify's docs are really tricky to understand. Adding packages to a lambda function isn't documented anywhere, this is the first time that I have seen it's possible. Does anyone else have a good source to learn the capabilities of each Amplify service that maybe expands on the official docs? I feel the official docs only shows a keyhole of information and not really to bigger picture making learning it a bit frustrating...
Does anyone get the error of net::ERR_CONTENT_DECODING_FAILED 200 when you send a GET request to the api endpoint and expect to receive an array of objects?
Is anyone getting a 403? I tried adding headers {Authorization: {jwt}} but that didn't work,. I'm not doing the exercise in a new app, I'm adding to my add which already uses cognito
To achieve faster development cycles for your lambdas, you might want to switch over to the serverless framework, it can spin up a local dev environment, running the lambda Functions on your machine. You can still do everything else than lambda development using amplify.
I find that keeping production environment at the same AWS account with other environments is very dangerous. Your dev and test environment can simply eat your budget for DynamoDB or other limited services, and then you are fucked. Please be warned, deploy your production environment on separate AWS account.
Just come across amplify after setting up a custom nodejs framework in aws and I'm totally sold! Thanks for the tutorial, this is super helpful
You are a lifesaver. Cheers Mate
Excellent Nader, I thought it would be rough to get through an hour but you made it interesting and I learned a ton, thx
This video is what I was looking for, thank you man!!!
great explanation Nader | nice video
Thanks, this tutorial was very helpful.
@54:30 your ternary expressions are swapped. That’s why the query always returns the same results.
Actual AWS engineering conversation:
"So how will people debug these things?"
"We're Amazon; we don't debug anything and neither should anyone else."
"I'm sold. Ship it."
As an engineerworking at Amazon this is true
Hello from the year 2022! at around +27:55, my setup triggers a deprecation warning. To fix it, I did this
import { Amplify } from 'aws-amplify';
take care and best wishes future internet person :)
Great video.
This is great! Thank you!
Thank u for this awesome video
I followed the tutorial and my app.js in the backend has the 'Enable CORS for all methods' block of code, however it is still being blocked because of cors - it says 'Access-Control-Allow-Origin' header is not present - nothing seems to solve and each attempt I have to amplify push and wait
Have you found a solution for it? I’ve got the same issue and have not found the solution yet 😭😭😭
@@ttngocthao when you create a path in your api , for example /people using aws console , you SHOULD write code in your app.js using /people in the ligne app.get('/people', async function (req, res) {.
In other words , if you add a new path , for example /birds, in the app.js code , you have then to create this path using the command line 'amplify add api' and declare a new path /birds.
Respect the path name.
Regards,
@@sylvainverdat7135 : I did create a path but that does not solve the cors issue.
@@ttngocthao I had some luck using the Moseif extension in Chrome.
There is an error at 13:00. If you are using Aurora Serverless, you cannot trigger functions automatically.
Hey great tutorial! Maybe I can have you on my channel while I do something similar and I can ask you questions :)
Hey Erik, I'd still love to come on to the channel!
What theme are you using for vscode
Amplify's docs are really tricky to understand. Adding packages to a lambda function isn't documented anywhere, this is the first time that I have seen it's possible. Does anyone else have a good source to learn the capabilities of each Amplify service that maybe expands on the official docs? I feel the official docs only shows a keyhole of information and not really to bigger picture making learning it a bit frustrating...
looks painful to have to push the lambda up each time to run it.
What did you do to solve that time?
@@jomab29 with the aws tooling you can invoke the function locally. There is a command for it in the CLI as well as vs code extension
@@-_-unseen-_- $amplify function invoke [theFunction] ???
Does anyone get the error of net::ERR_CONTENT_DECODING_FAILED 200 when you send a GET request to the api endpoint and expect to receive an array of objects?
Is this how you interact with environment secrets?
posting in 2021, AWS CDK is a viable (and much better imho) solution as well
Is anyone getting a 403? I tried adding headers {Authorization: {jwt}} but that didn't work,. I'm not doing the exercise in a new app, I'm adding to my add which already uses cognito
Could we use AWS SES on amplify??
fyi, the swapi api no longer works, at least not for me. I had to use a different rest endpoint for it to work.
Where can i find the source code of this example?
how can I upload the apis faster from amplify to AWS to test them faster? I think that time is crucial for development performance.
To achieve faster development cycles for your lambdas, you might want to switch over to the serverless framework, it can spin up a local dev environment, running the lambda Functions on your machine. You can still do everything else than lambda development using amplify.
Actually I think you can also invoke them through amplify cli.
This is complicated though when you use them tightly coupled to dbs
"if you get a 100 million user which probably will happen for you"
I find that keeping production environment at the same AWS account with other environments is very dangerous. Your dev and test environment can simply eat your budget for DynamoDB or other limited services, and then you are fucked. Please be warned, deploy your production environment on separate AWS account.
Good point.
Arnold Schwarzenegger?
damn a very long video with all the table of contents not covered was watching for nothing damn.