Django Deploy ElasticBeanstalk AWS error creating Enviroment
Im trying to deploy my django application at EB since I failed with heroku
django.config file:
option_settings:
aws:elasticbeanstalk:container:python:
WSGIPath: store/wsgi.py
Note: My normal python Virtual Env the python Version is 3.9.12 but when i run
eb init -p python-3.9.12 store it doesent get recognized, even if i just set as: eb init -p python-3.9 store
so i did
eb init -p python-3.8 store
and it worked
Also at the full log, it choose atumatcally the region,how can i change that?
I ran
eb create store-env
Error Log:
2022-04-22 04:04:14 ERROR Instance deployment failed. For details, see 'eb-engine.log'.
2022-04-22 04:04:16 ERROR [Instance: i-0e999ebdfd96bb4d9] Command failed
on instance. Return code: 1 Output: Engine execution has encountered an error..
2022-04-22 04:04:16 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2022-04-22 04:05:19 ERROR Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
ERROR: ServiceError - Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
The full log:
Creating application version archive "app-220422_005816740583".
Uploading: [##################################################] 100% Done...
Environment details for: store-env
Application name: store
Region: us-west-2
Deployed Version: app-220422_005816740583
Environment ID: e-7rraydvprc
Platform: arn:aws:elasticbeanstalk:us-west-2::platform/Python 3.8 running on 64bit Amazon Linux 2/3.3.12
Tier: WebServer-Standard-1.0
CNAME: UNKNOWN
Updated: 2022-04-22 04:01:26.541000+00:00
Printing Status:
2022-04-22 04:01:24 INFO createEnvironment is starting.
2022-04-22 04:01:26 INFO Using elasticbeanstalk-us-west-2-106867183434 as Amazon S3 storage bucket for environment data.
2022-04-22 04:01:53 INFO Created security group named: sg-0e4b3b52e777dd497
2022-04-22 04:02:09 INFO Created load balancer named: awseb-e-7-AWSEBLoa-9REA8354CHEP
2022-04-22 04:02:09 INFO Created security group named: awseb-e-7rraydvprc-stack-AWSEBSecurityGroup-VUWM2UXZ4XOU
2022-04-22 04:02:09 INFO Created Auto Scaling launch configuration named: awseb-e-7rraydvprc-stack-AWSEBAutoScalingLaunchConfiguration-mQrjs7K2XQeV
2022-04-22 04:03:28 INFO Created Auto Scaling group named: awseb-e-7rraydvprc-stack-AWSEBAutoScalingGroup-GFXAXY7VO0ZB
2022-04-22 04:03:28 INFO Waiting for EC2 instances to launch. This may take a few minutes.
2022-04-22 04:03:28 INFO Created Auto Scaling group policy named: arn:aws:autoscaling:us-west-2:106867183434:scalingPolicy:c9dfd38e-a528-4dc5-9621-7b007044672c:autoScalingGroupName/awseb-e-7rraydvprc-stack-AWSEBAutoScalingGroup-GFXAXY7VO0ZB:policyName/awseb-e-7rraydvprc-stack-AWSEBAutoScalingScaleUpPolicy-1L62SHU7ZES3
2022-04-22 04:03:28 INFO Created Auto Scaling group policy named: arn:aws:autoscaling:us-west-2:106867183434:scalingPolicy:305220c7-21e2-499a-b5d2-7c6fb2c9e0ae:autoScalingGroupName/awseb-e-7rraydvprc-stack-AWSEBAutoScalingGroup-GFXAXY7VO0ZB:policyName/awseb-e-7rraydvprc-stack-AWSEBAutoScalingScaleDownPolicy-VVXX30WTR05F
2022-04-22 04:03:28 INFO Created CloudWatch alarm named: awseb-e-7rraydvprc-stack-AWSEBCloudwatchAlarmHigh-ITXMB86OXTIF
2022-04-22 04:03:28 INFO Created CloudWatch alarm named: awseb-e-7rraydvprc-stack-AWSEBCloudwatchAlarmLow-XP4TY532MOPY
2022-04-22 04:04:12 INFO Instance deployment successfully generated a 'Procfile'.
2022-04-22 04:04:14 ERROR Instance deployment failed. For details, see 'eb-engine.log'.
2022-04-22 04:04:16 ERROR [Instance: i-0e999ebdfd96bb4d9] Command failed
on instance. Return code: 1 Output: Engine execution has encountered an error..
2022-04-22 04:04:16 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2022-04-22 04:05:19 ERROR Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
ERROR: ServiceError - Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.