dimanche 25 janvier 2015

AWS Option Settings

I have an app running on AWS ElasticBeanstalk. While trying to configure some app settings, I noticed that the optionsettings.<environment-name> was actually the file for a previous test app that I had running. Stupid me... I renamed the file, so that the environment name was a match for my current app and EC2 instance (I previously didn't have an optionsettings file) and ran eb update. Now I'm getting an Nginx 502 error and I'm not sure how to fix what I've done.


Is it possible to turn back environment settings and restore what I had before?


Here is what my file looks like:



[aws:autoscaling:asg]
Custom Availability Zones=
MaxSize=4
MinSize=1

[aws:autoscaling:launchconfiguration]
EC2KeyName=webserver
InstanceType=t1.micro

[aws:autoscaling:updatepolicy:rollingupdate]
RollingUpdateEnabled=false

[aws:ec2:vpc]
ELBScheme=public
ELBSubnets=
Subnets=
VPCId=

[aws:elasticbeanstalk:application]
Application Healthcheck URL=

[aws:elasticbeanstalk:application:environment]
NODE_ENV=production
PARAM1=production
PARAM2=
PARAM3=
PARAM4=
PARAM5=

[aws:elasticbeanstalk:container:nodejs]
GzipCompression=false
NodeCommand=
NodeVersion=0.10.26
ProxyServer=nginx

[aws:elasticbeanstalk:hostmanager]
LogPublicationControl=false

[aws:elasticbeanstalk:monitoring]
Automatically Terminate Unhealthy Instances=false

[aws:elasticbeanstalk:sns:topics]
Notification Endpoint=
Notification Protocol=email

Aucun commentaire:

Enregistrer un commentaire