![]() AWS flavor has default packages that are likely to be behind what you find in tutorials. To use AWS responsibly, you want learn something about AWS IAM but while you're just getting up and running, be irresponsible, IAM is a distraction.Ī concrete piece of advice: use Ubuntu linux to start, not AWS linux. That means there is only 1 AWS service you need to concentrate on: ec2. And I don't think it's plausible to run django on aurora/zappa as anything but a demo that it's not impossible. Someone correct me if I'm wrong - there's no way you're going to run an always-up hosted postgres instance for < $10 month if you're out of the free tier. If you wanted to really make a popular app and feel a sense of responsibility to your users, and aren't planning on hiring people, then long term you'd probably want to do hosted. ![]() If you're doing it to learn, it's a great exercise. This doesn't incur any costs if you have a new AWS free-tier account. What I did was the former - I did everything with a single ec2 instance, and no deployment pipeline (just scp and upgrade/install stuff thru the shell). The key distinction is are you going to want to set up everything on a linux machine to be similar to what you set up on your local PC, or are you going to use hosted services? "Hosted" would mean AWS lightsail and some AWS postgres. For working on aws ec2, one critical advantage I had that you might not is I was very familiar with unix shell.ĪWS is overwhelming if you start trying to research it generally. I set up a django site on AWS a couple years ago and it was a great learning experience - it helped with my day job. There's a couple things in this post I'm not so sure of that I called out - but corrections from others are welcome + solicited.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |