forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathdeploying-aws.html.md.erb
195 lines (110 loc) · 6.72 KB
/
deploying-aws.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
---
title: Deploying Operations Manager to AWS
owner: Ops Manager
---
<strong><%= modified_date %></strong>
[Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF) Operations Manager for Amazon Web Services (AWS) is currently in alpha.
This release is neither upgradeable, nor officially supported.
Questions and feedback can be posted to <a href="http://goo.gl/forms/N7Pld5wDyb">http://goo.gl/forms/N7Pld5wDyb</a>.
At present, Pivotal Cloud Foundry® Operations Manager for AWS lacks support for the following components.
Each will be fully supported in the final release.
- Elastic Load Balancer
- RDS
- S3
## Install Pivotal Cloud Foundry® Operations Manager Director ##
1. Log in to your AWS account.
1. Navigate to the VPC Dashboard at
[https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).
1. Click **Start VPC Wizard**.
<%= image_tag("aws/vpc-step1.png") %>
1. Select the second VPC Configuration (VPC with Public and Private Subnets).
<%= image_tag("aws/vpc-step2.png") %>
1. Enter a name for your VPC, keep the other defaults, and click **Create VPC**.
<%= image_tag("aws/vpc-step3.png") %>
1. Navigate to the EC2 Dashboard at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/).
1. Choose **Key Pairs** and click **Create Key Pair**.
<%= image_tag("aws/vpc-step3a.png") %>
1. Create a Key Pair named `pcf`.
Your browser should automatically download the private key.
Save that key to your `~/.ssh directory`.
You will use this in a later step.
1. Return to the EC2 Dashboard at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/).
1. Click **Launch Instance**.
<%= image_tag("aws/vpc-step4.png") %>
1. Search for a Community AMI named "PCF Ops Manager" and click **Select**.
<%= image_tag("aws/vpc-step5.png") %>
1. Choose `m3.xlarge` from the list of instance types and click **Next: Configure Instance Details**.
<%= image_tag("aws/vpc-step6.png") %>
1. Configure the instance to use your VPC, public subnet, and enable Auto-assign for a Public IP.
<%= image_tag("aws/vpc-step7.png") %>
1. Click **Review and Launch**.
1. Create a security group with the following protocols and ports.
<%= image_tag("aws/vpc-step8.png") %>
1. Click **Review and Launch**.
1. Review and click **Launch**.
1. Choose the `pcf` Key Pair that you created.
<%= image_tag("aws/vpc-step8a.png") %>
1. Navigate to the EC2 Dashboard.
1. Navigate to the Instances page.
1. Find the Public DNS of the instance that you created.
<%= image_tag("aws/vpc-step9.png") %>
1. SSH into the Ops Manager instance to fix a couple of minor stemcell issues. These issues will be fixed relatively soon.
<pre class='terminal'>
$ ssh-add ~/.ssh/your-key.pem
$ ssh tempest@your-instance.amazonaws.com
$ sudo su
$ export AWS_ACCESS_KEY_ID={your aws access key}
$ export AWS_SECRET_ACCESS_KEY={your aws secret access key}
$ export REGION={the aws region in the form 'us-east-1'}
$ bash -c "$(curl -fsSL http://goo.gl/0tFVA2)"
</pre>
1. Browse to the DNS address and create a username / password.
<%= image_tag("aws/vpc-step10.png") %>
1. Click on the Ops Manager Director for AWS tile.
<%= image_tag("aws/vpc-step11.png") %>
1. Enter your AWS information in the fields provided and click **Save**.
<%= image_tag("aws/vpc-step12.png") %>
1. Click on Director Config and enter an NTP Server. Click **Save**.
<%= image_tag("aws/vpc-step13.png") %>
1. Click on Create Network, enter network information based on the example below, and click **Save**.
Use the Private Subnet ID, the 10.0.0.2 VPC DNS server, the private subnet gateway (likely 10.1.0.1), and exclude Amazon IPs used at the bottom of the private range.
<%= image_tag("aws/vpc-step14.png") %>
1. Click on Assign Networks and assign the Director to the network that you created.
<%= image_tag("aws/vpc-step15.png") %>
1. Return to the Installation Dashboard and click **Apply Changes**.
Your installation of Ops Manager Director will begin.
1. Once the changes are applied, you should see the following:
<%= image_tag("aws/vpc-step16.png") %>
## Installing Elastic Runtime ##
1. Return to the AWS VPC Dashboard and navigate to the Elastic IPs page.
1. Click **Allocate New Address**. Note: We will use this IP for PCF Elastic Runtime's HA Proxy instance. We have not deployed it yet, but we need to know the address to create an SSL certificate ahead of time.
<%= image_tag("aws/vpc-er-step1.png") %>
1. Click **Allocate New Address**. Note: we will use this IP for PCF Elastic Runtime's HA Proxy instance. We have not deployed it yet, but we need to know the address to create an SSL certificate ahead of time.
<%= image_tag("aws/vpc-er-step1.png") %>
1. Write down the Elastic IP address that you allocated.
1. In a browser, log into the [Pivotal Network](https://network.pivotal.io/).
1. Download the Pivotal Elastic Runtime for AWS release.
1. Navigate to the Pivotal Cloud Foundry® Operations Manager Installation Dashboard and click **Import Product**.
<%= image_tag("aws/vpc-er-step2.png") %>
1. Import the Experimental Pivotal Elastic Runtime for AWS release that you downloaded.
1. Hover over the Pivotal Elastic Runtime product and click **Add**.
<%= image_tag("aws/vpc-er-step3.png") %>
1. Click on the Elastic Runtime tile in the Installation Dashboard.
<%= image_tag("aws/vpc-er-step4.png") %>
1. Navigate to the HAProxy form and enter a free IP address within your private Subnet.
<%= image_tag("aws/vpc-er-step5.png") %>
1. Click on the Generate Self-Signed RSA Certificate link.
1. Use the Elastic IP that you wrote down to generate a wildcard domain. You can do this by using your own Domain registration service, or by using something like xip.io (recommended). Make sure to enter the domain with an asterisk. For example: `*.54.122.3.11.xip.io`
<%= image_tag("aws/vpc-er-step6.png") %>
1. Click **Trust Self-Signed Certificates** and **Save**.
<%= image_tag("aws/vpc-er-step7.png") %>
1. Navigate to the Cloud Controller form and enter System and Application domains according to the wildcard domain that you are using. Do not enter the domain with an asterisk. For example: `54.122.3.11.xip.io`
<%= image_tag("aws/vpc-er-step8.png") %>
1. Click **Save**.
1. Navigate to the Lifecycle Errands form and uncheck the three Post-Install Errands.
<%= image_tag("aws/vpc-er-step9.png") %>
1. Click **Save**.
1. Return to the Installation Dashboard and click the Apply Changes button. Your installation of Ops Manager Director will begin.
1. Once the changes are applied, you should see the following:
<%= image_tag("aws/vpc-step16.png") %>
[Return to the Installing PCF Guide](../installing/index.html)