Tag Info

New answers tagged

0

You can download the .exe from Get Into PC this avoids the much larger install of the ADK.


1

You need to enable the RHEL optional and/or extras channels. yum-config-manager --enable rhui-REGION-rhel-server-extras rhui-REGION-rhel-server-optional


-2

To save some Ubuntu neophytes like myself some time, newer Ubuntu instances no longer use sshd reload. Instead it is asking for: sudo restart ssh Please see this SO link for more details: http://superuser.com/questions/214799/no-etc-init-d-sshd-file-ubuntu-ec2


0

You can implement an EC2 status check. It's done from the EC2 dashboard. Go to instances, select your instance, choose the status checks tab (next to instance description) Click on create status check alarm The default "Status Check Failed (any)" should be good. I always set the interval to greater than one so I don't get bothered for transient issues. It's ...


0

In fact unless it is a snapshot, as an uninitialised block device, you may need to.. Create a partition table Label the volume Create partitions (at least 1) Create a file system on your partition Format the file system if required None of these are strictly necessary if you do not want a filesystem, if you are only storing one file or stream (tar or dd ...


1

If I auto scale some instances, do I need to do installations on all instances or some one instance? If one then what will be my primary instance? There is no such thing as a "primary instance". When you set up an ASG, you specify which AMI you want to use for the ASG instances. You can either bake your application and configuration into that AMI, ...


0

What I don't get is how that's secure or workable if your public IP address is dynamic? This solution could work if you find your IP doesn't change often, or if you only need access for a short time. It adds an extra layer of security as SSH isn't exposed to traffic outside of the CIDR you supply. If a specific CIDR doesn't work, you could try on or ...


2

Create a new directory for example /opt/static/ and chown it to www-data or the equivalent on your OS and put your static stuff in there. This will totally bypass tomcat for the static assets (a good thing IMO) and then change your vhost definition to this (I am assuming that all your api calls are in the api url - it will also enable client side caching ...


1

It's fine to restrict access to your SSH server by IP address, but SSH doesn't rely on that for its security. If you disable password logins (PasswordAUthentication no) and use private key authentication only, no one can get in without your private key. It's safe. So in other words, you don't have to worry about the firewall rules if you don't want to.


1

You can add a CIDR range to the security group that represents the superset of all IPs your ISP can allocate to you. Either that, or use the AWS API to dynamically update your security group.


1

EC2 has an option to auto-associate a random public IP upon instance creation. If you enable that, your instance should be able to issue the API call to associate your EIP. If you're using the python-based AWS CLI, you can issue the --associate-public-ip-address paramater to do this. If you're not using this tool, you should start doing so, as the ...


2

You didn't come out and say this right away, but you have given AWS console access to someone who you don't trust. That is the problem you need to solve. What you've done is equivalent to giving someone physical access to you server. Once you've done that, all bets are off. Game over. So, the first thing that you need to do is revoke this person's access to ...


1

You have a few options to control access. Take as many of these approaches as you can. Use instance store backed EC2. Setup MFA on your AWS console. Setup Security Groups on your EC2 machine. Add a passphrase to your SSH private key. Disable password auth to SSH. Disable root login to SSH. Audit all user accounts for SSH public keys. If you do all of the ...


0

Referencing the default security group is possible using: { "Fn::GetAtt" : ["VPC", "DefaultSecurityGroup"] } Where "VPC" is your VPC resource name. With AWS::EC2::SecurityGroupIngress and AWS::EC2::SecurityGroupEgress, you can augment the permissions of this default security group. I think this is what you want: "VPCDefaultSecurityGroupIngress": { ...


0

You can use the AWS CLI tools to do this: $ aws ec2 describe-instances ... "PublicDnsName": null, "EbsOptimized": false, "LaunchTime": "2015-04-23T19:43:06.000Z", "PublicIpAddress": "54.200.248.x", "PrivateIpAddress": "10.0.0.64", "ProductCodes": [], ...


0

Your question is unclear; you should expand it. However, a few basic tips: AWS EC2 instances can be assigned public IPs (IPv4 only, currently), which would be displayed in the EC2 control panel. If you're looking to list the IPs directly from the instances, you can do an ifconfig eth0 | grep 'inet' which will show you the internal AWS IPs on your VPC. As ...


1

After many different approaches, it turned out that limiting my policy for a single queue was causing all the problems. I assumed that when policy applies to single queue and you do ListTopics, then you will get just the topic you have access to. However, my SNS had several other topics and most probably their existence in ListTopics result was considered a ...


0

[[ is a bash-builtin command and is not available in sh. You are running a script written for bash under sh. Try add execute permission chmod +x ec2-automate-backup-awscli.sh and run sudo /home/ubuntu/scripts/ec2-automate-backup-awscli.sh without sh


0

The solution was, based on @CraigWatson answer, the next configuration on GoDaddy DNS Zone File of the danigarcia-dev.com domain: Create a CNAME record with: www as the Host ec2-52-26-205-227.us-west-2.compute.amazonaws.com as the Points to A forwarding to the www.danigarcia-dev.com web address


0

Assuming that it is a full-fledged Windows service you need to start, then it's as simple as @Mxx points out: just set the service startup type to Automatic rather than Manual. If it's not a service but just a regular Windows process, then you can look into using Sysinternals Autologon to cause the instance to automatically log in as a particular user when ...


4

I can literally delete all but the most recent with impunity Assuming you don't need any data that was already deleted or overwritten on the volume when you took the most recent snapshot, that's true. EBS snapshots are logically incremental -- not physically incremental. Here's the cleverness that explains the difference: Snapshots of EBS volumes ...


0

You most likely have set your domain up for web forwarding rather than DNS redirection. To get redirection without URL rewriting, you'll need to point your domain apex to your EC2 instance using a CNAME record. So, using the GoDaddy documentation, create a CNAME record with @ as the Host, and ec2-52-26-205-227.us-west-2.compute.amazonaws.com as the Points ...


0

Changed Hannes' answer to avoid error messages and include example usage in script: if [ -f /sys/hypervisor/uuid ] && [ `head -c 3 /sys/hypervisor/uuid` == ec2 ]; then echo yes else echo no fi This doesn't work in Windows instances. Advantage over curl is that it's close to instantaneous on both EC2 and non-EC2.


2

First have you enabled mod proxy on apache? Secondly try remove ProxyPreserveHost On In addition make sure the port is opening; easiest way to check is go to http://www.yougetsignal.com/tools/open-ports/ (Enter website address and port 80) Hope this helps


0

Thanks for all the input. I've solved this by adding a condition to the virtualhost section that exludes the redirect to 443 for the : RewriteCond %{REQUEST_URI} !^/proxy/login.php$


2

If you had previously enabled CloudTrail, then the instance ID would perhaps be logged there. I would doubt if the tags were, though. The only other source would be AWS Support, who might be able to pull this information.


1

Can I reuse the same volume as root device on multiple spot instances? Simply to clarify: it's not possible to use the same EBS volume on multiple EC2 instances simultaneous. Assuming you mean not-simultaneously, you could reuse an EBS volume as the root volume, but you'd need to do the following: Allow the new spot instance to launch Shutdown the ...


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.


0

[the ElastiCache server] has security group(s) assigned, in my case just cache-access Security groups apply to ElastiCache servers just like they do to EC2 servers (they're EC2 under the hood, even). Port 6379 doesn't need to be open for the EC2 servers, but it does need to be open for the Redis server. You could put the cache or EC2 servers in ...


1

http://docs.ansible.com/ec2_module.html instance_profile_name (added in 1.3): Name of the IAM instance profile to use. Boto library must be 2.5.0+


0

It would seem that the Erlang VM is unable to either find or access one of mysql.beam, mysql_auth.beam, mysql_conn.beam or mysql_recv.beam. Make sure those are all in the appropriate ebin directory and readable as the user ejabberd runs as.


1

You can simply bake an AMI with the current version of your code and configs and then create as many EC2 machines as you'd like. Check out Packer and AWS auto scaling groups.


0

I think you can leverage the new Parameter support in Cloudformation to do this. http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html Get a list of all subnets in your VPC like this: "mySubnetIDs" : { "Description" : "Subnet IDs", "Type" : "List<AWS::EC2::Subnet::Id>" Then pick the first (or ...


0

For people who encounters this issue even with SHA2 and a very good rating on SSL LAB (+ NO warning): please check your libnss version. I'm currently using Ubuntu 13.10 here and libnss is version 3.15.x. => It seems that versions prior to 3.17, libnss check for the weakest security chain instead of the strongest. Which means that, if you have a SHA1 ...


0

You may also be able to utilise the VPC traffic flow logging functionality released today. You should be able to enable that on a specific ENI or a whole subnet. One method of actually analysing the traffic would be to create CloudWatch metric filters to sum up traffic on particular ports or IPs. Alternatively you could export or stream the logs from ...


0

There's an Amazon provided IAM policy for CloudWatch. No need to build your own. CloudWatchFullAccess


0

I have used ntop for years, although it might be overkill for your situation since it includes a web interface to view the data.


0

You can use various tools to track down network bandwidth usage - the most useful I have found is iftop from the command line. This is only a point-in-time snapshot however (much like top and htop), but if your instance is constantly generating traffic, this should enable you to see where it is going.


0

It turns out that it's pretty simple to connect to EC2 by using Quagga with Debian Linux. /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet static address 10.x.x.x netmask 255.255.255.0 network 10.x.x.x broadcast 10.x.x.x gateway 10.x.x.x allow-hotplug eth1 iface eth1 inet static address ...


2

The CentOS 6 (x86_64) HVM AMI image is setup to allow ssh key based login as the root user, it is advisable to setting up a non root user for regular instance access. Steps for implementing this: https://awsmp-usageinstructions.s3.amazonaws.com/CentOS_User_Add_Instructions.pdf Ref: http://wiki.centos.org/Cloud/AWS


1

You'll need to do an offline recovery. The steps are roughly: Shut down the server. Start up another temporary instance. Detach the EBS disk from the original server and attach it to the temporary server. Mount the filesystem. Edit /etc/shadow and copy/paste a known password hash into the ec2-user's entry. Unmount and detach from temporary server. ...


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


0

You have to configure ntpd on all instances. If you do not your servers' time will start drifting. You have to allow UDP 123 to the public internet, as described in the user guide under Configuring Network Time Protocol. If your instances are inside a VPC, you may want to dedicate an instance to be your NTP server, only expose that instance to the internet ...


0

I was getting 'Forbidden' as the response to './ec2.py --list'. It looks like a bug when not using RDS and a query request to describe RDS resources is made (as is the default with this plugin). Just disable the request in ec2.ini like this: rds = False


0

Well, I just needed to add a rule for port 80 (or all trafic to make it easier) in the Security groups..


0

Download the .pem file anywhere chmod 400 file.pem ssh -i file.pem ec2-user@ip (Amazon AWS distrib) or admin@ip on a LInux system.


0

Oh my... :( The Ubuntu Firewall (UFW) was activated (noob). I added ufw allow 443/tcp and now it's all right. sorry for the post. But who is riding a webserver with nginx and php-fpm can enjoy the above settings are all correct and my website is now functioning normally also with https.


0

I had a similar problem, my EC2 Amazon Linux instance was not reachable anymore after running sudo reboot. No SSH access, stop/start/reboot commands from Amazon admin console gave me no result too. I was finally able to restart my instance by creating an image via the Amazon console. The image creation process seems to fix the instance state. Hope it ...


0

Creating image also involves creation of snapshots attached to that instance. Below IAM policy should work. { "Effect": "Allow", "Action": [ "ec2:Describe*", "ec2:CreateSnapshot", "ec2:CreateImage" ], "Resource": [ "*" ] }


0

Below is the snippet of IAM policy that is working for me for creating tags. { "Effect": "Allow", "Action": [ "ec2:Describe*", "ec2:CreateTags" ], "Resource": [ "*" ] }



Top 50 recent answers are included