aws-security-group

From the doc: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#security-group-rules Source or destination: The source (inbound rules) or destination (outbound rules) for the traffic. Specify one of these options: (...) Another security group. This allows instances associated with the specified security group to access instances associated with this security group. This does not add rules from the source security group to this security group. You can specify one of the following security groups: The current security group. As someone tried it? I created 2 boxes

When trying to deploy my application, I recently got the following error: ERROR: Service:AmazonCloudFormation, Message:Stack named 'awseb-e-123-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: The following resource(s) failed to update: [AWSEBRDSDatabase]. ERROR: Updating RDS database named: abcdefg12345 failed Reason: DB Security Groups can no longer be associated with this DB Instance. Use VPC Security Groups instead. ERROR: Failed to deploy application. How do you switch over a DB Security Group to a VPC Security Group? Steps for using the Elastic Beanstalk

Docker containers behind ELB get dynamic ports which are auto registered with ELB so that they can get traffic redirected to them. In order to make your web servers accessible to ELB you have to open all these ports 1024 - 65535 originating from within your security group. Is there a way to not to have to open up a security group to a range of port but only to the pots that ELB is using? Security groups are never modified by AWS as this might cause conflicts and security issues. The only exception would be services such as Elastic Beanstalk. You'd likely have to do what the forum says and

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

I have an EC2 instance running in AWS. When I try to ping from my local box it is not available. How can I make the instance pingable? Rakib Add a new EC2 security group inbound rule : Type: Custom ICMP rule Protocol: Echo Request Port: N/A Source: your choice (I would select Anywhere to be able to ping from any machine) alkar You have to edit the Security Group to which your EC2 instance belongs and allow access (or alternatively create a new one and add the instance to it). By default everything is denied. The exception you need to add to the Security Group depends on the service you need to