New answers tagged

0

As you mentioned those machines are created many years ago, I think you should check if they are using the old kind of storage call instance store. In my experience, if you need to shutdown those EC2 machines with instance store, the only option is to terminate it but it would cause data loss. So my suggestion is to either add a new EBS to backup all data ...


0

First you should check your configuration of health-check in ELB. Misconfiguration there can lead to such consequences. Also you can try disabling Source/Destination check in settings of EC2 instance.


1

No. There is no way. For the purposes of web browsing, DNS serves a single function: resolving names to IP addresses. No ports or URL paths are involved. To perform a redirect, you will need to use an HTTP server.


0

What you want is not Cloudwatch, but rather AWS Config. With Config, you can build rules to specify how your account resources should look, and then alert if your account violates the specified rules. The alerts are delivered to an SNS topic, so you can receive them via any method that SNS supports.


2

Using the awscli. pip install awscli aws ec2 describe-instances --output table --instance-id i-aef88019 Output: ||| StateTransitionReason | User initiated (2015-11-16 13:36:40 GMT) ||| [...] |||| StateReason |||| |||+---------+----------------------------------------------------------+||| |||| ...


1

OK, finally figured the root cause of this issue. The AMI I was using was creating a bridge that caused the connection issue due to it colliding with the IPs of my subnets. The output from sudo route -n looked like this on an affected instance: ubuntu@ip-10-0-1-92:~$ sudo route -n Kernel IP routing table Destination Gateway Genmask Flags ...


2

The IP address that accessed your site is passed in CloudFlare's own CF-Connecting-IP header. You should always use this instead of X-Forwarded-For, as that can be supplied by the user and contain untrustworthy information.


0

CloudFlare passes an X-Forwarded-For http header with its requests to your origin server, giving the original IP address of the requester. You can log that header at your end if you want to.


-2

For wine installation in Linux, please follow instructions provided on Wine Downloads page. Fedora You should follow this WineHQ installation guide for Fedora: Add wine repository by: dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/23/winehq.repo Change 23 to your version of Fedora. Install package (example for the development ...


0

Yes you can. For hiding S3 you use origin access identities and not expose s3 endpoint to any other service other than CloudFront. To restrict access to CloudFront you have 2 choices. You can either use CloudFront's private content feature and restrict access by time or to specific IPs. Or, you can use AWS WAF and block access to any source IPs other than ...


0

It's a NAT rule. iptables -L -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination REDIRECT tcp -- anywhere anywhere tcp dpt:http redir ports 8080 REDIRECT tcp -- anywhere anywhere tcp dpt:http redir ports 8080 REDIRECT tcp -- anywhere ...


0

I've seen this kind of problem caused by one of two reasons: The route-tables attached to the various subnets are configured wrong. There is a Network ACL in play (unusual). You don't need to define routes for each subnet, they're implicit in the table. Double-checking the IP addresses that your DNS entry resolves to on the other-AZ instances will ensure ...


0

Here is the answer: https://dcos.io/docs/1.7/administration/sshcluster/ To SSH to a master node: $ dcos node ssh --master-proxy --leader To SSH to an agent node: $ dcos node ssh --master-proxy --mesos-id=<mesos-id>


4

The problem is that the AWS RDS MySQL read-replica mechanism requires that the two schemas be exact. Replication, in general, requires this. But, if your definition of "close enough" is indeed close enough, this can be done in RDS for MySQL the same way you'd always do it. create a DB instance ... and SET it to be the replica. Well, that won't be ...


2

Don't do this with traditional AD DS. If you have to go cloud-only, you should use the Azure Active Directory SaaS solution with Intune for management and Windows 10 on the desktop. You lose things like Kerberos, GPO, etc, but you gain a great amount of flexibility and have no infrastructure to manage. As I said, this isn't a 1:1 comparison of features ...


0

Make sure that you've selected HTTPS as Instance protocol. I've had set 443 both as LB and instance ports but HTTP selected as Instance Protocol and exactly the same behaviour.


0

You can use s3cmd: s3cmd du s3://Mybucket -H or s3cmd du s3://Mybucket --human-readable It gives the total objects and the size of the bucket in a very readable form.


0

I'd try making your rules more specific - ie one for SSH, one for HTTP, one for HTTPS, with source 0.0.0.0/0. Then try changing the rules on a per rule basis, ideally making small gradual changes not a large jump to your target configuration. You might also double check the outgoing IP address of the proxy in your web server logs, to make sure you've got it ...


0

In your CloudFormation template, if you simply reference your SNS topic, then you'll get the ARN. For example: { "Ref": "MySnsTopic" } So you can use that as input to your nested CloudFormation template.


0

Check your ARN. It should be in the format shown on this page http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-ec2 When it says account is. This is the numerical AWS account to ID


0

Have you tried using the rolling update settings in elastic beanstalk? That way it deploys to one at a time whilst leaving the other in service


0

When you mounted EBS as /home, you hide all existing homes, including your user home. In users home ssh keys are stored, so SSH cannot load your public ssh. If you have disabled auth by password, you destroy your way how to log in. But there is a solution - simply delete your EBS and reboot EC2. Mount should fail during boot and your original /home will be ...


0

I would suggest you detactch the root ebs volume and mount it on another ubuntu instance. Then delete that entry from the fstab, reattach to the original instace and you should be able to boot again. Before you do this though check the system logs via the aws console to confirm what's failed


0

I never did find an answer to this using only travis to build and ship, I had to manually create a zip file after Travis ran grunt build and use awscli to upload it to s3 and trigger an EB deployment. .travis.yml language: node_js node_js: - 0.10 before_install: - sudo pip install awscli - ls /usr/local/bin/ - which aws - npm set progress=...


0

You can also set the security group on the load balancer to block public access temporarily. Not elegant but it works.


0

I believe I see where the confusion lay. The article implies that specific subnet objects are created for each of the layers. 10.0.0.0/18 10.0.32.0/19 10.0.32.0/20 - public 10.0.48.0/20 10.0.48.0/21 - protected 10.0.56.0/21 - spare You are not creating subnet objects for each item in the chart, you're only creating ...


1

Was this method valid then but invalid now, or was it never valid on AWS VPC at all? Yes, it was valid when written, and yes, it is valid now. The referenced question does not really have enough information to determine what error was being made, but the author almost certainly was making an error, since what was being attempted was correct, in principle. ...


0

The certificate issued by the Certificate Authority should be uploaded to IAM along with the private key and certificate chain (CA Bundle). After uploading, the certificates are available for other AWS services to use. The tool for certificate uploading is AWS command line interface (CLI). *note: the Certificate Authority can send you the certificate in a ...


0

For internet access to work behind a NAT instance, your default route in your private subnets needs to be the internal ENI of your NAT instance - see docs. Also, your NAT EC2 instance needs to have the Source/Destination Check disabled - see here. I would also make sure you have followed and understood the Amazon documentation on using a NAT EC2 instance. ...


0

Am not sure if this will work, but it looks like you might be able to get a similar outcome using NotificationConfiguration within the ASG resource. The NotificationConfiguration could send a notice to an SNS topic which has the SQS queue subscribed. Obviously, the lifecycle will progress past pending with this approach and not wait for a complete-...


0

So the closest I have found is a compromise by creating a Debian/Ubuntu EC2 instance and then installing "katoolin" which enables you to install all the Kali distro tools.


0

I needed to do remote port forwarding from the EMR cluster (to forward the local port on the EMR cluster master node to the remote port on the EC2 instance) instead of local port forwarding on the EC2 instance (which was forwarding the local port from the EC2 instance to the remote port on the EMR cluster master node). So, the command looks like: ssh -R ...


5

By default the AWS billing data is only accessible to the root account and not subject to IAM. In order to share access the root account has to go to the "Account Stettings" and enable "IAM User Access to Billing Information".


1

As you've worked out, you have a load balancer and auto scaling creating different instances of the server from an AMI. That means some of them will be using a server that has old information. Since you're using RDS your text and configuration should be shared. Creating an AMI on each change isn't practical. I suggest you look into Amazon Elastic File ...


0

I resolved with some help from this page Can not access EC2 server via IP address Option #2 solved my problem and hope it will help some others. A different problem popped up though. I got the server running in the public IP but puma is not running; the deployment message claims everything was working fine. I resolved by bypassing this and run bundle exec ...


1

When you give a profile name or change the default profile name you're effectively saying 'i want to use a named profile in my crednetials file'. so what you've done here is said 'use the profile called 'ken' as my default, but your default profile is called 'default' not 'ken'. Typically this ability is used to have profiles called 'dev' or 'prod' etc, ...


0

You can try this: ssh -q -o StrictHostKeyChecking=no user@host "python -c python-script.py"


1

No need of additional software installations. You need only awscli. Here is what I just wrote. It is simple and works like charm. #!/bin/bash -e # # Author: Peycho Dimitrov # # DESCRIPTION # # Create full backup of all hosted Route53 zones / domains in your account. # # REQUIREMENTS # # Available s3 bucket (where your json files will be saved) # ...


4

This type of configuration is not supported by AWS. VPC Peering does not support "multiple hop" routing. The following configurations are not supported through VPC Peering. VPC A -> VPC B -> Internet VPC A -> VPC B -> VPC C Reference: Invalid VPC Peering Connection Configurations


1

Your nodejs server is listening to the local loopback device 127.0.0.1 as you can see in the netstat output. 127.0.0.1:8080 You need to change the nodejs server to listen to 0.0.0.0


0

This probably means that your Docker daemon is not running on your Container instance. You can do so by running the below command (ssh to your instance beforehand): sudo docker -d &


0

Navigating to the dashboard of your application locate 'Configuration' and click 'Change' You should see a list where you can choose a Platform. The latest version is indicated in that list. Selecting platform AWS EB uses specific setups for different programming languages. You can find a list of the setups in the documentation http://docs.aws.amazon.com/...


0

In order to achieve the desired goal, do the following: Create a public subent and a private one. Put your database in a private subnet, disable external access Create an EC2 instance in a public subnet. RDP into it. Use it in order to connect to the private RDS. (by default public and private subnets in AWS are able to communicate with each other) This ...


1

It's important that only users who create the instance and view/manage them. This is very difficult to do with users in the same account (and the whitepaper you link to makes no promises about it). You can limit actual instance shell access easily through SSH keys, but the AWS-level instance management pieces are harder to separate. EC2 IAM permissions ...


1

You can set up alert on billing if the monthly usage is more than $XX: CloudWatch -> Create Alarm -> Total Estimated Charge -> next -> select threshold etc. I also want to create user groups that are allowed to create any resources they want under my account, and see and manage only those resources. I believe it is possible to allow to create any ...


1

The requested hostname is included in the Host: header. Elastic Load Balancer will forward all headers on to the underlying EC2 instances. There is no configuration to allow or disallow headers. CloudFront configuration allows you to blacklist and whitelist headers.


3

To your original question: if you mount a filesystem "on top" of your current working directory, you will not see the contents of the mounted fs, nor will you be able to save content to that fs until you cd back to the parent directory and then enter the mounted fs again. When you write data, it consumes space on whatever filesystem it is written to. In ...


0

Solution: Ask customer support if your account is put into isolation and have them remove it. This behavior will most likely only happen if your account was suspended and it wasn't removed when it was re-activated. Account Isolation can at the region level.


0

If not already being used, you should consider using a replica set cluster. This will give your database high availability. The MongoDB documentation then provides a guide on performing version changes from 2.6 to 3.0 and from 3.0 to 3.2, respectively: https://docs.mongodb.com/manual/release-notes/3.0-upgrade/#upgrade-a-replica-set-to-3-0 https://docs....


0

If this is the output of netstat: tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN That shows that postfix still only listens to the SMTP port on localhost, otherwise I would expect to see 0.0.0.0:25 as the local address. Did you restart postfix after changing the main.cf? Is your security group assigned to your ...



Top 50 recent answers are included