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

Commit c7ea3f8

Browse files
committed
Added screenshots to README
1 parent 22607ed commit c7ea3f8

File tree

3 files changed

+15
-5
lines changed

3 files changed

+15
-5
lines changed

README.md

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ will display the metrics captured by the filter described above and display it i
125125

126126
![Dashboard](docs/dashboard.png)
127127

128-
## Launch in Additional Regions (Optional)
128+
## Launch Additional Regions (Optional)
129129

130130
It may be likely that running this solution from a single AWS region is enough to load test your service. However,
131131
if you want to take it a step further, you can deploy Fargate clusters in multiple regions and make it a
@@ -141,10 +141,16 @@ US East (N. Virginia) | us-east-1 | [![Launch in us-east-1](https://camo.githubu
141141
US East (Ohio) | us-east-2 | [![Launch in us-east-2](https://camo.githubusercontent.com/210bb3bfeebe0dd2b4db57ef83837273e1a51891/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f636c6f7564666f726d6174696f6e2d6578616d706c65732f636c6f7564666f726d6174696f6e2d6c61756e63682d737461636b2e706e67)](https://console.aws.amazon.com/cloudformation/home?region=us-east-2#/stacks/new?stackName=DistributedLoadTesting&templateURL=https://s3.amazonaws.com/distributed-load-testing-using-aws-fargate/templates/additional-region.yaml)
142142
US West (Oregon) | us-west-2 | [![Launch in us-west-2](https://camo.githubusercontent.com/210bb3bfeebe0dd2b4db57ef83837273e1a51891/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f636c6f7564666f726d6174696f6e2d6578616d706c65732f636c6f7564666f726d6174696f6e2d6c61756e63682d737461636b2e706e67)](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=DistributedLoadTesting&templateURL=https://s3.amazonaws.com/distributed-load-testing-using-aws-fargate/templates/additional-region.yaml)
143143

144-
Once the stack creation has been completed, go back to the region where you launched the `Master` stack and follow these
145-
steps:
144+
This stack will ask for 2 parameters: The `DockerRegistryURL` and `TaskExecutionRoleArn`. You can find the values for those
145+
parameters in the `Outputs` section of the `Master` CloudFormation stack launched in **Step 1**.
146146

147-
![AddRegion](docs/add-region.gif)
147+
![MasterOutputs](docs/master-outputs.png)
148+
149+
![AdditionalRegionParams](docs/add-region-params.png)
150+
151+
Finally, Once the stack has been completed, you need to tell CodePipeline that a new region has been configured so that
152+
it also launches the Load Tests scenarios in this region. To do this, go back to the region where you launched the `Master`
153+
stack and follow these steps:
148154

149155
1. Go to CodePipeline, then select the pipeline created by the master stack
150156
2. Click on the `LoadTest` step to edit it.
@@ -157,7 +163,11 @@ Name | Value
157163
REGION_2 | Additional region (i.e. us-east-1)
158164
REGION_2_STACK_NAME | CloudFormation stack name (i.e. DistributedLoadTesting)
159165

160-
Save the changes and you are done! You can repeat those steps for every additional region.
166+
*Gif to help demonstrate the steps mentioned above:
167+
168+
![AddRegion](docs/add-region.gif)
169+
170+
Save the changes, run the pipeline and you are done! Repeat those steps for every additional region.
161171

162172
### Monitor All Regions
163173

docs/add-region-params.png

154 KB
Loading

docs/master-outputs.png

208 KB
Loading

0 commit comments

Comments
 (0)