Tag Info

Hot answers tagged

27

Most Linuxes these days should perform a forced fsck at boot time when the file /forcefsck is present on the system. If you are at liberty to reboot the VM, run touch /forcefsck Then reboot at your convenience


19

For our ec2 ubuntu instance, the above answers did not work completely. On Ubuntu, by default, the check is not enabled in the rcS file. So Edit rcS file sudo vi /etc/default/rcS below the line #FSCKFIX=no Add FSCKFIX=yes Then do as suggested above. sudo touch /forcefsck Reboot from ec2 console. Delete the line FSCKFIX=yes to get back rcS ...


12

Your certificate is using the outdated SHA-1 algorithm, which because of security risks Google Chrome now warns about. http://googleonlinesecurity.blogspot.com/2014/09/gradually-sunsetting-sha-1.html https://community.qualys.com/blogs/securitylabs/2014/09/09/sha1-deprecation-what-you-need-to-know https://shaaaaaaaaaaaaa.com/check/aws.hatchlings.com ...


10

You should not be sharing these keys. Period. Each user should generate their own SSH keypair and their public key should be deployed to each system they need access to. Private keys are named as they are for a reason - they should be private to each user, generated by them, protected with a passphrase, and kept in a secure location on that user's ...


8

How would this be setup connection wise without forcing all traffic through the domain controller? With site to site VPNs. You'd set up your cloud assets as a site, and then establish a site-to-site VPN between your cloud site and each of your physical sites. An alternate option, that Microsoft uses, but is generally ill-advised (unless you really, ...


7

This is due to a limitation of RPM/YUM on Amazon Linux, and the way that the multiple versions of php are packaged. One of the features of Amazon Linux is that there are multiple versions of several languages and other opensource software packages. In many cases these packages have to conflict with one another, as the software is not designed to be installed ...


7

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 ...


7

VPC does not make any difference in latency. The main thing you can consider if you need especially low latency is using placement groups. There are some limitations on which instance sizes support this, but if you use them, you are guaranteed very low-latency interconnects on the EC2 10Gbps network.


6

I have done this, please read my article before you actually do this here: http://neonos.net/white-labeled-dns-name-servers-on-amazon-route-53-with-delegation-sets/ The functionality has been programmed by Amazon in Nov 2014, however it has not been implemented in the web based console, hopefully they will do this soon. There is also no documentation or ...


6

If your VPC EC2 instances are in private subnets, then to access EC2-Classic, your VPC will need a NAT. Give your NAT an elastic IP address so it's a constant public IP address. Then in your RDS security group, allow access only for that Elastic IP address. If your VPC EC2 instances are in public subnets, then you could give each of them elastic IP ...


6

No, t1.micro uses PV instances. Use t2.micro for an HVM instance.


6

TLDR: ec2-register -a x86_64 -d '3.15.7-200.fc20.x86_64' -n 'Fedora_20_HVM_AMI' --sriov simple --virtualization-type hvm -s snap-b44feb18 --root-device-name /dev/sda1 Detailed steps: Answering further based upon Jeff Strunk's response to simplify the steps and giving a bit more details on the ec2 register image: Create Instance using PV Image. Make / ...


6

Using a VPC will solve a lot of your problems, as private IP addresses will be static there. Amazon is strongly encouraging people to move to VPC for reasons like this. Once you have one, your two systems should be able to talk over the AWS-internal network. To answer your question about exposure along the aws-public <---> aws-public route, it is ...


6

You want to setup NTP. See: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html Extra content here.


6

Amazon run on Xen, which provides Para-virtualization (PV) or Hardware-assisted virtualization (HVM). Para-virtualization used to be the recommended choice, as it gave you better performance (with a much closer integration to the virtualization host, through patched specialized kernels/drivers on both the host and the guest). Hardware-assisted ...


6

Is S3 a proper choice to keep live linux user home directories? Amazon has announced their EFS service, which is exactly what you need for this. Either use EFS or roll your own NFS server for home directories.


5

The first problem isn't on your instance at all... it's your terminal, which isn't correctly configured for utf-8, so you're seeing characters other than what's supposed to be displayed. Googling ΓΆΓΆ linux will find many examples of this, such as https://bugzilla.redhat.com/show_bug.cgi?id=517447 The second problem is that you are confusing volumes (disks) ...


5

Yes there is! Embrace the power of DNS eventual consistency. Set up an ELB, point it at your instance. Update the A record for your public instance with a CNAME for the ELB. Wait a week. Associate an Elastic-IP with the instance. Update the CNAME record for your app with a new A record for the EIP. Wait a week. Turn off the ELB. For the two weeks of ...


5

Amazon announced ClassicLink literally just yesterday. I haven't had time to try it out yet so I'm not sure exactly what it's capable of but from that blog post: You can now enable this feature for any or all of your VPCs and then put your existing Classic instances in to VPC security groups. It sounds like this feature might be ideally suited to ...


5

Turns out EC2 was blocking the forwarded packets from the OpenVPN server. There is a setting on the EC2 Dashboard under Network & Security -> Network Interfaces -> Actions -> Change Source/Dest. Check. When I disabled this on all my instances traffic through the VPN is flowing as intended. Hopefully this will help someone else.


5

Since you cannot boot into live disc, this is may sounds a bit weird, but i guess it'll do the job) high level: boot into new (another) instance. attach storage from old instance to new (current). run fsck. detach storage from new (current) and reattach it to old instance.


5

The answers here seem to be missing a few steps prior to re-sizing specially for people who are changing their EBS volume size. If you have used a snapshot to create the EBS or with certain AMIs you will need to extend the disk (xvda), extend the partition (xvda1), then extend the filesystem (/). If I'm reading this correctly, your disk looks like this: ...


5

Came across the same issue with Server version: Apache/2.4.6 As per the documentation at [1], "In 2.4.5 and later, SSLProxyCheckPeerCN has been superseded by SSLProxyCheckPeerName, and its setting is only taken into account when SSLProxyCheckPeerName off is specified at the same time." So adding following entry did the trick: SSLProxyCheckPeerName off So ...


5

If it's reinstantiating itself then you've probably got it in an auto-scaling group. Delete that auto-scaling group (or reduce the minimum instance count to zero).


5

Provide your script via "user-data" during your launch process and it will be executed upon first boot. If you're using awscli, use the --user-data option" $ aws ec2 run-instances --image-id ami-xxxxxxxx --count 1 --instance-type m1.small --key-name foo-key --security-group-ids sg-xxxxxxxx --subnet-id subnet-xxxxxxxx --placement AvailabilityZone=us-west-2a ...


5

Supposedly this is supported now https://aws.amazon.com/blogs/aws/route-53-update-private-dns-more Reusable Delegation Sets When you use Route 53 to host DNS for a domain, it sets up four authoritative name servers collectively known as a delegation set. As part of today's release we are simplifying domain management by allowing you to use the same ...


5

If you have only been creating snapshots at AMI creation time, you may be able to reliably do this with the CLI or powershell tools: Get all EC2 snapshots created by your AWS Account (OwnerID = your aws account) Get Snapshots associated with still running Volumes Of these snapshots, attempt to match their VolumeID with the VolumeID of still running ...


4

Good question, the Amazon EC2 documentation for CPU Credits in T2 Instances could be more precise here indeed - the introductory blog post New Low Cost EC2 Instances with Burstable Performance provides a better explanation, see the table in the middle: The column labeled "Baseline Performance" indicates the percentage of single core performance of the ...


4

I'm not positive I understand your question completely, but if what you want is to be able to generate a list of your volumes, along with name tags, something like this might work: aws ec2 describe-tags --query "Tags[*].{Name:Value,ResourceId:ResourceId}" --filters "Name=key,Values=Name" --filters "Name=resource-type,Values=volume" --output json ...


4

Check the file/directory permissions with ls -alh or stat command. Seems might be a permission/ownership issue.



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