You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 5, 2025. It is now read-only.
* Version bump and update AMIs to be worldwide
Signed-off-by: Irving Popovetsky <[email protected]>
* Reduce unhealthy threshold from 10 minutes to 2 and double the check frequency
Signed-off-by: Irving Popovetsky <[email protected]>
* upload files to S3 bucket on tags automatically. Update python version to latest. test marketplace.yaml
Signed-off-by: Irving Popovetsky <[email protected]>
* speedup and smartify travis
Signed-off-by: Irving Popovetsky <[email protected]>
* Some JMESPath magic in order to ensure we get the latest AMI
Signed-off-by: Irving Popovetsky <[email protected]>
* Major reliability improvement: Make the Chef Server frontend ASG automatically rebuild instances that go unhealthy, but not bootstrap instances. Add cloudwatch alerts for all unhealthy hosts. Add clarity about the email address to the PREREQS.md doc
Signed-off-by: Irving Popovetsky <[email protected]>
* bump AMIs again to pick up Automate 20190722 release
Signed-off-by: Irving Popovetsky <[email protected]>
Copy file name to clipboardExpand all lines: PREREQS.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,20 +14,27 @@ You must create or upload at least one SSL certficate to AWS Certificate Manager
14
14
In the parameters, fill in the `ChefSSLCertificateARN`, `AutomateSSLCertificateARN` and `SupermarketSSLCertificateARN` values with the ARNs for the certificates. The ARNs are always viewable in the ACM console, an example ACM ARN looks like: `arn:aws:acm:us-west-2:446539779517:certificate/82d30a13-b420-4f43-80de-9e7872f70b96`
15
15
16
16
17
-
## Network
17
+
###Network
18
18
19
19
You must already have a VPC setup properly before continuing setting up the stack, it should;
20
20
21
21
* Have enough IP's available to assign to nodes
22
22
* Be split up into 3 subnets, each in different Availability Zones (AZ's)
23
23
* Provide the VPC ID and associated subnets to the `VPC` and `ServerSubnets` parameters
24
24
25
-
## Security
25
+
### Contact Email Adress
26
+
27
+
Supply a valid email address or team/DL alias here. Cloudwatch alerts will be sent to this address!
28
+
29
+
* At stack launch time you will receive an email titled `AWS Notification - Subscription Confirmation`
30
+
* It's important you click the `Confirm subscription` button in this email or else you will not receive notifications
31
+
32
+
### Security
26
33
27
34
* You should already have created/uploaded an SSH key to AWS. Provide the keypair name to the `KeyName` parameter
28
35
* If you're using the `main.yaml` stack, you must also create a security group in the referenced VPC to define your administrative access. Provide sg ID to the `InboundAdminSecurityGroupId` parameter
29
36
30
-
## Amazon Elasticsearch and Service Linked Role (SLR)
37
+
###Amazon Elasticsearch and Service Linked Role (SLR)
31
38
32
39
Amazon Elasticsearch requires a specific SLR to be created prior to running this CloudFormation template, specifically one called `AWSServiceRoleForAmazonElasticsearchService`. This role cannot be created programmatically as it is created automatically when setting up a VPC access domain in the AWS console. For more information on this [please see this doc from AWS](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/slr-es.html), at this time, even though the doc points to a way to create this manually via the CLI, it still only works via console setup, however AWS adds new features all the time, and by the time you do this, it may work programmatically, please follow their documentation. Once you've created the VPC access domain for AWS ElasticSearch, you can then delete this domain, the role will still be there and you should be able to continue.
0 commit comments