Device Storage on AWS node

[Deepesh Nandal]

Hi,

 We are thinking to buy AWS node as suggested on https://craftercms.org/downloads/. I would like to know if the AWS node is optimised to run crafterCMS like how it is specified on url  https://docs.craftercms.org/en/3.1/system-administrators/activities/authoring-env-performance-tuning.html ?

Regards,

Deepesh Nandal.

[Sumer Jabri]

These are optimized and ready for use. You should buy `m5.xlarge` or higher for authoring. Delivery does benefit from being `c5.large`.

If you're going to run serverless, consider one authoring (or two if a stateful cluster), and 4 stateless delivery nodes in a scale-group. If serverless, you'd want to use 3.1.4+ (build from `develop` or wait for the final release soon).

--sumer

[Deepesh Nandal]

Hi Thanks for the reply !

I have bought AWS m5.xlarge. However we need to start authoring with solr and not elastic search. On my custom local installation I would just do "startup.sh withSolr" on console. How do we do this on AWS node ?

Regards, 

Deepesh Nandal.

[Sumer Jabri]

Edit the `systemd` configuration file to add that parameter. The file is located here `/etc/systemd/system/crafter.service `

```

[Unit]

Description=Crafter CMS Authoring

Documentation=http://docs.craftercms.org

[Service]

User=crafter

Group=crafter

ExecStart=/opt/crafter/bin/startup.sh withSolr

ExecStop=/opt/crafter/bin/shutdown.sh

RemainAfterExit=true

[Install]

WantedBy=multi-user.target

```

Reload systemd and make sure the new configuration is loaded.

--sumer

[Deepesh Nandal]

Thanks a lot, this works :-)