amazon-elastic-beanstalk

问题 So I had a very long post related to deployment of an elixir app to Elastic Beanstalk (here: HTTP 500 Deploying Elixir/Phoenix to AWS Elastic Beanstalk). I've finally boiled the problem to my NGINX being misconfigured to route traffic. It's posting this: 2017/11/18 00:52:45 [error] 2811#0: *15 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.25.36, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:4000/", host: "172.31.17.239" I've looked

问题 For context, I essentially followed this guide to get my rails app set up: https://medium.com/@jatescher/how-to-set-up-a-rails-4-2-app-on-aws-with-elastic-beanstalk-and-postgresql-3f9f29c046e2 My app is now running on AWS: http://ems-heroes-dev.elasticbeanstalk.com/ 64bit Amazon Linux 2015.03 v2.0.1 running Ruby 2.2 (Puma) However, I can't get any of my assets to load. Here is my config/environments/production.rb: EmsHeroes::Application.configure do config.cache_classes = true config.eager

问题 I created a CodeBuild Project that uses a docker image for node8. The purpose of this CodeBuild project is to do unit testing. It takes an input artifact from CodeCommit. And in the buildspec.yml it runs a test command. This is my (simple) buildspec file: version: 0.2 phases: install: commands: - echo "install phase started" - npm install - echo "install phase ended" pre_build: commands: - echo "pre_build aka test phase started" - echo "mocha unit test" - npm test - echo "mocha unit test

问题 I have a domain for instance example.com . The domain is hosted by a third party service (Digital Ocean). I would like to give control of a subdomain to AWS. So I would like to point aws.example.com to AWS. Once the root subdomain is pointed to AWS. I would like to use Route 53 to setup the following functionality: aws.example.com => alias to eb my-production-eb dev.aws.example.com => alias to eb my-dev-eb stage.aws.example.com => alias to eb my-stage-eb Is this possible? Do I have to point

问题 Newbie to AWS, I have a t2.micro EC2 instance supporting my Elastic Beanstalk application. It was created while I deployed my WAR file to Elastic Beanstalk. My EB application does not need to run 24 hrs a day so it only needs to work during a specific period of time a day. When I tried to stop it from the AWS EC2 management console by selecting "Actions -> Instance state -> Stop", the instance was terminated instead but a new instance was created and initialized and then running automatically

问题 After running pip install --upgrade awsebcli I get the following error when trying to do eb deploy Could not push code to the CodeCommit repository: ERROR: CommandError - An error occurred while handling git command. Error code: 128 Error: fatal: 'codecommit-origin dev' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. I can't figure out why that happened. It seems like the

问题 So for reasons Id rather not go into, my DB is on an EC2 instance in eu-west-1 and I have created a beanstalk app on us-east-1. Id like my app to talk to that EC2 instance on a MySQL port (3306). Can anyone assist with how Id set this up, what ingress rules I need to setup on the EC2 security group? Given that I will have multiple versions of the app in beanstalk, the IP address may change regularly (after environment rebuilds etc). 回答1: The important concept regarding Security Group Rules

问题 I want to deploy my web app to elastic beanstalk but it appears to only support Go 1.4 rather than Go 1.6. Is there a way to get a custom image? The reason I want 1.6 is because it supports vendoring and my web app depends on 3rd party packages. 回答1: The best choice would be to use docker. Here are the steps to deploy your application to Elastic Beanstalk: Choose the Generic Docker platform when creating a new environment. Put a file named Dockerfile in your project root with the following

问题 I am trying to add an HTTPS listener to my EBS classic load balancer. I used the CLI upload-certificate tool to upload my cert (using the GUI never resulted in the cert showing up as an option on the load balancer form. No errors, logs, events). I setup the listener according to AWS docs. For Listener port, type the incoming traffic port, typically 443. For Listener protocol, choose HTTPS. For Instance port, type 80. For Instance protocol, choose HTTP. For SSL certificate, choose your

问题 I need to pass some arguments to my docker build command. I understand that this can be done using the ARG instruction within the Dockerfile . Now assuming I have the following in my Dockerfile . ARG myvar and use the command docker build --build-arg mvar=myOwnVar ... , this would work. However, I am using AWS Elastic Beanstalk with Docker to build an image and deploy it in a container. So the questions are, Is this possible at all? If, yes how can I ensure that AWS EB passes values to these