Tag Info

Hot answers tagged

1

Second option is to replace a lost key pair on an EC2 instance as long as it's an EBS backed instance. The following link may help: replace-lost-keypair


1

Be sure to either add another user to sudoers first or set a password on the ubuntu account (I would advise the former). Failure to do that could lock you out of sudo on your instance! You may notice that the ubuntu user is not actually listed in /etc/sudoers Check /etc/sudoers.d/90-cloud-init-users Be sure to edit any sudoers file with visudo. e.g. ...


1

Amazon EC2 does not have automated mirroring of EBS volumes. So when you modify data on EBS volume A, you need to repeat it on EBS volume B. There are some ways to use network drives to share data between EC2 instances. In these cases, you have an external server hosting a network drive that each of your EC2 instances connects to. NFS is one example, Amazon ...


1

Can we mirror one EC2-Instance data to another? You can mirror data yourself using software like rsync. You could also take advantage of Amazon S3 or Amazon Elastic File System as a central location for your data. You have other options too, these are just a few examples. In the instance A I’ve created simple PHP file call “test.php”. This sounds ...


1

Can we upgrade versions in multiple EC2-Instance at the same time? Put simply, yes. You're responsible for everything at the Operating System level (including upgrades, software, config). You could use configuration management systems to manage a fleet of servers, or some form of orchestration to perform actions on your fleet at the same time. Here ...


1

To be honest the cause could be dozens of different things, you really need to systematically profile each component and narrow down where latencies are being introduced, rather than trying to guess where the problem is. Having said that, here's two things that come to mind: ELB does not scale instantly If you're using ELB (which I'm assuming you are) you ...


1

Three possibilities: Your VPC route table for the subnet is missing an entry pointing 0.0.0.0/0 to the IGW Your instance was launched into the default or wrong security group that is missing the incoming ssh rule You have a NACL on the subnet that is blocking the traffic


1

I would say there are two approaches: Use the AWS API to determine the IP of all group members and then do SSH. -- This itself is possible on different levels, ranging from a shell script using aws-cli (describe-auto-scaling-instances and describe-instances) to a more sophisticated setup e.g. with Python boto and Fabric. Have all instances register ...


1

You said: My sshd_config file has two changes from the default UsePAM was set to no and PasswordAuthentication was set to yes. I don't think that had anything to do with it. Actually that almost certainly is your problem. On a Linux system with PAM, attempting to login bypassing PAM is not guaranteed to work, and generally does not. Set UsePAM yes and ...


1

AWS has a variety of different storage options. Off the top of my head these include: Local magnetic disks (ephemeral storage) Local SSD's EBS (essentially SAN/NAS) EBS with Provisioned IOPS AWS has a lot of different options for you, including the ability to pay them more for better IO performance. You can also get high IO performance using SSD's ...


1

I would try something like this : RewriteEngine On RewriteCond %{HTTP_HOST} ^52\.17\.12\.123$ [OR] RewriteCond %{HTTP_HOST} ^ec2-52\.17\.12\.123\.eu-west-1\.compute\.amazonaws\.com$ RewriteRule (.*) http://www.example.com/$1 [R=301,L]


1

RewriteCond %{HTTP_HOST} !^52.17.12.123.com$ means that the RewriteRule is applied whenever the hostname is not 52.17.12.123.com. However, your goal is to redirect whenever the host is not your own hostname. Therefore you need to use this configuration for rewrites instead: RewriteEngine On RewriteCond %{HTTP_HOST} !^www.example.com$ RewriteRule ^ ...



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