amazon-vpc

问题 Our Redshift cluster resides in Zone A. When our Lambda function uses a Zone A subnet, it can connect to Redshift. When our Lambda function uses a subnet other than Zone A, it times out. The work around, where we ALLOW connections for Redshift on port 5439 from 0.0.0.0/0, is not desired. We have our Lambda functions and Redshift cluster in the same VPC. Lambda functions have 4 dedicated subnets (one per zone) Redshift has 4 dedicated subnets per zone as well Lambda functions have their own

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . 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

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

问题 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? 回答1: Update: in late December, 2015, AWS announced a new feature, a Managed NAT Gateway for

问题 I have a NodeJS Lambda function running in a private subnet, with allow all incoming/outgoing policies in both the security group and the NACL (not safe, but they do the job). The private subnet has a NAT gateway sitting in a public subnet of the same VPC, so internet connectivity works. My goal is to send messages to an SQS queue. The Lambda code is this: const AWS = require('aws-sdk') const sqs = new AWS.SQS() exports.handler = (event, context, callback) => { sqs.sendMessage({ MessageBody:

问题 I had only one public subnet to VPC,and added NAT gateway to that public subnet, but i'm not able access the instance using NAT ip address. @1)I'm able to ping the instance, with public Ip address(added icmp to security group), but by using NAT elastic IP address i'm not able to ping. @2)Does NAT is applicable for single public subnet or not. My goal is to translate the ip address attached to public subnet instance. 回答1: I believe you are using the wrong service for what you are trying to do.

问题 I'm trying to create a vpc using Saltstack and boto_vpc module. This is my state: vpc_create: module.run: - name: boto_vpc.create - cidr_block: '10.0.0.0/24' - vpc_name: 'myVpc' - region: 'us-east-1' - key: 'ADJJDNEJFJGNFKFKFKIW' - keyid: 'SJDJNFNEJUWLLLCLCLENNRBFLGSLSLKEMFUHE' The keys that I'm using are correct but I got this error : [INFO ] Running state [boto_vpc.create] at time 14:25:35.839797 [INFO ] Executing state module.run for boto_vpc.create [ERROR ] EC2ResponseError: 401

问题 I'm trying to connect Bitnami Certified Kafka AMI with Elastic Beanstalk nodejs environment using kafka-node, how to do that? After installing apache Kafka locally and testing it with Kafka-node successfully, I wanted to test my app with AWS kafka server. I configured my AWS Bitnami Certified Kafka AMI listeners to match my Public DNS (IPv4) and exposed the 9092 and 2181 ports in inbound rules like this: Type protocol port source Custom TCP Rule TCP 9092 0.0.0.0/0 Custom TCP Rule TCP 2181 0.0

问题 I'm attempting to create an instance in another region, but I get this error: AWS Error Code: InvalidParameterCombination, AWS Error Message: VPC security groups may not be used for a non-VPC launch Here is the code I'm executing. RunInstancesRequest instancereq = new RunInstancesRequest(); instancereq.setInstanceType("m3.medium"); instancereq.setImageId("ami-37b1b45e"); instancereq.setMinCount(1); instancereq.setMaxCount(1); ArrayList<String> secgroup = new ArrayList<String>(); instancereq

问题 I'm trying to create a new ElasticBeanstalk application with an Application Load Balancer. I'm calling the following commands: $ mkdir HelloWorld $ cd HelloWorld $ eb init $ echo "Hello World" > index.html $ eb create dev-env --elb-type application Output of the last command results in this error: Creating application version archive "app-170821_175709". Uploading HelloWorld/app-170821_175709.zip to S3. This may take a while. Upload Complete. ERROR: Configuration validation exception: Invalid