Tag Info

Hot answers tagged

5

This is clearly a bug in the software computing the traffic rate. You need to show the image to the vendor of the software, which produced the graph. That's the only way, you are going to get an answer as to what happened. Probably some negative number showed up where a positive number was expected, and wrapped around to around 18EB. Use that erroneous ...


4

'ssh port' in Amazon SG is just shortcut for tcp port 22. You should be perfectly ok with adding Custom TCP rule with whichever port you run your TCP on. As far as I'm aware, Amazon SG is purely layer 4 filter, so it doesn't care about what is actually protocol used.


2

The nginx executable file is probably not in your PATH environment variable. This variable is used by your shell to determine where executable files are located and executing the first if a match is found. Your init.d script gives a hint to the location of the executable: /usr/local/nginx/sbin/nginx. To get the version of nginx execute: ...


2

Simple - take a snapshot of your current RDS instance and then restore that snapshot to a new instance in your VPC.


2

You do not have an A record for example.com. You have an A record for *.example.com, in which example.com is not included. You will need two records.


1

Security group rules aren't able to be inherited by other groups. What you need to do is to create your sg-operators security group and then apply it to a group of instances directly, which you can easily do in a VPC (not in Classic). Background: Adding an allow rule for a security group to an existing security group means that the instances in the source ...


1

It's very possible whatever network your behind does not allow outbound connections to port 49153. One way to avoid this is to use the Java based client in your browser provided by Amazon.


1

Just go into your wp-config.php file and add the line define('RELOCATE',true); right above the line that says 'That's all! Stop editing!' Then login to WordPress at your NEW ip address. It will work fine. Then just go toSettings->General and update your site URL to the correct info. Be sure to scroll to the bottom and click Save. Your site will again ...


1

To deploy on EC2 you should create a standalone version of your application in your local machine using: play dist Then you copy the generated .zip to your EC2 instance using scp, unzip it using unzip. You would then want to run your application like so: sudo nohup yourAppName-version/bin/yourAppName -Dhttp.port=80 sudo in order to be able to bind to ...


1

As per my understanding, you need to modify your chef recipe (i.e. learn a bit of chef) to change PHP version installed. Else you would keep on running into issues and even if you install a different PHP version, chef would automatically try to revert it as this is what it is supposed to do.


1

Your server admin has basically transfered your sites from one data-center to another. You're thinking of EC2 instances as traditional servers. Now it's time to change your thinking. Think of EC2 instances as containers for your web applications, and even part of your web application, rather than simply something you host them on. Modularizing your websites ...


1

You need to configure the reverse DNS (PTR) records for your elastic IPs by filling out this form. Make sure your A records are correct or they will not create the PTR record.



Only top voted, non community-wiki answers of a minimum length are eligible