10-10-19

Yesterday, a review:

1. YAY I GOT EVERYTHING WORKING LOCALLY!
2. But wait, not on aws. W T F
3. Panic
4. Panic more.
5. Turn the panic into sheer despair.

6. Break the problem down one by one.

7. Make sure the post request is working (on AWS) express docs on post
8. Test via curl
9. Review permissions? I Think this is what fixed everything? However, TBH I am not sure. I’m also not sure if it’s a good thing to just… blanket give permissions. I’m actually pretty sure this is a very bad thing. Oh well, learning! If you, reader, have any idea the “correct” way to do this, please PLEASE LMK via email!! So much learning to do!! See “Add Permissions to your Environment’s Instances” section
10. withCredentials: true also might be a thing
11. annnnd it also might have just been this blanket permission add AWSElasticBeanstalkFullAccess

TODO:

1. USE THE LAMBDAS, LUKE
2. Go back to express roots
3. Express on Heroku
4. Understand the words on this page – wtf is non-proxy integration
5. Maybe go back to these roots, too
6. this looks like a fun adventure!
7. Maybe play around with php + aws

RESOURCES:

AWS Elastic Beanstalk docs Dude’s github …from the original medium article