amazon-vpc

A guy I work with gave me the EC2 credentials to log onto his EC2 console. I was not the one who set it up. Some of the instances show a public dns name and others have a blank public DNS. I want to be able to connect to the instances that have a blank public DNS. I have not been able to figure out why these show up as blank. Mat I had the same problem an solved it. Have a look at the step-by-step instructions: Go to console.aws.amazon.com Go To Services -> VPC Open Your VPCs select your VPC connected to your EC2 and select Actions => Edit DNS Hostnames ---> Change DNS hostnames: to YES Hope

What is an Internet Gateway? What is a NAT Instance? What services do they offer? Reading AWS VPC documentation, I gather they both map private IP addresses to internet route-able addresses for the outgoing requests and route the incoming responses from the internet to the requester on the subnet. So what are the differences between them? What scenarios do I use a NAT Instance instead of (or besides) an Internet Gateway? Are they essentially EC2 instances running some network applications or are they special hardware like a router? Instead of simply pointing to AWS documentation links, can you

I am very new to kubernetes and have just got a stock kubernetes v.1.3.5 cluster up on AWS using kube-up. So far, I have been playing around with kubernetes in understanding it's mechanics (nodes, pods, svc and stuff). Based on my initial (or maybe crude) understanding , I had few questions: 1) How does routing to cluster IP work here (i.e in kube-aws) ? I see that the services have IPs in the range 10.0.0.0/16. I did a deployment with rc=3 of stock nginx and then attached a service to it with Node Port exposed. All works great! I can connect to the service from my dev machine. This nginx

I am trying to connect to RDS Database from an AWS Lambda (Java). Which IP should I enable from the RDS Security group rules? You can't enable this via IP. First you will need to enable VPC access for the Lambda function, during which you will assign it a Security Group. Then, within the Security Group assigned to the RDS instance you will enable access for the Security Group assigned to the Lambda function. You can configure Lambda to access your RDS instance. You can enable this using Lambda management console. Select Lambda function which need access to RDS instance and then go to

In AWS I have a VPC set up with a Bastion Host. The bastion host is a single EC2 instance with a public address trough which you can SSH to any other server on the VPC. I have created an RDS MySQL instance within the VPC and I would like to connect to it using MySQL workbench. I have followed the steps detailed here , however in "Step 6: Setting up remote SSH Configuration", it asks me to "Provide the Public DNS of the Amazon EC2 instance" (i.e. the bastion host). MySQL workbench then does checks for certain MySQL resources on that server. However, this is not correct in my opinion as I have

I'm working on an Ansible playbook where I use the ec2_vpc_subnet_facts to register facts about subnets in a VPC like: - ec2_vpc_subnet_facts: region: "{{ ec2_region }}" filters: vpc-id: "{{ vpc.vpc.id }}" register: vpc_subnet_facts thus getting back a structure like (removed irrelevant attributes): "vpc_subnet_facts": { "changed": false, "subnets": [ { ... "id": "subnet-0bb50753", ... "tags": { "Name": "mytag1" }, ... }, { ... "id": "subnet-0bb50754", ... "tags": { "Name": "mytag2" }, ... } ] } Later in the playbook, when creating the EC2 instances the idea is to lookup a subnet ID based on

We're using Amazon EC2, and we want to put an ELB (load balancer) to 2 instances on a private subnet. If we just add the private subnet to the ELB, it will not get any connections, if we attach both subnets to the ELB then it can access the instances, but it often will get time-outs. Has anyone successfully implemented an ELB within the private subnet of their VPC? If so, could you perhaps explain the procedure to me? Thanks Nathan Pahucki My teammate and I just have implemented ELB in a VPC with 2 private subnets in different availability zones. The reason you get timeouts is that for each