AWS For Developers For Dummies
Book image
Explore Book Buy On Amazon
Any code you deploy using EB becomes immediately public at the URL provided in the URL field unless you change the security rules for AWS. This means that you really do need to verify that the page is safe to display before you deploy it. However, you can also make the page private by following these steps:
  1. Choose Services → EC2 from the menu at the top of the page.

    You see the EC2 Dashboard page.

  2. Choose Network & Security → Security Groups from the Navigation pane.

    EC2 displays a list of security groups. The selected security group in the figure is the one used with EB.

    EC2 security groups The EC2 security groups contain the security group used to configure EB.
  3. Select the security group entry for EB configuration and choose Actions → Edit Inbound Rules.

    EC2 displays the Edit Inbound Rules dialog box. You can change any configuration option for the security group that will modify the way in which incoming requests work. For example, you can change the HTTP type to HTTPS to create secure access to the page. However, in this case, you can use a simpler method to secure access to the page in a reasonable way: Simply disallow access from sources other than your system.

    restrict access AWS Modify the rules to ensure that access remains restricted.
  4. Choose My P in the Source field for both HTTP and SSH access of the security group.

    EC2 modifies the rules as expected.

    To make this setup work, you must also provide access to the website to the instance security group. Otherwise, when you attempt to perform updates, the updates will fail.

  5. Click Add Rule.

    You see a new rule added to the list.

  6. Choose All Traffic in the Type field and All in the Protocol field.

    These two settings provide complete access to the security group.

  7. Choose Custom in the Source field and type sg in the text field after it.

    You see a listing of security groups for your server. A source can consist of a Classless Inter-Domain Routing (CIDR) address, IP address, or security group ID. Typing sg tells EC2 that you want to use a security group. Note that one of the security groups in the list specifically mentions the AWSEBSecurityGroup, which is the security group that you want to use.

    choose security group AWS Choose an existing security group to allow instance access to your EB setup.
  8. Click the security group for the website instance in the list.

    The security group appears in the Source field.

  9. Click Save.

    The inbound security rules now prevent access to the site by any entity other than the website instance or you.

The IP address supplied when you choose My IP in the Source field uses the IP address of your current location. If other people use the same router (and therefore the same IP address), they also have access to the website. Consequently, setting the inbound rules does help provide security, but only a certain level of security. In addition, the IP address can change when you reset the router and then reconnect to the Internet provider. Consequently, you may find that you lose access to the test site you’ve created because of the change in IP address. If you suddenly find that you have lost access, verify that your IP address hasn’t changed.

About This Article

This article is from the book:

About the book author:

John Mueller is an author and technical editor who has written 103 books. Some of his current works include Python development books. He has also written AWS For Admins For Dummies, which provides administrators a great place to start with Amazon Web Services (AWS). John has had an interest in AWS since its inception. In fact, he wrote Mining Amazon Web Services based on that humble beginning. Be sure to read John's blog at

This article can be found in the category: