Very nice and thank you. Following your instructions was excellent and I managed to get things going. I can now even administer my RDS databases using pgAdmin4. However, having used pgAdmin4 to create a few new databases, they don't show up in my RDS console at all. Any ideas? Anyway - no biggie. Just very grateful to you and cheers from Sydney, Australia - Dave
Thank you so much, Dave! Sure, I'll give you some insight on this. When you create databases in Amazon RDS using a client like pgAdmin4, these databases won’t appear in the RDS console. The RDS console primarily displays instance-level information rather than user-created databases within those instances. To explain further, the RDS console shows each RDS instance and the settings you’ve configured for it (such as engine type, instance size, and network settings). However, it doesn’t display individual databases created within an instance, whether they’re created via AWS tools or external clients like pgAdmin4. This is standard behavior across AWS for managing resources at the instance rather than the database level. To interact with these databases, continue using pgAdmin4 or another SQL client connected to your RDS instance. You’ll still be able to manage, query, and delete databases this way. Hope that helps and thank you again for your comment! All the best!
@@CloudWithDjango Thank you so much for your detailed reply. For some reason YT didn't notify me of your response, but I'm back watching your excellent video and noticed your generous reply. For me, the next challenge is to connect to an AWS hosted Postgres database from a Django instance set up either using Elastic Beanstalk or EC2. I'm slowly getting my head around the AWS ecosystem and am very grateful to you for your efforts in helping us! Cheers, David
Of course, my pleasure! Ah, don't worry, It can sometimes not notify you or things of the sort. Thank you so much for your message and for watching my video! That sounds like a great challenge with it all! I hope everything goes well with it! I'm very happy to hear that you are getting the hang of the AWS eco system and such! Of course, It's my pleasure! Thank you for supporting the channel and watching the content! I wish you all the best, Arno.
Thanks a lot for your videos they completely saved me!! I have a question, my db is on RDS, and I want to deploy my app on PythonAnywhere, after followed the steps in your videos I got: "Connection refused Is the server running on that host and accepting TCP/IP connections" I can deploy it on Pycharm but not on PythonANywhere (connect to same db) I added inbound rules, changed settings of db...Do you know what can it be?
Hi Sodi, Thank you for you feedback, and it is a pleasure. Yes, I know what the problem is. In your local environment, you need to make your migrations (re-migrate) and ensure that you are using your new DB from AWS (I'd recommend then creating a new superuser as a test), only then should you deploy it to PythonAnywhere etc. Good luck!
Why should I use AWS RDS? I don’t like generalizations that cover up details & keep me ignorant about what’s underneath the hood. If I use RDS (as opposed to me just installing Postgresql on AWS EC2 Ubuntu) I’m concerned I won’t learn enough about my Postgresql install.
Using AWS RDS simplifies database management with automated tasks and scalability benefits, but installing PostgreSQL on AWS EC2 allows for deeper learning and control over its installation and configuration.
Once you finished learning PostgreSQL, AWS RDS helps you avoid learning PostgreSQL twice, third, and so on. Also, it helps to avoid learning and do-it-yourself about Replication, Concensus, State-machine, Leader Election, Asynchronous Transactions..
Hi sir, is it wrong if I create a postgres database in the EC2 instance along side my django server so that django get data from the same server so it will be fast . is this wrong ?
Hi Abbas, There are two ways to manage your postgres database. Either with RDS or directly on EC2. Both ways are perfectly fine. I can't speak for speed, but both ways I'm sure have advantages and disadvantages. Myself personally, I prefer to keep Postgres separate with RDS. I only use EC2 as my live server for hosting my Django application.
# Amazon RDS PostgreSQL database - markup
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql',
'NAME': '',
'USER': '',
'PASSWORD': '',
'HOST': '',
'PORT': '5432',
}
}
legend
you are a lifesaver, thank you so much , god bless you.
Of course, my pleasure! Glad that it helped!
Oh my goodness! Is this the best tutorial for this theme ever made???? Yes.
Thank you so much!!!
Awesome tutorial again. You are doing great man.
Thank you so much! I'm glad that you are enjoying the content!
Amazing tutorial! Everything worked super smoothly. Thank you so much!
I'm glad to hear that everything worked well! Of course, my pleasure!
PERFECT. Thank you very much it worked flawlesly.
Thank you! Of course! Glad that you found the tutorial helpful!
Bro you saved me. Thank you
No problem! Glad that it helped!
Thank you, you really saved me
Of course, my pleasure! I'm glad that you found the video useful! Good luck to you!
Thank you!
very helpful thansk.
I'm glad that it was helpful! :)
I am following the tutorial. AWS doesn't have postgres 13.4 anymore. What should I do?
Very nice and thank you. Following your instructions was excellent and I managed to get things going. I can now even administer my RDS databases using pgAdmin4. However, having used pgAdmin4 to create a few new databases, they don't show up in my RDS console at all. Any ideas?
Anyway - no biggie. Just very grateful to you and cheers from Sydney, Australia - Dave
Thank you so much, Dave! Sure, I'll give you some insight on this. When you create databases in Amazon RDS using a client like pgAdmin4, these databases won’t appear in the RDS console. The RDS console primarily displays instance-level information rather than user-created databases within those instances. To explain further, the RDS console shows each RDS instance and the settings you’ve configured for it (such as engine type, instance size, and network settings). However, it doesn’t display individual databases created within an instance, whether they’re created via AWS tools or external clients like pgAdmin4. This is standard behavior across AWS for managing resources at the instance rather than the database level. To interact with these databases, continue using pgAdmin4 or another SQL client connected to your RDS instance. You’ll still be able to manage, query, and delete databases this way.
Hope that helps and thank you again for your comment! All the best!
@@CloudWithDjango Thank you so much for your detailed reply. For some reason YT didn't notify me of your response, but I'm back watching your excellent video and noticed your generous reply.
For me, the next challenge is to connect to an AWS hosted Postgres database from a Django instance set up either using Elastic Beanstalk or EC2. I'm slowly getting my head around the AWS ecosystem and am very grateful to you for your efforts in helping us! Cheers, David
Of course, my pleasure! Ah, don't worry, It can sometimes not notify you or things of the sort. Thank you so much for your message and for watching my video!
That sounds like a great challenge with it all! I hope everything goes well with it! I'm very happy to hear that you are getting the hang of the AWS eco system and such! Of course, It's my pleasure! Thank you for supporting the channel and watching the content! I wish you all the best, Arno.
Thannk u very much .
plz make video on implementing State-management concept of React-Redux on Django app for e-commerce cart management
My pleasure!
Thank you for your suggestion. If I have some time, I will see if I can look into that. React and Django is a good topic!
Thanks a lot for your videos they completely saved me!!
I have a question, my db is on RDS, and I want to deploy my app on PythonAnywhere, after followed the steps in your videos I got: "Connection refused
Is the server running on that host and accepting TCP/IP connections"
I can deploy it on Pycharm but not on PythonANywhere (connect to same db)
I added inbound rules, changed settings of db...Do you know what can it be?
Hi Sodi,
Thank you for you feedback, and it is a pleasure.
Yes, I know what the problem is. In your local environment, you need to make your migrations (re-migrate) and ensure that you are using your new DB from AWS (I'd recommend then creating a new superuser as a test), only then should you deploy it to PythonAnywhere etc.
Good luck!
Why should I use AWS RDS?
I don’t like generalizations that cover up details & keep me ignorant about what’s underneath the hood.
If I use RDS (as opposed to me just installing Postgresql on AWS EC2 Ubuntu) I’m concerned I won’t learn enough about my Postgresql install.
Using AWS RDS simplifies database management with automated tasks and scalability benefits, but installing PostgreSQL on AWS EC2 allows for deeper learning and control over its installation and configuration.
Once you finished learning PostgreSQL,
AWS RDS helps you avoid learning PostgreSQL twice, third, and so on.
Also, it helps to avoid learning and do-it-yourself about Replication, Concensus, State-machine, Leader Election, Asynchronous Transactions..
Thanks!
My pleasure!
✌
Nice
Hi sir, is it wrong if I create a postgres database in the EC2 instance along side my django server so that django get data from the same server so it will be fast . is this wrong ?
Hi Abbas,
There are two ways to manage your postgres database. Either with RDS or directly on EC2. Both ways are perfectly fine.
I can't speak for speed, but both ways I'm sure have advantages and disadvantages.
Myself personally, I prefer to keep Postgres separate with RDS. I only use EC2 as my live server for hosting my Django application.