English subtítols

← GitHub Integrations • Setting up GitHub Enterprise on AWS

Obtén el codi d'incrustació
5 llengües

Showing Revision 10 created 11/18/2014 by Jenny Lam-Chowdhury.

  1. ♪ (jazzy music) ♪
  2. Hi, I'm Brent Beer
  3. with Github's training team.
  4. Millions of developers
    in the world's best companies
  5. use GitHub to streamline
    the way they build and ship software.
  6. Now with support for
    Amazon Web Services, or AWS,
  7. GitHub Enterprise offers the same
    great experience to system administrators.
  8. In this video we're going to take a look
  9. at how to acquire the GitHub AMI
    to deploy our instance,
  10. setting things up
    from the AWS Web Console,
  11. and lastly, starting up our instance
  12. to begin building
    and shipping great software.
  13. To get started, let's visit
    enterprise.github.com
  14. and click Try for Free
    in the upper right-hand corner.
  15. On this screen we need to fill out
    some information about our organization
  16. which is typically
    the name of our company,
  17. our full name,
    and some contact email address.
  18. This information will be used to sign in
    to our GitHub Enterprise web account.
  19. Fill out my full name.
  20. I'm going to go ahead and select
    GitHub on AWS as our installation type.
  21. Then lastly, we're going to fill out
    some common questions here
  22. for our GitHub support,
    so they know best how to help us
  23. if we run into any issues along the way.
  24. Click the terms of use,
    and then Continue.
  25. On this screen we have three options
  26. of how to launch
    our GitHub Enterprise on AWS trial.
  27. The method that we're going to be using
    in this screencast
  28. will be the last option we see
    down here in the very bottom section.
  29. If we want a different AMI ID,
    we can select a different region
  30. with the Edit button in the upper corner.
  31. Simply select your own region
    from this option,
  32. and save changes.
  33. We're going to be using US East 1
    in this screencast.
  34. Let's go ahead and copy that AMI ID,
  35. put that on our clipboard,
    and also click
  36. the Download your License button
    on the right hand portion of the screen.
  37. Then go ahead and open a new tab
    to go to aws.amazon.com.
  38. Once here, click Sign in to the console
  39. so that we can visit our console
    to launch our instances.
  40. Enter your password,
  41. and click EC2
    in the upper left-hand corner.
  42. This is where we're going to be launching
  43. all of our Amazon web service
    instances from.
  44. From here, click Launch Instance
    to start creating our instance.
  45. We're going to click Community AMI
  46. so we can search for that AMI ID
    that was presented to us
  47. after we signed up
    with GitHub Enterprise.
  48. Search for that AMI ID that you had
  49. by typing it in into the Search field.
  50. and click Enter.
  51. Click Select once you see
    that AMI presented to you.
  52. We recommend starting
    with an r3.large instance type.
  53. On the next screen we don't have
    any custom configuration details,
  54. so we can skip this and add storage.
  55. We do need to add
    an additional volume here.
  56. This EVS volume
    needs to be at least 10 GB.
  57. I'm going to set it to 12,
    just for growth purposes.
  58. This EVS volume
    is going to be used for Git data
  59. as well as general user data.
  60. Next we're going to tag the instance.
  61. We're want to give this
    a name and value scheme
  62. so that it's easy
    to identify this instance
  63. when looking at our dashboard.
  64. I'm going to call this ghe-aws.
  65. Next we have our security groups.
  66. These security groups are going to be
    so that we can control
  67. what ports have access to our instance,
  68. as well as which ports we can use
    when doing management console activities.
  69. I have an existing security group
    configured already
  70. and I want to talk
    about some of these settings.
  71. A number of these settings
    are going to be used
  72. for Git data, and Git traffic,
  73. as well as emails, or email servers,
    as we can see, SMTP and SMTPS,
  74. as well as access to our
    Management Console over a different port,
  75. as well as a custom SSH port to port 122.
  76. This is going to be used for
    when we need to SSH into this machine.
  77. After we have all of these custom ports
    as well as default ports selected,
  78. we can review and launch our instance.
  79. We have one last step
    to review everything here.
  80. Once we're OK with it,
    we can click Launch.
  81. Before we actually launch our instance,
  82. we need to create a SSH key pair.
  83. I'm going to name this ghe-aws as well,
  84. and click Download.
  85. That'll download to my computer,
  86. then I can use that as I need to
    when I need to SSH into this machine.
  87. Once that's downloaded,
    click Launch Instance.
  88. This should be launching
    and initialized in a few minutes
  89. so we'll go ahead and give that
    a little bit to finish up
  90. and then we can visit our instance
    to finish the configuration.
  91. When ready, let's grab the public DNS
  92. presented to us at the bottom
    of the screen here.
  93. I'm going to put that onto my clipboard
    and open a new tab
  94. and visit this address.
  95. Now, because we have
    a self-signed SSL certificate,
  96. we do want to give everyone
    a little bit of a heads-up here
  97. that on the next screen
    we will be prompted
  98. with a little bit of a warning here.
  99. So depending on Safari, Firefox or Chrome,
  100. we can see different prompts.
  101. We will go ahead and detect
  102. which browser
    you're currently viewing this in
  103. and instruct you on the next steps
    to get past that screen.
  104. If you really wanted to double-check this,
  105. we can SSH into the machine
    to verify this certificate.
  106. We have steps for that below.
  107. Click Continue to Set up.
  108. Continue past the prompt.
  109. Now we need to upload
    our GitHub Enterprise license
  110. that we got when we signed up
    for GitHub Enterprise.
  111. So, click License file,
  112. grab that license,
    that .ghl file,
  113. and finish the installation.
  114. Before we finish configuring our instance,
  115. we need to create a management console
  116. as well as API password.
  117. This means even our site admins,
    as they choose to browse
  118. into the management console
    to alter configuration settings,
  119. they will need to type
    this password to get in.
  120. Choose a password that you know
    everyone else will be able to share,
  121. as well as using a password generator
    to generate this.
  122. I'm going to choose New Install
    for this screencast.
  123. Lastly, we have one last step before
    we start our instance configuration
  124. We get to review all of our steps.
  125. If we have any DNS,
    we want to change our host name,
  126. our authentication as we choose
    to set up an LDAP or SAML server
  127. for authentication into this instance,
  128. we can add those here.
  129. We can also revisit these settings
    after our instance is up and running.
  130. Let's go ahead
    and scroll down to the bottom
  131. and Save Settings so that we
    can start configurating the instance.
  132. Let's go ahead and speed this up
    so we can move forward with this demo.
  133. Once you're instance is finished,
    click Visit Your Instance to begin.
  134. Before we can get started
    inviting people to our instance,
  135. because we have built-in authentication,
  136. we need to create our first admin account.
  137. This is of course true for regardless
    of which authentication we have.
  138. Pick a username and an email address,
  139. as well as a password that is generated
  140. from some auto-generating
    password application for you.
  141. Next, we want to start out
    with at least one organization
  142. so that new members of this instance
    can have collaboration
  143. around a different project together.
  144. We're going to call this
    organization name internal-tools.
  145. And the email for this
  146. should be set as well,
  147. and create that organization.
  148. Now, if we had other people
    on our instance already,
  149. we could invite additional
    team members to this,
  150. but for now, we'll just start out
    with services admin in this.
  151. Now that our instance is up and running,
  152. we can go back and revisit
    that management console
  153. if we need to finish some configuration,
  154. or we could start inviting people
    to join into this enterprise instance
  155. to start building great software.
  156. For more information
    about GitHub Enterprise
  157. and GitHub Enterprise on AWS,
  158. visit enterprise.github.com/AWS
  159. Thanks for watching this episode
    on getting started
  160. with GitHub Enterprise
    on Amazon Web Services.
  161. With GitHub Enterprise on AWS
  162. software developers
    and system administrators
  163. can both use the tools
    they know and love.
  164. ♪ (jazzy music) ♪