1

I am following the AWS tutorial to create a Webapp here: http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-create-rds.html

I am stuck at the part 'Create a Security Group for Your DB Instance'.

The tutorial instructs you to start writing 'WebserverSG' into the IP source, and to select an option. However, even after completely typing 'WebserverSG', no such option is presented and I am unable to create the security group.

Is there a way to know the source without selecting it from the options? Alternatively, have I done something wrong for the option to not be presented?

This is my first time dealing with AWS; I don't have a concrete understanding of the purpose of security groups - so please bear this in mind!

Thanks in advance for any answers.

  • Start typing sg- in the box for source IP address. Does anything pop up? – Michael - sqlbot Jan 13 '16 at 22:48
0

A couple of things:

  • The tutorial assumes that you have already created an EC2 Security Group named WebServerSG, as shown in the previous step of the tutorial.

  • As of this writing, the auto-complete logic for the field in question keys off of the security group's Group ID rather than the Group Name. The tutorial incorrectly suggests the opposite. You can verify this by typing sg- (all Group IDs begin with sg-) and seeing the drop-down show all of your existing security groups.

Here's how it looks when I try it:

enter image description here

Security Groups are an abstraction that define inbound and outbound traffic rules that you can apply to instances.

The purpose of this exercise is to allow inbound traffic associated with MySQL (we can tell this because the inbound port in the listed rule is 3306 -- commonly associated with MySQL) from your web server(s) to your database server(s).

As demonstrated in the tutorial, you can reference other security groups in the rule definitions to build complex (or in this case, common -- web application servers regularly communicate with database servers) access patterns.

  • Cheers - I didn't name my web server security group WebServerSG. Remaking the security group and launching a new instance has fixed it. – Boyentenbi Jan 14 '16 at 15:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.