I want to create an Elastic Beanstalk configuration that allows me to deploy a .NET Windows Service but without deploying a web application. 

I have just read [this blog post][1] which explains how to use .ebextensions to deploy a Windows Service alongside your web application, but is there a scenario for which the .ebextensions can be run without deploying a Web Deploy package for a web application?

Is my only option to create an empty web application that contains the .ebextensions directory and then deploy the Web Deploy package?

The Elastic Beanstalk FAQ mentions the ability to deploy non-web applications ([here][2]) and I have found a similar (unanswered) question on the AWS developer forums ([here][3]).

&lt;h3&gt;Update&lt;/h3&gt;

Due to the lack of activity on this question and my inability to find any other information on the internet, I just assumed that the answer to this question is &quot;No&quot; (at least for now). 

I ended up creating an empty web application and used that to deploy my Windows Service via the .ebextensions YAML config.

As a side note, I&#39;d like to highlight [this page from Amazon&#39;s documentation][4] which I found to be a very helpful guide to creating those special config files.

&lt;h3&gt;Another Update&lt;/h3&gt;
After implementing the approach mentioned above, I discovered that Elastic Beanstalk was not executing my `.ebextensions` scripts for new Beanstalk instances. As a result, the Windows Service failed to be installed when new instances were created. I had to jump through several more hoops to finally arrive at a scalable solution. Please let me know if you want the details of the final solution. &lt;br&gt;&lt;br&gt;
Ultimately, it just seems like Elastic Beanstalk wasn&#39;t meant for deploying scalable Windows Services.


----------


&lt;h3&gt;Basic Solution&lt;/h3&gt;
I&#39;m not comfortable releasing the source code since it was not for a personal project, but here is the basic structure of my current deployment solution:


1.  A custom EC2 AMI contains a &#39;bootstrap&#39; program that runs on startup. The program does the following:
&lt;br/&gt;  1.1.  [Download a &#39;zip&#39; archive][5] from a (configurable) &#39;deployment&#39; S3 bucket
&lt;br/&gt;  1.2.  Extract the downloaded zip file to a temporary directory
&lt;br/&gt;  1.3.  An &quot;install.bat&quot; script is located/executed  (the name of the script is also configurable). This script installs and starts the windows service.
2.  The Elastic Beanstalk &quot;Instance AMI&quot; is set to the custom AMI with the bootsrap program (see: [this article][6])

To deploy new code: upload the installation .zip archive (that contains the windows service and install.bat file) to the S3 bucket and terminate all EC2 instances for the Elastic Beanstalk application. As the instances are re-created the bootstrapping program will download/install the newly updated code.

Of course, if I were starting over, I would just skip using Elastic Beanstalk and use the standard AWS auto-scaling along with a similar deployment scheme. **The bottom line** is that if you don&#39;t have a web application, don&#39;t use Elastic Beanstalk; you&#39;re better off with the standard AWS auto-scaling.

&lt;h3&gt;New AWS Deployment Tools&lt;/h3&gt;

Amazon recently announced several new code deployment/management services that seem to address deployment issues: http://aws.amazon.com/blogs/aws/code-management-and-deployment/

I have yet to use these new services (I&#39;m not even sure if they&#39;ve been released yet), but they look promising.

  [1]: http://blogs.aws.amazon.com/net/post/Tx1RLX98N5ERPSA/Customizing-Windows-Elastic-Beanstalk-Environments-Part-1
  [2]: http://aws.amazon.com/elasticbeanstalk/faqs/#supported-applications
  [3]: https://forums.aws.amazon.com/message.jspa?messageID=416932
  [4]: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-windows-ec2.html
  [5]: http://docs.aws.amazon.com/AmazonS3/latest/dev/RetrievingObjectUsingNetSDK.html
  [6]: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.customenv.html

Deploy a .NET Windows Service with Amazon Elastic Beanstalk with no Web Application

We have a fairly simple node.js app, but due to AWS Elastic Beanstalk deployment mechanism, it takes about 5 minutes to roll-out a new version (via `git aws.push`) even after a single file commit.

I.e. the commit itself (and upload) is fast (only 1 file to push), but then Elastic Beanstalk fetches whole package from S3, unzips it and runs `npm install`, which causes node-gyp to compile some modules. Upon installation/building completion, Elastic Beanstalk wipes `/var/app/current` and replaces it with the new app version.

Needless to say, constant node_modules rebuilding is not necessary, and rebuilding that takes 30 seconds on my old Macbook Air, takes &gt;5 mins on a ec2.micro instance, not fun.

I see two approaches here:

 1. tweak `/opt/containerfiles/ebnode.py` and play with node_modules location to avoid its removal and rebuilding upon deployment. 
 2. set up a git repo on Elastic Beanstalk EC2 instance and basically re-write deployment procedure ourselves, so /var/app/current receives pushes and runs `npm install` only when necessary (which makes Elastic Beanstalk to look like OpsWorks..)

Both options lack grace and are prone to issues when Amazon updates their Elastic Beanstalk hooks and architecture.

Maybe somebody has a better idea how to avoid constant rebuilding of node_modules that are already present in the app dir? Thank you.

avoid rebuilding node_modules in elastic beanstalk

I use Celery with RabbitMQ in my Django app (on Elastic Beanstalk) to manage background tasks and I daemonized it using Supervisor.
The problem now, is that one of the period task that I defined is failing (after a week in which it worked properly), the error I&#39;ve got is:

```python
[01/Apr/2014 23:04:03] [ERROR] [celery.worker.job:272] Task clean-dead-sessions[1bfb5a0a-7914-4623-8b5b-35fc68443d2e] raised unexpected: WorkerLostError(&#39;Worker exited prematurely: signal 9 (SIGKILL).&#39;,)
Traceback (most recent call last):
  File &quot;/opt/python/run/venv/lib/python2.7/site-packages/billiard/pool.py&quot;, line 1168, in mark_as_worker_lost
    human_status(exitcode)),
WorkerLostError: Worker exited prematurely: signal 9 (SIGKILL).
```

All the processes managed by supervisor are up and running properly (`supervisorctl status` says _RUNNNING_).

I tried to read several logs on my ec2 instance but no one seems to help me in finding out what is the cause of the `SIGKILL`. What should I do? How can I investigate?

These are my **celery settings**:

```python
CELERY_TIMEZONE = &#39;UTC&#39;
CELERY_TASK_SERIALIZER = &#39;json&#39;
CELERY_ACCEPT_CONTENT = [&#39;json&#39;]
BROKER_URL = os.environ[&#39;RABBITMQ_URL&#39;]
CELERY_IGNORE_RESULT = True
CELERY_DISABLE_RATE_LIMITS = False
CELERYD_HIJACK_ROOT_LOGGER = False
```

And this is my **supervisord.conf**:

```conf
[program:celery_worker]
environment=$env_variables
directory=/opt/python/current/app
command=/opt/python/run/venv/bin/celery worker -A com.cygora -l info --pidfile=/opt/python/run/celery_worker.pid
startsecs=10
stopwaitsecs=60
stopasgroup=true
killasgroup=true
autostart=true
autorestart=true
stdout_logfile=/opt/python/log/celery_worker.stdout.log
stdout_logfile_maxbytes=5MB
stdout_logfile_backups=10
stderr_logfile=/opt/python/log/celery_worker.stderr.log
stderr_logfile_maxbytes=5MB
stderr_logfile_backups=10
numprocs=1

[program:celery_beat]
environment=$env_variables
directory=/opt/python/current/app
command=/opt/python/run/venv/bin/celery beat -A com.cygora -l info --pidfile=/opt/python/run/celery_beat.pid --schedule=/opt/python/run/celery_beat_schedule
startsecs=10
stopwaitsecs=300
stopasgroup=true
killasgroup=true
autostart=false
autorestart=true
stdout_logfile=/opt/python/log/celery_beat.stdout.log
stdout_logfile_maxbytes=5MB
stdout_logfile_backups=10
stderr_logfile=/opt/python/log/celery_beat.stderr.log
stderr_logfile_maxbytes=5MB
stderr_logfile_backups=10
numprocs=1
```

---

## Edit 1

After restarting **celery beat** the problem remains.

## Edit 2

Changed `killasgroup=true` to `killasgroup=false` and the problem remains.


Celery: WorkerLostError: Worker exited prematurely: signal 9 (SIGKILL)

I am trying to access an environment variable that I have defined in the AWS Beanstalk configuration. I need to access it within a config file in `.ebextensions` _or_ in a file that is copied in place in a config file. I have tried the following:

    container_commands:
      update_nginx_config:
        command: &quot;cp .ebextensions/files/nginx/nginx.conf /etc/nginx/nginx.conf&quot;

And in my `nginx.conf` file, I have tried to access `$MYVAR`, `${MYVAR}` and `{$MYVAR}`, some of which was suggested [here][1] and [here][2] (the latter being directly within a config file).

    files:
      &quot;/etc/nginx/nginx.conf&quot; :
        mode: &quot;000644&quot;
        owner: root
        group: root
        content: |
          $MYVAR ${MYVAR} {$MYVAR}

This does not work either. In all cases, the variable names are just output such as `$MYVAR`, so Beanstalk does not recognize my variables. I found the below in the [AWS documentation][3] about `container_commands`:

&gt; They also have access to environment variables such as your AWS
&gt; security credentials.

This is great, but it does not say _how_.

How can I access an environment variable with ebextensions, be it within a config file itself or in a separate file that is copied in place?

Thank you in advance!


  [1]: https://forums.aws.amazon.com/thread.jspa?messageID=529504
  [2]: https://stackoverflow.com/questions/16585898/referencing-env-variables-from-elastic-beanstalk-ebextensions-config-files
  [3]: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html#customize-containers-format-container_commands

Accessing environment variables in AWS Beanstalk ebextensions

I have a rest api running on Elastic Beanstalk, which works great. Everything application-wise is running good, and working as expected.

The application is a rest api, used to lookup different users.

    example url: http://service.com/user?uid=xxxx&amp;anotherid=xxxx

If a user with either id&#39;s is found, the api responds with `200 OK`, if not, responds with `404 Not Found` as per. `HTTP/1.1` status code defenitions.

It is not uncommon for our api to answer `404 Not Found` on a lot of requests, and  the elastic beanstalk transfers our environment from `OK` into `Warning` or even into `Degraded` because of this. And it looks like `nginx` has refused connection to the application because of this degraded state. (looks like it has a threshold of 30%+ into `warning`and 50%+ into `degraded` states. This is a problem, because the application is actually working as expected, but Elastic Beanstalks default settings *thinks* it is a problem, when it&#39;s really not.

Does anyone know of a way to edit the threshold of the 4xx warnings and state transitions in EB, or completely disable them?

Or should i really do a symptom-treatment and stop using `404 Not Found` on a call like this? (i really do not like this option)

Elastic Beanstalk disable health state change based on 4xx responses

What are the exact differences between EC2, Beanstalk and LightSail in AWS?

What are good real time scenarios in which I should use these services?

AWS - What are the exact differences between EC2, Beanstalk and LightSail?

I am able to check out an entire `svn` repository using the following command: 

    svn co https://myaccount.svn.beanstalkapp.com/myapp/

But I cannot figure out the command to commit a single file. If I make to change to `myapp/page1.html`. 

How can I check in just that one file?

How can I commit a single file using SVN over a network?

When we setup Elastic Beanstalk extensions in .ebextensions

I wonder what is the difference between `commands` and `container_commands` in Beanstalk configuration file keys.

My command is like this

    container_commands:
      04_insert_app:
        command: &quot;cat .ebextensions/insertapp_job.txt &gt; /etc/cron.d/insertapp_job &amp;&amp; chmod 644 /etc/cron.d/insertapp_job&quot;
        leader_only: true

container_commands works fine.

commands: has error `.ebextensions/insertapp_job.txt` not found

What is the difference between commands and container_commands configuration keys in Beanstalk?

Is there any difference if i use one space, two or four spaces per indent level in **YAML**?

Are there any specific rules for space numbers per Structure type??

For example **4** spaces for nesting **maps** , **1** space per **list item** etc??


I am writing a yaml configuration file for elastic beanstalk .ebextensions and i am having really hard time constructing this correctly. Although i have valid yaml in [YAML Validator][1] elastic beanstalk seems to understand a different structure.


  [1]: http://www.yamllint.com/

YAML How many spaces per indent?

I get the following error when deploying to EB:

&gt; ERROR: You cannot have more than 500 Application Versions. Either
&gt; remove some Application Versions or request a limit increase.

I went manually and deleted some versions.
I don&#39;t want deploys to fail because of this limit. 
Is there a way in Elastic Beanstalk to auto-evict unused versions? 

cannot deploy - ERROR: You cannot have more than 500 Application Versions

I&#39;m running into **&quot;413 Request Entity Too Large&quot;** errors when posting files larger than 10MB to our API running on AWS Elastic Beanstalk.

I&#39;ve done quite a bit of research and believe that I need to up the **client_max_body_size** for Nginx, however I cannot seem to find any documentation on how to do this using Elastic Beanstalk. My guess is that it needs to be modified using an ebetension file.

Anyone have thoughts on how I can up the limit? 10MB is pretty weak, there has to be a way to up this manually.

Increasing client_max_body_size in Nginx conf on AWS Elastic Beanstalk

I have developed a .NET MVC application and have started playing around with AWS and deploying it via the Visual Studio Toolkit. I have successfully deployed the application using the Elastic Beanstalk option in the toolkit.

As I was going over the tutorials for deploying .NET apps to AWS with the toolkit, I noticed there are tutorials for deploying with [both Elastic Beanstalk and CloudFormation](http://aws.amazon.com/visualstudio/). What is the difference between these two? 

From what I can tell, it seems like they both essentially are doing the same thing - making it easier to deploy your application to the AWS cloud (setting up EC2 instances, load balancer, auto-scaling, etc). I have tried reading up on them both, but I can&#39;t seem to get anything other than a bunch of buzz-words that sound like the same thing to me. I even found an [FAQ](http://aws.amazon.com/cloudformation/faqs/#3) on the AWS website that is supposed to answer this exact question, yet I don&#39;t really understand.

Should I be using one or the other? Both?

What is the difference between Elastic Beanstalk and CloudFormation for a .NET project?

The Amazon Elastic Beanstalk blurb says:

&gt; Elastic Beanstalk lets you &quot;open the hood&quot; and retain full control  ...  even pass environment variables through the Elastic Beanstalk console.

[http://aws.amazon.com/elasticbeanstalk/][1]

  [1]: http://aws.amazon.com/elasticbeanstalk/

How to pass other environment variables besides the one in the Elastic Beanstalk configuration?

How do you pass custom environment variable on Amazon Elastic Beanstalk (AWS EBS)?

What are the advantages we get by using Elastic Beanstalk over maually creating EC2 instance and setting up tomcat server and deploy etc for a typical java web applicaion. Are load balancing, Monitoring and autoscaling the only advantages?

Suppose for my web application which uses database I installed the database in the EC2 instance itself. When Autoscalling takes place will the database gets created in the newly created instance or it will be accessing the database I created in the master instance... If it creates just a replica when autoscaling happens how will be data sync happens between the instances?

Manual deployment vs. Amazon Elastic Beanstalk

I&#39;m running into this problem trying to link my **Godaddy domain** with an **AWS Elastic Beanstalk instance**. I found a lot of documentation on how to link an **EC2 instance** with a domain on Godaddy but not for Elastic Beanstalk instance. So I ended up with this URL: `www.MY_SITE.elasticbeanstalk.com`

Here is what I did for an EC2 instance:

 1. I updated the **Nameservers** on my Godaddy domain with the ones from my **Route 53 Hosted Zone**.
 2. I created a new **Elastic IP** on the EC2 console.
 3. I went back to Godaddy and updated the **DNS A @** field from their DNS Manager, with the EC2 Elastic IP one.
 4. You normally have to wait 1h to 48h and it should work.

How can I do the same for a AWS Elastic Beanstalk instance, not an EC2 one? I can&#39;t see the instance I created from my EC2 console in order to link it to an Elastic IP.

Hope this is clear enough.. Any help?

How to link godaddy domain with AWS Elastic Beanstalk environment?

When you setup an Auto Scaling groups in AWS EC2 `Min` and `Max` bounds seem to make sense:

* The minimum number of instances to scale down to based on policies
* The maximum number of instances to scale up to based on policies

However, I&#39;ve never been able to wrap my head around what the heck `Desired` is intended to affect.

I&#39;ve always just set `Desired` equal to `Min`, because generally, I want to pay Amazon the minimum tithe possible, and unless you need an instance to handle load it should be at the `Min` number of instances.

I know if you use `ElasticBeanstalk` and set a `Min` to 1 and `Max` to 2 it sets a `Desired` to 2 (of course!)--you can&#39;t choose a value for `Desired`.

What would be the use case for a different `Desired` number of instances and how does it differ?  When you expect AWS to scale lower than your `Desired` if desired is larger than `Min`?


AWS EC2 Auto Scaling Groups: I get Min and Max, but what&#39;s Desired instances limit for?

I would like to know if there is a way to setup a cronjob/task to execute every minute. Currently any of my instances should be able to run this task.

This is what I have tried to do in the config files without success:

    container_commands:
      01cronjobs:
        command: echo &quot;*/1 * * * * root php /etc/httpd/myscript.php&quot;

I&#39;m not really sure if this is the correct way to do it

Any ideas?


AWS Elastic Beanstalk, running a cronjob

I&#39;ve developed a Docker based application comprised of multiple microservices. It has to consume Amazon SQS messages and processes them. At first I wanted to use AWS Elastic Beanstalk, but then I fell over the EC2 Container Service. Now I don&#39;t know which one to choose.

As of now, Elastic Beanstalk supports Multi-Container-Environments. That&#39;s great because every microservice has its own application server inside a docker container. The next problem is scaling:

I don&#39;t know how the scaling mechanism works. For example: I have 5 docker containers in my Elastic Beanstalk Environment. Now only the fifth docker container is under heavy load, because it has a huge amount of SQS messages to process, the other four are nearly idle, because they don&#39;t need much CPU or maybe don&#39;t have a lot of SQS messages. Let&#39;s assume the 5th container runs a JBoss application server. As far as i know, the server only can consume a limited amount of parallel requests even if there is enough CPU/memory available.

If the JBoss Docker container isn&#39;t able to handle the amount of requests, but there is enough CPU/memory available, of course I want to automatically start a second Docker/JBoss container on the same instance. But what happens, if I don&#39;t have enough CPU/memory? Of course I want to spin on a second instance, which is configurable through a auto-scaling group in EB. Now a second instance spins up, but every container except of the 5th is nearly idle, of course I don&#39;t want them to spawn 4 unnecessary at the second instance too, which would be a waste of resources. Only the 5th should spawn and the others should scale like the 5th scale based on configurable parameters like e.g.: CPU/memory/SQS. 

I don&#39;t exactly know if Amazon ECS is doing that, or if it&#39;s possible at all, but I really can&#39;t find any source on the internet about this topic, which is in general said, scaling based on instances/containers.

Should I use AWS Elastic Beanstalk or the Amazon EC2 Container Service (ECS) to scale Docker containers?

I would like to know what are the advantages and disadvantages of using AWS OpsWorks vs AWS Beanstalk and AWS CloudFormation?

I am interested in a system that can be auto scaled to handle any high number of simultaneous web requests (From 1000 requests per minute to 10 million rpm.), including a database layer that can be auto scalable as well.

Instead of having a separate instance for each app, Ideally I would like to share some hardware resources efficiently. In the past I have used mostly an EC2 instance + RDS + Cloudfront + S3

The stack system will host some high traffic ruby on rails apps that we are migrating from Heroku, also some python/django apps and some PHP apps as well.

Thanks in advance.

AWS OpsWorks vs AWS Beanstalk vs AWS CloudFormation?

I can&#39;t seem to force https on the free usage tier of elastic beanstalk.

I have tried the following suggestion at https://stackoverflow.com/questions/6858492/how-to-force-https-on-amazon-elastic-beanstalk-without-failing-the-health-check

Using this Apache rewrite rule

    RewriteEngine On
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteCond %{REQUEST_URI} !^/status$ 
    RewriteCond %{REQUEST_URI} !^/version$ 
    RewriteCond %{REQUEST_URI} !^/_hostmanager/ 
    RewriteRule . https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

When I try that, http requests do not get redirected to https as I would like. Instead, the http page loads normally. I&#39;ve also tried to use the X-Forwarded-Port header with the same result. 

I&#39;ve also tried the following rewrite rule

    RewriteCond %{SERVER_PORT} 80
    RewriteRule . https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

And this rule causes a redirect loop. So it would seem that the apache rewrite rules don&#39;t pick up the Elastic Load Balancer headers X-Forwarded-Port and  X-Forwarded-Proto, but also a redirect loop isn&#39;t what I am going for either.

Please help. I am new to AWS, Elastic Beanstalk, and not very familiar with Apache rules. I am not too sure where to go from here. Thanks.

How to force https on elastic beanstalk?

From an architecture perspective I&#39;m trying to get a better understand of how and where files deployed to eb (t2) server are stored.

I see some .zip files in s3 that show when I upload something via the eb interface, though how/where exactly does this get end up on my ec2(t2) server?




Where does elastic beanstalk t2 server store my node.js app files?

I implemented a REST api in django with django-rest-framework and used oauth2 for authentication.

I tested with:

    curl -X POST -d &quot;client_id=YOUR_CLIENT_ID&amp;client_secret=YOUR_CLIENT_SECRET&amp;grant_type=password&amp;username=YOUR_USERNAME&amp;password=YOUR_PASSWORD&quot; http://localhost:8000/oauth2/access_token/

and

    curl -H &quot;Authorization: Bearer &lt;your-access-token&gt;&quot; http://localhost:8000/api/

on localhost with successful results consistent with the documentation.

When pushing this up to an existing AWS elastic beanstalk instance, I received:

    { &quot;detail&quot; : &quot;Authentication credentials were not provided.&quot; }



Authorization Credentials Stripped --- django, elastic beanstalk, oauth

Deployment of a Node.js application (Node 6, npm 5) to Beanstalk fails with:

&gt; gyp ERR! stack Error: EACCES: permission denied, mkdir
&gt; &#39;/tmp/deployment/application/node_modules/heapdump/build&#39;

though the error is not package-specific, any node-gyp call fails.

The ERROR event in the AWS Console reads:

&gt; [Instance: i-12345] Command failed on instance. Return
&gt; code: 1 Output:
&gt; (TRUNCATED).../opt/elasticbeanstalk/containerfiles/ebnode.py&quot;, line
&gt; 180, in npm_install raise e subprocess.CalledProcessError: Command
&gt; &#39;[&#39;/opt/elasticbeanstalk/node-install/node-v6.10.0-linux-x64/bin/npm&#39;,
&gt; &#39;--production&#39;, &#39;install&#39;]&#39; returned non-zero exit status 1. Hook
&gt; /opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh failed. For more
&gt; detail, check /var/log/eb-activity.log using console or EB CLI.

and `eb-activity.log` contained the aforementioned npm error.

The application was deployed manually by uploading a .zip file that did not include `node_modules`. I.e. it was not deployed via the `eb` command-line tool.

Beanstalk: Node.js deployment - node-gyp fails due to permission denied

I want to shut down the app servers while I upgrade the database.  

Is there a way to pause or stop the app servers without terminating/destroying the environment?

Can I just go to the Elastic Beanstalk load balancer and change that temporarily without any issues or consequences to the Elastic Beanstalk configurations or the way it manages its servers?

Pause an Elastic Beanstalk app environment?

I&#39;ve noticed some Elastic Beanstalk is drawing about $20 to $30 every month on my AWS account and it turns out it is an empty S3 bucket.

I tried deleting it but it returns &quot;Access Denied&quot; error.

[![Access Denied][1]][1]


I also tried to use life cycle to remove it, but it also didn&#39;t work. Here is how I set up the life cycle:

[![Life Cycle][2]][2]

I set it to remove 1 day after creation

[![enter image description here][3]][3]


  [1]: http://i.stack.imgur.com/M5a5i.png
  [2]: http://i.stack.imgur.com/F8C3T.png
  [3]: http://i.stack.imgur.com/4u7k8.png

How to fix &#39;Access Denied&#39; while deleting empty S3 Elastic Beanstalk?

I have a elastic beanstalk linux-tomcat ami instance with the sample application installed and working off the public dns. I&#39;m able to ssh into the
 instance but cannot find where tomcat 7 lives (ie. the conf directory to edit server.xml). I&#39;ve tried this with a 64 and 32 bit ami. Any ideas on where I might find this? I looked under:

    /etc
    /usr/share

I did find a `elasticbeanstalk-tomcat7-deployment` file under `tmp` (was empty).

I did a:

    sudo yum install tomcat7

and the sample application is also being served up from `:8080` and working on the public DNS. So I (think) have 2 tomcat servers running on the same beanstalk instance. In that case, I&#39;m trying to find where the Tomcat 7 folders are (serving pages on port `80`).

Where can I find the Tomcat 7 installation folder on Linux AMI in Elastic Beanstalk?

What is the difference between EC2 and Beanstalk? I want to know regarding SaaS, PaaS and IaaS.

To deploy a web application in Wordpress I need a scalable hosting service. If there anything better than my purpose, please let me know as well.

FYI - I want to host and deploy multiple Wordpress and Drupal sites. 

I do not want to give more time for the server and focus on development. But the cloud hosting needs to be auto scalable. 

Difference between Amazon EC2 and AWS Elastic Beanstalk

I would like to switch off Elastic Load Balancer (ELB) for my Elastic Beanstalk environment. 

Currently I don&#39;t need it and I don&#39;t want to pay for it. 

It is possible to delete the ELB in EC2 managment window but then Elastic Beanstalk health state is switched from GREEN to RED.
I just found a [information][1] that it&#39;s not possible.

Does someone has a trick how to run Elastic Beanstalk without load balancing and have environment GREEN health state?

  [1]: https://forums.aws.amazon.com/thread.jspa?threadID=63622

Elastic Beanstalk without Elastic Load Balancer

I deployed an app using elastic beanstalk to my personal AWS account..Now I want to change the AWS credentials so the eb cli knows to deploy to a different account. But it does not ask me for the AWS keys when I type &quot;eb init&quot;. Where do I specify this?

How to change the AWS account using the Elastic Beanstalk CLI

I just signed up for Amazon&#39;s new Elastic Beanstalk offering. What I can&#39;t figure out is how to SSH to a Beanstalk instance. I don&#39;t have a private key because Beanstalk generated the instance on my behalf.

SSH to Elastic Beanstalk instance

I&#39;ve got a Node.js powered site that I&#39;m running on Amazon Elastic Beanstalk.

My Node.js app listens on port 8080, and I&#39;m using the nginx elastic load balancer configuration with my EB app, listening on port 80 and 443 for HTTP and HTTPS. 

However, I only want to accept traffic in my app that has come via HTTPS.

I could rig something up in the app to deal with this, but am interested in a way to get the load balancer to redirect all HTTP requests to my site via HTTPS.

All Amazon Elastic-Beanstalk Solutions on Gang of Coders

Total of 31 Amazon Elastic-Beanstalk Solutions