amazon-vpc | 易学教程

EC2 instance has no public DNS

阅读更多关于 EC2 instance has no public DNS

问题 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. 回答1: 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

Connecting to Amazon RDS instance through EC2 instance using MySQL Workbench

阅读更多关于 Connecting to Amazon RDS instance through EC2 instance using MySQL Workbench

问题 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

Amazon ELB in VPC

阅读更多关于 Amazon ELB in VPC

问题 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 回答1: My teammate and I just have implemented ELB in a VPC with 2

Ansible lookup values from complex structure?

阅读更多关于 Ansible lookup values from complex structure?

问题 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" }, ... }

Allow AWS Lambda to access RDS Database

阅读更多关于 Allow AWS Lambda to access RDS Database

问题 I am trying to connect to RDS Database from an AWS Lambda (Java). Which IP should I enable from the RDS Security group rules? 回答1: 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. 回答2: You can configure Lambda to access your RDS instance. You can enable this

Why do we need private subnet in VPC?

阅读更多关于 Why do we need private subnet in VPC?

There are 4 scenarios in AWS VPC configure. But let's look at these two: Scenario 1: 1 public subnet. Scenario 2: 1 public subnet and 1 private subnet. Since any instance launched in public subnet does not have EIP (unless it's assigned), it is already not addressable from the Internet. Then: Why is there a need for private subnet? What exactly are the differences between private and public subnets? Update: in late December, 2015, AWS announced a new feature, a Managed NAT Gateway for VPC . This optional service provides an alternative mechanism for VPC instances in a private subnet to access