Issue
I have followed AWS's instructions for deploying a django application using the ebcli
.
It is important to note, I think, that after running eb init
I am prompted to select a reigon, enter my credentials, and set my instance. Afterwhich I receive feedback that my application has been created. I checked the AWS console on the browser and I see nothing. Yes, I checked all regions.
I found out that after doing eb list
and eb status
that the environment wasn't actually created in the eb init
step so I referenced this answer: AWS Elastic Beanstalk : the command eb list shows no environments
Running eb create --single
allowed the application to upload and I could access via the link provided. However, this for some reason is not attached to the instances in my user and cannot see it in the browser. Why is it that I cannot see my application in the AWS console despite it existing and running currently?
Here is the output of eb status
Environment details for: ****
Application name: *****
Region: *****
Deployed Version: app-2ecd-200609_120851
Environment ID: e-wbqx6*****
Platform: arn:aws:elasticbeanstalk:ap-northeast-1::platform/Python 3.7 running on 64bit Amazon Linux 2/3.0.2
Tier: WebServer-Standard-1.0
CNAME: *****.elasticbeanstalk.com
Updated: 2020-**-** 03:18:12.491000+00:00
Status: Ready
Health: Green
Solution
Based on the comments.
The issue was the use of different account in eb cli
and aws console
.
The solution was to use the same account.
Answered By - Marcin
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.