Tag Info

New answers tagged

2

Yes, that is possible and safe. Yes, that should be possible. But I recommend you to enable Amazon Load Balancer Sticky Session feature Yes, it should be possible with some caveats: you should be careful about network protocol used for accessing shared data. Subversion relies on file locking and atomic file move operations. SMB and SMB2 are known to be ...


0

Well, if anyone cares, upgrading python to v 2.7 solves my problem: http://www.lecloud.net/post/61401763496/install-update-to-python-2-7-and-latest-pip-on-ec2 33 yum install make automake gcc gcc-c++ kernel-devel git-core -y 34 yum install python27-devel -y 35 rm /usr/bin/python 36 ln -s /usr/bin/python2.7 /usr/bin/python 37 cp /usr/bin/yum ...


1

This is what works for me: Set a private IP as primary IP address in "AWS::EC2::Instance" resource: "NetworkInterfaces" : [ { "DeleteOnTermination" : true, "Description" : "Main interface", "DeviceIndex" : "0", "PrivateIpAddresses" : [ ...


2

It is not possible to share a single EBS volume between multiple EC2 instances. Your diagram is offloading the data to a shared server. However, this shared server is simply another single-point-of-failure. So you're not saving yourself anything: if the AZ of that server goes down, then you've lost the data, even if the web server/VisualSVN server in ...


0

Finding the right position is kind of tricky. Spin up a RDS read replica stop the replication manually with mysql.rds_stop_replication use mysql> SHOW SLAVE STATUS\G to get needed information for the next steps the Exec_Master_Log_Pos variable will tell you the master binlog position the slave currently is the binlog file name can be found in variable ...


0

Change userdata to include the shell or cloudinit(userdata) script for the Userify group. This will create local sudo-capable users so you can fix the issue.


0

Your EC2 instance is running a web-server, so, what you need is to install the certificate in that web-server. Upload a certificate to IAM only makes sense when you use CloudFront, ELB, etc. and you want this services under HTTPS. One application of using certificates is to allow HTTPS access for Elastic Load Balancing. Actually, the server ...


2

"I've got plenty of memory and CPU for the load" - clearly you don't. Either you make your current workload fit into the available resource or you expand the resource to fit the workload. "Got OpCache running" - tuning PHP is a bit more involved than jus enabling the cache. It's certainly a starting point, but your next step should be to check that you've ...


1

Found an example here: http://pyrasis.com/book/TheArtOfAmazonWebServices/Chapter30/09 (though it seems to use an outdated/deprecated option).


0

This can be achieved by using describe-images from the EC2 service in the AWS command line tools. You'll have to specify the AMI id for the --image-id argument. From the docs: Describes one or more of the images (AMIs, AKIs, and ARIs) available to you. Images available to you include public images, private images that you own, and private images ...


0

By design, in case of equal priority, VRRP will select the node with the highest primary address as the MASTER. https://www.juniper.net/techpubs/en_US/junose11.3/topics/concept/vrrp-router-election-rules.html http://www.ietf.org/rfc/rfc3768.txt If the Priority in the ADVERTISEMENT is equal to the local Priority and the primary IP Address of ...


1

No, there is no way at this time to connect two Virtual Private Gateways in different regions. I'm sure it's a feature that's coming, given the VPC peering is available for VPCs in a single region. As for "You are responsible for implementing HA solutions for all VPN endpoints (if required)", I discussed in a previous answer there are various techniques for ...


0

The load balancer will start sending traffic towards the new EC2 instance as soon as that instance starts passing the load balancer's health check. I'm guessing your load balancer is configured with a TCP ping health check. That means as soon as the new instance starts responding to pings on port 80 it is considered healthy and ready to receive requests. ...


0

Try, on ssh, restarting apache. sudo service httpd restart // RHEL or CENTOS sudo /etc/init.d/httpd restart // also RHEL or CENTOS sudo service apache2 restart // ubuntu /sbin/service httpd restart // ec2 linux Oh, but you're using nginx, and it looks like it IS running for you, so yes, looks like an IP / DNS thing. Can you pull up your elastic IPs in ...


1

Many thanks to @MichaelHampton. Was finally able to confirm my local ISP was the issue and that the settings were working by launching a second AWS EC2 instance and testing the connection from there.


0

Your instance will only be "cloned" if you have a recent AMI (Amazon Machine Image) taken of the instance. There will probably be some changes to your filesystem since that snapshot was taken, so it's a good idea to use AWS userdata to create a Bash/CloudInit script that will trigger an update on the areas that will change, e.g. codebase, media etc. ...


3

The size of one I/O operation is dependent on a lot of things. Calculating the average for your application is not necessarily a bad idea. Amazon's definition of them implies that their hardware supports 256KB blocks. A single I/O operation is the read or write of one block. An "unaligned" access to the hardware where an operation spans two blocks will ...


0

The AWS CLI now supports the --query parameter which takes a JMESPath expressions. This means you can sum the size values given by list-objects using sum(Contents[].Size) and count like length(Contents[]). This can be be run using the official AWS CLI as below and was introduced in Feb 2014 aws s3api list-objects --bucket BUCKETNAME --output json ...


0

Look at your routing table - command is route. With the newer ip command use ip route show. You can look at help for either of these on how to add / delete routing entries in the table.


2

Subnet is defined by network and mask, e.g. network : 10.0.100.5 mask : /8 This means your subnet is : 10.0.100.5/8 Basically any valid IP of 10.xxx.xxx.xxx family belongs to this subnet. Only one interface can be used to access hosts in this subnet. So it's either eth0 or eth1 in your case. Other interface can have IP in same subnet, but it wont work ...


0

Many configurations need to share a single public IP. They need NAT. Your scenario's network traffic is all internally initiated. (SQS is polled.) With this type of traffic, there is no advantage to affording a NAT instance.


1

CloudWatch is far enough for testing the health of EC2 instance. If you need something more detailed inside the EC2, you could have a look at monit. Monit is a small Open Source utility for managing and monitoring Unix systems. Monit conducts automatic maintenance and repair and can execute meaningful causal actions in error situations.


2

This has just changed and Read Replication is supported both internally to RDS, and via triggers to external databases. The forum announcement is here: https://forums.aws.amazon.com/ann.jspa?annID=2747


0

You do not need hosting from GoDaddy. I have GoDaddy and I host with EC2. It is very simple to set up a website on EC2 and link it to a GoDaddy domain. Here is what you do: Launch an EC2 instance ( you can do this easily on the aws ec2 console at https://console.aws.amazon.com/e...) Set up your web server. If you have a Linux instance, this is called ...


0

AWS has a new feature to use tags to restrict IAM roles. For instance, you could set a set of servers with the tag "database" or "production" and keep users from doing anything with just that set of EC2 instances. I'm not sure if you can prevent them from seeing them altogether. There's a deeper StackOverflow discussion here about that and you can use ...


0

Userify.com manages user accounts, SSH keys, and sudo roles. It's pretty easy to deploy using AWS's User Data (under the Advanced tab of instance launch) or stick it right in the UserData script for an autoscaling group or whenever you're launching an instance by hand, which is great because it works before you even log in. (Or you can just paste the ...


0

Your example is realllly close. Amazon Linux calls their networking service network. So if the application/service you're attempting to control with upstart requires a network connection, do this: start on (runlevel [345] and started network) stop on (runlevel [!345] or stopping network) You don't need the runlevel bits, but its not a bad idea to be able ...


0

It's been a while since I worked properly with AWS, but you can script what you describe above. Creating a new image and changing the EBS config isn't that hard, at least not as far as I can remember. Once you have the script, you might be able to set up your FTP-client to execute it once an upload is complete. Amazon has lots of documentation on how to ...


1

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


0

I was able to accomplish this with a different key: container_commands: 001_get_utility_dir: command: "cd /opt/python/ondeck/app/utility && curl http://[bucket].s3.amazonaws.com/elasticbeanstalk/utility.tgz | tar xz"


1

These are not OS packages but rather modules provide for Perl, most modules can be gotten through CPAN. Have a look here for details on how to do this. Its a fairly easy process.


0

Chroot environments require the presence of all libraries and binaries necessary for normal operation. This includes all shared object files that the login shell is linked to. If you copy additional command binaries into this chroot, you will need their linker dependencies as well. Look for a guide on how to set up a chroot environment for ssh logins. ...


0

One big thing to keep in mind is that the IP address of your AWS instance can change. Given that you stated an "october update" it sounds like the server might have been rebooted at that time, and if so then that's the kind of event that can cause the IP address to change. Make sure you are using the public IP address or the DNS name of the instance to ...


0

In some setups there are security aspects to consider when deciding where to terminate SSL: Which node do you want to trust with your certificate? How much communication will happen behind the SSL termination point and thus remain unprotected? You also have to consider technical aspects about what is possible, and what is not: A load balancer that ...


0

Well, you would confirm that like in any other system: log in to the guest OS and check if the service is started. You are not even telling what guest OS are you running, so it's difficult to give you directions here. On Windows, look for IIS. On Linux, look for Apache. On both, check if TCP port 80 is listening, unless you are running your web server on a ...


0

Setting up a container network is much easier with weave. For more AWS-specific instructions, take a look at the project's blog.


1

These are hints from http://blog.celingest.com/en/2013/12/12/cloudfront-configuring-custom-error-pages/ You need to add another CloudFront origin pointing to the bucket where your error page is The cache behaviour of the newly-created origin should have a Path Pattern pointing to the folder (in the error page bucket) where the error pages reside You can ...


0

I rebooted several times and had to repartition my drive. After a few hours of unrelated things like this, YUM started working. I can't explain what fixed the issue.


0

Wow. OK.. I figured out what the problem was. I had my application trying to connect via a subdomain which I had routed to a public elastic IP. That seems to have been the culprit. For you to utilize a security group as an allowed incoming connection you have to use the private ip address of an elastic IP (if that's what you decide to use).


0

You could utilize route 53 private DNS, assuming your clients are in your vpc. https://aws.amazon.com/blogs/aws/route-53-update-private-dns-more/


1

It's because you are aliasing to an endpoint, not your specific resource. s3-website-us-east-1.amazonaws.com is the correct value, assuming your bucket lives in us stanard region. http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html#root-domain-walkthrough-switch-to-route53-as-dnsprovider


0

Every instance has an AWS OpsWorks agent that communicates regularly with the service. AWS OpsWorks uses that communication to monitor instance health. If an agent does not communicate with the service for more than a small amount of time (approximately five minutes), AWS OpsWorks considers the instance to have failed. AWS OpsWorks automatically ...


1

Autohealing is a feature enabled on a layer basis, for which it applies to all EC2 instances that belong to one layer. The way it works is that if the AWS OpsWorks agent that is installed on every EC2 fails to establish communication with OpsWorks, that instance is terminated and replaced. ...


1

In note of the recent EB CLI release, you can now do this with the EB CLI v3. eb create --tags foo=bar


0

Just came across this question, dumping some knowledge into it in case anyone else comes across this. Nowadays, ELB's can have Access logs enabled, which give you a bunch of different metrics on requests so you can tell if the ELB is at fault, or if your backend instances are at fault. (See request_processing_time and backend_processing_time )


0

If it is an EBS volume backed instance you can detach it from an instance, launch a new instance (in the same availability zone - e.g. if the broken instance is in us-west-1a, the new instance should also be in us-west-1a (not us-west-1b)) and mount it onto another healthy instance and then undo the edit /etc/fstab, or amend any errors you may have made.


0

Somebody compiled a library here https://plus.google.com/u/0/wm/1/111764273672221448826 but it would be safer to do it on your own.


1

I ran into this exact problem when I was first setting up chef on EC2. Here's the command we use to launch EC2 instances with knife successfully: knife ec2 server create \ --flavor m3.medium \ --image ami-****** \ --iam-profile "iam-app" \ --ebs-size 30 \ --security-group-ids sg-**** \ --subnet subnet-6de**** \ --ssh-key my-key-name \ --ssh-user ubuntu \ ...


0

Well of course, as soon as I walked away from the computer, I realized what the issue is... knife is trying to ssh in using the private IP. D'oh! I can only assume that --associate-public-ip will fix that. I'm away from the computer and will test later. Feel free to confirm/deny/offer advice.


0

Many thanks Tejay Cardon, your code works like a charm (I promise I'll look into writing a LWRP someday)! FTR the following code works for me on an aws ec2 ubuntu 14.04 build without a reboot. I was even able to do a sudo ifdown eth0 && sudo ifup eth0 from an ssh session and didn't get disconnected. execute "add custom dns domain search suffix" do ...



Top 50 recent answers are included