ec2

504 Gateway Timeout - Two EC2 instances with load balancer

匿名 (未验证) 提交于 2019-12-03 02:56:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: This might be the impossible issue. I've tried everything. I feel like there's a guy at a switchboard somewhere, twirling his mustache. The problem: I have Amazon EC2 running an application. It functions without issue when there is only one instance and no load balancer. But in my production environment I have two identical instances running behind one load-balancer and when performing certain tasks, like a feature that generates a PDF and attaches it to an email, nothing happens at all, and when using Google Developer tools with

Amazon EC2 Capacity & Workflow Questions

匿名 (未验证) 提交于 2019-12-03 02:52:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I’m hoping some of you with experience using amazon EC2 could offer some advice… of course it’ll be subjective which is fine, I’m pretty sure your guestimate would be better than mine. I am planning on moving all my client’s websites from shared hosting environments to Amazon EC2. They’re all pretty low traffic sites (the busiest site receives around 50 unique visitors a day). There’s about 8 sites, but I may expand this as I take on more projects and host more sites… current capacity planning is for say 12 sites. Each site runs on ASP.Net

How to connect to MongoDB EC2 instance

匿名 (未验证) 提交于 2019-12-03 02:50:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: we have an EC2 MongoDB 2.4 instance from Amazon MarketPlace. when i try to access it from my computer using the mongo command like so: mongo xx-xx-xx-xx-xx.compute-1.amazonaws.com i get the following error Error: couldn't connect to server xx-xx-xx-xx-xx.compute-1.amazonaws.com:27017 at src/mongo/shell/mongo.js:147 exception: connect failed i can connect to the remote instance using ssh so it is reachable. the port is the default port 27017. mongod is running and working on the remote instance. any suggestions on how to fix this? 回答1: As

Failure to launch Amazon EC2 non free instances

匿名 (未验证) 提交于 2019-12-03 02:50:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I need to launch a Amazon EC2 instance, in particular a GPU accelerated one. I already tried with free tiers using t2.micro instances and everything is fine. When I try to select a non free one such as g2.2xlarge I get this error Launch Failed You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit. (Service: AmazonEC2; Status Code: 400; Error Code: InstanceLimitExceeded; Request ID:

Java 8 application on EC2

匿名 (未验证) 提交于 2019-12-03 02:49:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I was wondering if anyone knows if it will be possible for me to install Java 8 on an EC2 instance. My application is packed as a fat jar with embedded jetty, so the Java 8 runtime alone should be sufficient. I'm not too familiar with Linux, and I saw that they only had Java 7 support on the default AMI. Is there a simple command I can run to update to Java 8? 回答1: Java 8 may not be available out-of-the-box on the AMI that you are looking for. However, you can always install it once the instance is created. e.g. Check this post which

Automount EBS volume in Amazon EC2 Windows Instance

匿名 (未验证) 提交于 2019-12-03 02:47:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: Does anyone know how to auto-mount an Elastic Block Storage (EBS) volume when starting a Windows 2003 instance in Amazon's Elastic Compute Cloud (EC2)? 回答1: Setup: Make sure the EBS volume is formatted and labeled (in the example I used the label PDRIVE). Setup a drive mapping using Ec2ConfigServiceSettings.exe Install Java on the instance Install the EC2 API command line tools Install a copy of your cert and private key Install a copy of curl.exe (open source tool) You can use the group policy editor to set this script as your

Running EC2 instance suddenly refuses SSH connection

匿名 (未验证) 提交于 2019-12-03 02:46:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I've set up the EC2 instance couple days ago and even last night I was able to SSH to it with no problems. Today morning, I can't ssh to it. Port 22 is already open in the security group and I haven't changed anything since last night. Error: ssh: connect to host [ip address] port 22: Connection refused I had similar issue recently and i couldn't figure out why it was happening, so I had to create a new instance, set it up again, and connect and configure all EBS storages to the new one. Took me couple hours... and now it's happening again.

EC2 API Error validating access credential

匿名 (未验证) 提交于 2019-12-03 02:45:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I installed the ec2 api following the amazon guide. I setted up the access id and secret as environment variable. Here it is my profile: export AWS_ACCESS_KEY=XXXXX export AWS_SECRET_KEY=XXXXXX export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre export EC2_HOME=/usr/local/ec2/ec2-api-tools-1.7.1.0 export PATH=$PATH:$EC2_HOME/bin Everythings looks configured as asked, but i can't connect to aws. Here the output of the command ec2-describe-regions in verbose mode: Client.AuthFailure: AWS was not able to validate the provided access

Amazon ec2 user-data, how does it work?

匿名 (未验证) 提交于 2019-12-03 02:45:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: We are starting instances, and accessing the user-data we place. But does anybody understand the internals of this operation (from Amazon's side)? When we pass in the user-data, at what point is that data transmitted to the VM (is this a Xen feature) and where is it stored? I first thought, it was set as the USER_DATA env var, but we can also pass it as a file. Where is that file stored? Is it generic to all instances or varies depending on AMI? This is not a problem per se, just wanted to know how Amazon does this. User data screenshot:

How to access/ping a server located on AWS?

匿名 (未验证) 提交于 2019-12-03 02:44:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: With what address should a server located on AWS be accessed? I've created an AWS instance and installed a web server on it. However the server is not reachable via any of the: ec2-174-129-24-92.compute-1.amazonaws.com the IP address from instance's ifconfig an elastic IP address I've created on the AWS dashboard and associated with the instance Surprisingly, ssh with root@ec2-174-129-24-92.compute-1.amazonaws.com works fine. What might be the problem and how to bind an address to the instance? 回答1: In your security group open -1 to -1 on