You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to test our Aries Issuer, Verifier and Mediator instances in their "native location" -- e.g. in a Kubernetes cluster that we already have established. As such, we need to set up Locust in to run in a powerful environment -- e.g. on AWS, but we don't need to setup and run the Aries instances. It would be good to have the guidance in (probably) NON-CLUSTERED.md to highlight what is needed for that setup, and what can be ignored in the document.
The text was updated successfully, but these errors were encountered:
swcurran
changed the title
In the document on setting up AWS, it would be nice to have a section highlighting the steps for only running Locust on AWS
In the document on setting up AWS, it would be nice to have a section highlighting the steps for running only Locust on AWS
Jan 9, 2024
We want to test our Aries Issuer, Verifier and Mediator instances in their "native location" -- e.g. in a Kubernetes cluster that we already have established. As such, we need to set up Locust in to run in a powerful environment -- e.g. on AWS, but we don't need to setup and run the Aries instances. It would be good to have the guidance in (probably) NON-CLUSTERED.md to highlight what is needed for that setup, and what can be ignored in the document.
The text was updated successfully, but these errors were encountered: