Hot answers tagged

7

No, the data on your ephemeral drive will not be there. Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.


5

90%-95% SLA is useless, it is better to don't say it (even old shared hosting guarantee better SLA for your webapp), you need at least 99.5% for serious business. If you need better SLA (and your customers will!) you need to have mirrored resources (2 app servers, 2 database servers etc.), setup loadbalancing and failover (like keepalived, haproxy, squid ...


5

I've managed this with the following which works well. Create /etc/cron.d/reboot with the contents below. Note - It's been a while, you should check syntax. @reboot root run-parts /etc/cron.reboot Create a folder /etc/cron.reboot From there it's a matter of dropping files in to the cron.reboot folder.


4

Q: Can I use certificates on Amazon EC2 instances or on my own servers? No. At this time, certificates provided by ACM can only be used with specific AWS services. Q: With which AWS services can I use certificates provided by ACM? You can use ACM with the following AWS services: • Elastic Load Balancing • Amazon CloudFront ...


4

This question is probably going to get closed as "too vague" very quickly. With AWS you can architect a highly available solution, or you can provide a low reliability solution. Any single virtual server is probably fairly reliable, 99.9% or better, but the software you run on it and the monitoring you do will probably be the limiting factor. However a ...


3

Your certs are tied to the host names you supply and are therefore independent of the IP address of the machine they are used on.


2

I have an Amazon Linux server (no GUI), which is somewhat similar to Ubuntu, but not the same. The CPU utilization when the server isn't serving requests is around 0.03%, and I get to maximum CPU credit fairly quickly. Eight t2.micro instances comes to $86/month, one m4.2xl is $350 a month. If you go with the t2 instances you also need a load balancer, ...


2

If the EBS volume that backed the terminated instance is still around, you have a chance at restoring the data. Otherwise, all is lost. This is reason number 2,274,738 to: 1) Never deploy things outside of your configuration management system and 2) Always have backups.


2

I guess the key word here is TERMINATE. You might be able to get away with stopping and starting your instance again immediately. If it's EBS backed it will be a new instance and will be EXACTLY the same, other than the external IP address. Note that in this case you need to STOP your instance, NOT terminate. Terminate deletes the EBS disk. To be safe, or ...


2

Yes but not directly. You can use something like HA Proxy to provide access. This could defeat the purpose of Elasticache though - you may want to use vanillia Redis so you can synch using the Redis native tools otherwise your queries are going to have some serious latency.


2

The ResearvationId has nothing to do with Reserved Instances. It is a unique value indicating a request to launch EC2 instances. A launch request may come from the cli, AutoScaling, or the AWS Management Console. Each request to aws ec2 run-instances will return zero or more reservations of instances. Usually, it'll be one if it succeeds, but the docs say ...


2

This is happened to me also. The thing is that amazon is trying to install php/mysql of older versions . you need to specify which version you need to install. to install php-mysql for php 5.6 issue this command. sudo yum -y install php56-mysqlnd You can install older versions if you want to.


2

lastlabs.com is not pointed at Route53 nameservers. Any records you set up on Route53 will currently have no effect. Name Server: NS75.DOMAINCONTROL.COM Name Server: NS76.DOMAINCONTROL.COM Update the nameservers at your domain registrar to point to the four nameservers Route53 gave you.


1

The two big methods here are: Use a central authentication system such as LDAP. Use a configuration management system to manage SSH keys and associated files. The first isn't very Linuxy since it requires people to use a password on their first entry to a system. That said, it does allow large installations to work rather well. The second can be ...


1

tl;dr The system I am running sends a hell a lot of DNS requests out - probably it does not use any DNS caching. And the DNS server is in another Availability Zone. My friend proposes installing dnsmasq and pointing all /etc/resolv.conf there. Full way to debug such stuff I debugged this with a friend, here is how we arrived at the solution so everyone ...


1

It'll go through a standard Linux shutdown, so you can setup a service with a shutdown script to do whatever you like.


1

To restrict RDS access to only your Auto Scaling EC2 instances, and to allow access to your EC2 instances only from your ELB, you're going to use the same method: add a rule to your security group based on a source security group (rather than a source IP address CIDR). Assuming your EC2 instance(s) security group is sg-123, you would do the following: In ...


1

Regional Data Transfer only applies for AWS services, so if you're transferring data from one EC2 instance to another EC2 instance in the same AWS region it's free, if you're transferring data between EC2 instances in different regions you have to pay. An AWS region is a grouping of Availability Zones, an Availability Zone being: Each availability zone ...


1

The way to do this is to create a DNS A record.


1

The shell may be eating your quotes, since both error message show them to be absent. {fusion_**** : *** } isn't valid JSON, it definitely needs to be {"fusion_****" : "***"} with both key and value quoted (assuming the value is a string; the literals true, false, and null... and numeric values are not quoted, of course). I would guess that it needs to be ...


1

After some help from @bleve and @LetoTo in the IRC #swan I changed the config like this: left={local_ip} leftid={elastic_ip} leftsourceip={elastic_ip} leftsubnet={elastic_ip}/32 And now works. This line was added to the routing table after connecting the VPN: 192.168.253.155 dev eth0 scope link src 52.6.108.86


1

Rackspace now has Security Groups! Before this, though, it would certainly be possible to use a Linux box as a firewall. The Vyatta server image is designed just for this purpose—though it's not a "cheap server" at $6.24/d, it is a cheap firewall.


1

If you put it into an AutoScalingGroup, you can edit the AutoScalingGroup min/max/default to 0, then as soon as it starts to destroy the old instance, you can then put the min/max/default to 1/1/1 and presto: new instance.


1

Amazon has announced a "Run Command" feature.


1

You should have differet vhosts/server blocks for each hostname. You should serve example.com on port 80 as normal and only reverse proxy to port 8080 for otherdomain.example.com.


1

How can I set the DNS up so any lookups to *.mydomain.aws will use NameServers I specify, and everything else will use the default one? That's not how DNS works. You specify a set of DNS servers, your clients throw their requests at them, and the servers have to deal with whether or not they can get answers to the clients' queries. Fortunately, with ...


1

It depends what you mean by change the instance. If you resize your current instance then you should be fine. If you migrate your instance (because it can't be resized) then you should make sure that you take your private key with you. If you don't you'll still be able to apply for a certificate for with the CSR, but the returned certificate won't be of ...



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