amazon-vpc

I'm trying to insert records into a Postgres database in RDS from a Lambda function. My Node.js lambda function works correctly when run locally, but the database connection times out when run in AWS. I've read several articles and tutorials which suggest that AWS Lambda functions cannot access RDS instances that are within a VPC. For example: http://ashiina.github.io/2015/01/amazon-lambda-first-impression/ Unfortunately; it seems I am unable to create an RDS instance that exists outside of a VPC. At this dropdown I would expect to be able to select an option for "No VPC" or something along

I have a Play 2 web application, which I deploy to Elastic Beanstalk using Docker. In this web app, I start an Akka cluster. The starting procedure involves adding all nodes in the autoscaling group as seed nodes (including itself). On the first deploy to EB I specify to deploy to a VPC (I only select one availability zone). When I run the app and start the cluster, I get the following message: AssociationError [akka.tcp://cluster@localhost:2551] -> [akka.tcp://cluster@172.31.13.25:2551]: Error [Invalid address: akka.tcp://cluster@172.31.13.25:2551] [ akka.remote.InvalidAssociation: Invalid

My Redshift cluster is in a private VPC. I've written the following AWS Lamba in Node.js which should connect to Redshift (dressed down for this question): 'use strict'; console.log('Loading function'); const pg = require('pg'); exports.handler = (event, context, callback) => { var client = new pg.Client({ user: 'myuser', database: 'mydatabase', password: 'mypassword', port: 5439, host: 'myhost.eu-west-1.redshift.amazonaws.com' }); // connect to our database console.log('Connecting...'); client.connect(function (err) { if (err) throw err; console.log('CONNECTED!!!'); }); }; I keep getting Task

I am using serverless framework for creating lambdas. I created a simple Lambda function, which queries from an mongo instance and returns the response. Initially, I created the mongo instance with publicIp and made the Lambda access that instance with publicIP. It worked well. Now, in order to increase the security, I added the VPC configuration to the Lambda. Here is my serverless.yml: functions: graphql: handler: handler.graphql iamRoleStatements: - Effect: Allow Resource: "*" Action: - ec2:CreateNetworkInterface - ec2:DescribeNetworkInterfaces - ec2:DetachNetworkInterface - ec2

When trying to figure out how to configure a aws_instance with AWS VPC the following errors occur: * Error launching source instance: InvalidParameterCombination: The parameter groupName cannot be used with the parameter subnet status code: 400, request id: [] or * Error launching source instance: InvalidParameterCombination: VPC security groups may not be used for a non-VPC launch status code: 400, request id: [] This is due to how a security group is associated with an instance. Without a subnet it is OK to associate it using the security group's name: resource "aws_instance" "server" { ...

Things I have done: $ vi /etc/hosts Added IPAddress Hostname I want to automate this process like every new instance I launch should have an entry in /etc/hosts Guess you need add the host itself in /etc/hosts. Put this in user data when you create a new ec2 instance #!/usr/bin/env bash echo `ec2-metadata -o|cut -d: -f2` " " `ec2-metadata -h |cut -d: -f2` >> /etc/hosts 来源： https://stackoverflow.com/questions/27739618/automatically-add-an-entry-in-etc-hosts-file-in-newly-launched-amazon-ec2-insta