ykdojo / editdojo2

This used to be Edit Dojo's private repo - now it's public.

Home Page:https://www.csdojo.io/edit

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

YK: Learn how to set this up on AWS

ykdojo opened this issue · comments

commented

This is just a learning task.

commented

For now, I used this to install Python 3.6 alongside 3.7 on my Mac.

commented

NOTE: I'm working on the aws-setup-yk branch for this.

commented

Ran:

eb init -p python-3.6 editdojo

eb create

eb status

following: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-django.html#python-django-deploy

But I'm still getting the error: Stack named 'awseb-e-thtmzcravi-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBV2LoadBalancer, AWSEBSecurityGroup].

commented

@Jonathantsho did you have an issue like this too?

@Jonathantsho did you have an issue like this too?

I followed the same tutorial as well! I did not have the same issue.
Have you tried running eb init again after you ran eb init -p python-3.6 editdojo?
This setups up your ssh keys. I don't think it ties into the error, but could be worth a shot.

For EB create, did you select classic for the load balancers?

I also did this within the pipenv shell. Maybe that could be a factor as well.
If all else fails, make sure your CLI is up to date, and your IAM role allows for creating elastic beanstalk applications.

Check the elastic beanstalk console within AWS as well. The recent events/logs should give you good information as to why the app is CREATE_FAILED.

If this is confusing, let me know i'll share screen and we can walk through it.

I just set up AWSServiceRoleForElasticBeanstalk on AWS's IAM console.

Reference links:
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-django.html#python-django-deploy
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html
https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys

(I was trying to run eb init -p python-3.6 editdojo)

I haven't used the EB CLI before, but you have setup your access keys / secret access keys in the credential configuration correct?

-For the User in the IAM setup, check if you have the policy for elastic beanstalk access. I've given myself administrator access in the permissions policies to not worry about permissions.

This I think should be the biggest be the most likely solution.

commented

This worked when I gave my user AdministratorAccess. Thanks!!

image

commented

Twitter login is still not working: http://editdojo-dev2.us-west-1.elasticbeanstalk.com/

commented

Closing this issue because we're going to go with Heroku at the beginning. Will revisit this if we want to switch to AWS in the future.