AWS Secrets Manager

Learn to store secrets using AWS Secrets Manager integration.

What Is AWS Secrets Manager?

AWS Secrets Manager can be used to Securely store and tightly control access to tokens, passwords, certificates, API keys, and other secrets


Many of our services that require secrets, such as cloud provider integrations, can work out of the box with this service. In the configuration where you need to supply the password, username, or URL, you need to write the secret’s name in the AWS Secrets Manager starting with the prefix smaws_. If you have turned off the Secrets Manager, but you want to store secrets through environmental variables, you can still do that. First, keep the secret in an environmental variable. Then, in the config, instead of the prefix smaws_, use env_ followed by the name of the environmental variable where you stored the secret.

 "executionSettings": {
      "executionType": "regular",
      "defaultBrowser": "chrome",
      "defaultLifeCycle": "restart every time",
      "resolution": "",
      "browserVersion": "",
      "url": "",
      "arguments": [
          "name": "{runName}",
          "platform": "Windows",
          "version": "86",
          "recordVideo": "true",
          "recordScreenshots": "true",
          "screenResolution": "1920x1080x24",
          "username": "smaws_saucelabuser",
          "accessKey": "smaws_accessKey"

Another way how you can use directly the integration is through to services SecretsManager and SecretsResolver.

string keyVaultValue = new SecretsManager().getSecret("saucelabuser");
var _uri = new SecretsResolver().getSecret(() -> ConfigurationService.getSection<ReportingSettings>().getUrl());

The core difference is that SecretsManager directly connects and returns the value for the secret in the key vault. At the same time, SecretsResolver also checks whether there is a set environmental variable on the execution machine matching the secret name.