Skip to content
This repository was archived by the owner on Sep 28, 2022. It is now read-only.

Commit 753a5f5

Browse files
committed
Minor format change to README file
1 parent afbf32e commit 753a5f5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

examples/elasticsearch/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
### Load Testing an Amazon Elasticsearch Cluster
1+
## Load Testing an Amazon Elasticsearch Cluster
22

33
This example assumes that your Elasticsearch cluster is behind a VPC and not exposed publicly to the internet. However,
44
either way is possible to test. Having it publicly accessible makes it even easier.
@@ -9,7 +9,7 @@ To start, follow all the instructions
99
in the main [README](https://github.com/aws-samples/distributed-load-testing-using-aws-fargate/blob/master/README.md),
1010
except for **Step 2 and 4** in which you need to do the following changes instead.
1111

12-
#### Instead of Step 2
12+
### Instead of Step 2
1313
Open the [Dockerfile](https://github.com/aws-samples/distributed-load-testing-using-aws-fargate/blob/master/Dockerfile)
1414
in the root directory of the project and uncomment the elasticsearch instruction and comment out the http one. It should
1515
look like this:
@@ -32,7 +32,7 @@ documents to be indexed in the cluster, while the consumer will issue *search* r
3232
If you look at the `taurus.yml` file, you can see both scenarios specified, which means that Taurus will execute both
3333
scripts in parallel.
3434

35-
#### Instead of Step 4
35+
### Instead of Step 4
3636

3737
In the case of your Elasticsearch cluster running behind a VPC, the easiest option would be run the Fargate Docker tasks
3838
in the same VPC. So, follow **Step 4** just as described in the main [README](https://github.com/aws-samples/distributed-load-testing-using-aws-fargate/blob/master/README.md)

0 commit comments

Comments
 (0)