Editing Troubleshooting Elastic Beanstalk Deployment (section)

=== eb deploy failure ===

* Run `eb logs` in the local distribution of the environment to view the latest commands run in the EBS environment.
** If `eb logs` generates a "permission denied" message, try `eb logs --instance [EBS-INSTANCE-ID] --verbose`
* View the tail of the file `/var/log/cfn-init-cmd.log`. This file will list all commands in `.ebextensions` and whether they executed successfully or not.
* Check the `.ebextensions` config files on the server in `/var/app/staging/`
* Confirm the domain settings in AWS Route 53.
* Confirm that the web files have been uploaded to `/var/www/html/`.
* Confirm the EBS raw URL to the site: '''AWS Console''' > '''Elastic Beanstalk''' > '''Environments''' > ''click on the URL for the environment in question''
* Scale back the application and incrementally deploy.
** Remove all web files except for a boilerplate "Hello, World" index file.
** Comment out all commands in `.ebextensions` configuration files. 
** Remove `composer.json`
** Run `eb deploy` to see if it can successfully upload this most basic environment. 
** Incrementally add back components of the application and redeploy to isolate problematic components.

==== Errors running `composer install` ====

This could be due to an expired GitHub personal access token. 

These tokens allow composer to pull from private GitHub repos. 

The token is stored in a file in an S3 bucket. The file is copied to the EBS server in one of the `.ebextensions` scripts and used to run composer. Look in that script for the expected location of the file.

If the token is expired, [https://github.com/settings/tokens generate a new one]. Save the token in a text file and upload it to the S3 bucket, overwriting the old token file.