1
0
Fork 0

Doc - Deployment - Missing commit (#5848)

This commit is contained in:
sleto-it 2018-07-11 21:02:41 +02:00 committed by GitHub
parent a75905b62d
commit ccde2a5ea2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions

View File

@ -6,7 +6,7 @@ provider is common choice and many of the most big ArangoDB installation are run
on the cloud.
Up to ArangoDB 3.2, official ArangoDB AMI were available in the [AWS marketplace](https://aws.amazon.com/marketplace/search/results/ref=dtl_navgno_search_box?page=1&searchTerms=arangodb).
Such AMI is not being maintained anymore, though. However, deploying on AWS is
Such AMI are not being maintained anymore, though. However, deploying on AWS is
still possible, and again, a quite common scenario.
After having initialized your preferred AWS instance, with one of the ArangoDB supported

View File

@ -1,5 +1,5 @@
ArangoDB Deploying Options by _Cloud Provider_
==============================================
ArangoDB Deploying Options in the _Cloud_
=========================================
- [AWS](AWS.md)
- [Azure](Azure.md)

View File

@ -248,9 +248,9 @@
* [Troubleshooting](Deployment/Kubernetes/Troubleshooting.md)
* [Mesos, DC/OS](Deployment/DCOS/README.md)
* [Cluster Deployments](Deployment/DCOS/ClusterMesos.md)
* [In the Cloud](Deployment/Cloud/README.md)
* [AWS](Deployment/Cloud/AWS.md)
* [Azure](Deployment/Cloud/Azure.md)
* [In the Cloud](Deployment/Cloud/README.md)
* [AWS](Deployment/Cloud/AWS.md)
* [Azure](Deployment/Cloud/Azure.md)
* [Upgrading](Upgrading/README.md)
* [General Upgrade Information](Upgrading/GeneralInfo/README.md)
* [OS-specific Information](Upgrading/OSSpecificInfo/README.md)