Launching secure-by-default SLES on Amazon EC2 instances with Amazon Virtual Private Cloud (VPC)

Transcription

1 Launching secure-by-default SLES on Amazon EC2 instances with Amazon Virtual Private Cloud (VPC) Rick Ashford Mike Friesenegger SUSE Sales Engineer SUSE Sales Engineer

2 SUSE and AWS Partnership Overview SUSE Linux Enterprise Server on Amazon EC2 launched Fall 2010 Available in all AWS regions and instance types Same mission-critical Enterprise Linux from data center to public cloud Seamless support through AWS Support One-click build and simplified management with SUSE Studio and SUSE Manager Trial at no cost through AWS Free Usage Tier Page 2

3 Agenda What are you going to accomplish in this lab? Accessing the lab What you will do during the lab Page 3 Building the Web Server image using SUSE Studio Connecting Studio to AWS Uploading the Web Server image as an EC2 AMI Create Virtual Private Cloud (VPC) Launch the AMI in the private side of the VPC Access the Web Server through public side of the VPC

4 Important items before we begin... Make sure the browser does not block pop-ups Review the pages carefully as you do the lab Page 4 Use the arrows to guide you through the steps Some pages have notes to highlight information Some pages are informational with nothing to do A suggestion - open gedit because some pages ask you to take a note of certain information Please tell us the page number whenever you are having a problem with the lab

5 What are you going to accomplish in this lab?

6 Build a Web Server AMI using SUSE Studio AMI Page 6

7 Upload the Web Server AMI to AWS (Normally you would do this but step has been done ahead of time) AMI Page 7

8 Build an AWS Virtual Private Cloud (VPC) Public Subnet /24 Internet Page 8 Private Subnet /24

9 Launch the Web Server AMI in the Private Subnet Allowing SSH Inbound Public Subnet /24 Private Subnet /24 AMI Internet Page 9 ssh

10 Launch an AWS SLES image in the Public Subnet Allowing SSH Inbound Public Subnet /24 Private Subnet /24 AMI Internet Page 10 ssh ssh

11 Access the Web Server AMI through the Public SLES Image Public Subnet /24 Private Subnet /24 AMI Internet Page 11 ssh ssh

12 How might an AWS VPC be used in your organization? This option is shown on slide 49 Ha rd Page 12 Your Datacenter wa re VP N

13 Accessing the Lab

14 Page 14

15 Page 15

16 Page 16

17 Save files to the desktop... 1 No need to download. Should be on the desktop... 2 Page 17 Right click on index.html and select Save File

18 Ignore the username and password fields above the button and the popup after clicking the button. Page 18

19 Building the Web Server image using SUSE Studio

20 Page 20

21 Use the account of your choice Page 21

22 Page 22

23 Page 23

24 2 3 Page 24 1

25 1 2 Page 25

26 1 2 3 Page 26

27 1 2 Page 27 Browse to the index.html that was saved to the desktop

28 Page 28

29 Page 29

30 Building the image takes around 5 minutes Page 30

31 Connecting Studio to AWS

32 Back to the qwiklab tab 1 Page 32

33 Page 33

34 Copy & paste the Access Keys into a temp document 1 Page 34

35 Stop to learn how to find the AWS Access Keys using slides Thank you.

36 Where can one find the Access Keys in AWS (1 of 2 ways)... This page is for reference. Nothing to do on this page. Page 36

37 Where can one find the Access Keys in AWS (1 of 2 ways continued)... This page is for reference. Nothing to do on this page. Page 37

38 Where can one find the Access Keys This page is for reference. in AWS (2 of 2 ways)... Nothing to do on this page. Page 38

39 Where can one find the Access Keys in AWS (2 of 2 ways continued)... This page is for reference. Nothing to do on this page. Page 39

40 Back to the SUSE Studio tab 1 2 Page 40

41 Paste from the temp document Page 41

42 Uploading the Web Server image as an EC2 AMI

43 Normally the AMI would need to be uploaded to EC2 We are cheating because the AMI is already uploaded... Do not upload for this lab! This is normally what you would see during an upload Page 43

44 Stop to see how to upload the AMI using a CLI. Thank you.

45 Create Virtual Private Cloud (VPC)

46 Back to the qwiklab tab 1 2 Page 46

47 Copy and paste the AWS credentials 1 2 Page 47

48 Page 48

49 Page 49

50 1 2 Page 50

51 Page 51

52 Page 52

53 Page 53

54 Launch the AMI in the private side of the VPC

55 Page 55

56 Make a note of these... Page 56

57 Page 57

58 Page 58

59 Page 59

60 1 2 3 Page 60

61 Page 61

62 Page 62

63 Page 63

64 1 2 Page 64

65 1 2 3 Page 65

66 Save to the desktop... Page 66

67 Page 67

68 1 2 Page 68

69 2 1 Page 69

70 Page 70

71 1 2 3 Verify this is the subnet 4 Page 71

72 Page 72

73 Page 73

74 1 2 3 Page 74

75 Page 75

76 Page 76

77 Page 77

78 The web server running in the private side of the VPC Rename this instance to web server by clicking in the Name area. Page 78

79 Access the Web Server through public side of the VPC

80 Page 80

81 2 1 Page 81

82 Page 82

83 1 2 Verify that the subnet used is / Page 83

84 Page 84

85 Page 85

86 1 2 3 Page 86

87 Page 87

88 Page 88

89 Page 89

90 The SLES server running in the public side of the VPC Rename this instance to public by clicking in the Name area. Page 90

91 Make note of the public hostname or IP address 1 2 Page 91

92 Open a terminal Page 92

93 1 2 Page 93

94 1 Page 94

95 Make note of the web server hostname or IP address 1 2 Page 95

96 1 Page 96

97 1 2 Page 97

98 Page 98

99 We hope you enjoyed the lab!! Thank you.

100 v0.6