d38803217cedb8ac02be4139c211c3fa9d11b1e9
wiki/info/landscape/aws-automation.md
| ... | ... | @@ -1 +1,79 @@ |
| 1 | -Test |
|
| ... | ... | \ No newline at end of file |
| 0 | +# AWS Automation |
|
| 1 | + |
|
| 2 | +This page describes the functionality of a bash script that automates the setup of SAP Sailing Analytics instances. |
|
| 3 | + |
|
| 4 | +## Importance |
|
| 5 | + |
|
| 6 | +- Avoiding misconfiguration of instances due to human mistakes |
|
| 7 | +- Allowing fast reaction times to external needs (e.g. horizontal scaling) |
|
| 8 | +- Saving time |
|
| 9 | + |
|
| 10 | + |
|
| 11 | +## Scenarios |
|
| 12 | + |
|
| 13 | +- SAP instance on a dedicated EC2 instance |
|
| 14 | +- SAP instance on a shared EC2 instance |
|
| 15 | +- SAP instance on a dedicated EC2 instance as a master |
|
| 16 | +- SAP instance on a dedicated EC2 instance as a replica |
|
| 17 | + |
|
| 18 | +## Basics |
|
| 19 | + |
|
| 20 | +### 1. Example setup: SAP instance on a dedicated EC2 instance |
|
| 21 | + |
|
| 22 | +Login to the [https://aws.amazon.com/console/](AWS Web Console). |
|
| 23 | +Account number: 017363970217. |
|
| 24 | + |
|
| 25 | +Parameters necessary for EC2 instance: |
|
| 26 | + |
|
| 27 | +- Keypair |
|
| 28 | +- Instance type (e.g. t2.medium) |
|
| 29 | +- Security group |
|
| 30 | +- Image |
|
| 31 | +- User Data |
|
| 32 | + |
|
| 33 | +Example of content for parameter User Data: |
|
| 34 | + |
|
| 35 | +<pre> |
|
| 36 | +MONGODB_HOST=123.123.123.123 |
|
| 37 | +MONGODB_PORT=27017 |
|
| 38 | +MONGODB_NAME=wcsantander2017 |
|
| 39 | +SERVER_NAME=wcsantander2017 |
|
| 40 | +USE_ENVIRONMENT=live-server |
|
| 41 | +INSTALL_FROM_RELEASE=build-201803302246 |
|
| 42 | +SERVER_STARTUP_NOTIFY=leon.radeck@sap.com |
|
| 43 | +</pre> |
|
| 44 | + |
|
| 45 | +### 2. SAP instance configuration |
|
| 46 | + |
|
| 47 | +[Image] |
|
| 48 | + |
|
| 49 | +Necessary configuration steps: |
|
| 50 | + |
|
| 51 | +- Create event in admin console |
|
| 52 | +- Create new user account with permissions for that event |
|
| 53 | +- Change admin password |
|
| 54 | + |
|
| 55 | +If instance home page or event page should be reachable by a specific URL: |
|
| 56 | + |
|
| 57 | +Add one of the following lines to /etc/httpd/conf.d/001-events.conf: |
|
| 58 | +<pre> |
|
| 59 | +Use Home-SSL [instance name].sapsailing.com 127.0.0.1 8888" |
|
| 60 | +</pre> |
|
| 61 | +<pre> |
|
| 62 | +Use Event-SSL [instance name].sapsailing.com “[event id]“ 127.0.0.1 8888 |
|
| 63 | +</pre> |
|
| 64 | + |
|
| 65 | +Then check and reload apache configuration by entering the commands: |
|
| 66 | +<pre> |
|
| 67 | +apachectl configtest |
|
| 68 | +sudo service httpd reload |
|
| 69 | +</pre> |
|
| 70 | + |
|
| 71 | +## 3. Load Balancer configuration |
|
| 72 | + |
|
| 73 | +To reach the SAP instance by a specific URL (e.g. wcsantander2017.sapsailing.com), follow these steps: |
|
| 74 | + |
|
| 75 | +- Create target group with |
|
| 76 | + |
|
| 77 | + |
|
| 78 | + |