@@ -10,11 +10,10 @@ Creating a new instance is straight-forward. You should either use environment v
1010> [ !NOTE]
1111> Environment variables take precedence over shared credentials.
1212
13- ## Using environment variables
14- You can pass required configuration as following environment variables:
15- * ` AWS_ACCESS_KEY_ID `
16- * ` AWS_SECRET_ACCESS_KEY `
17- * ` AWS_REGION `
13+ Once you have an instance of AWS Secrets Manager you gain access to following functions:
14+ * ` CreateSecret(key string, val string, override bool) error `
15+ * ` GetSecret(key string) (AWSSecret, error) `
16+ * ` RemoveSecret(key string, noRecovery bool) error `
1817
1918## Using shared credentials
2019If you have shared credentials stored in ` .aws/credentials ` file, then the easiest way to configure the client is by setting
@@ -23,11 +22,11 @@ If you have shared credentials stored in `.aws/credentials` file, then the easie
2322> [ !WARNING]
2423> Remember, that most probably you will need to manually create a new session for that profile before running your application.
2524
26-
2725> [ !NOTE]
2826> You can read more about configuring the AWS SDK [ here] ( https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html ) .
2927
30- Once you have an instance of AWS Secrets Manager you gain access to following functions:
31- * ` CreateSecret(key string, val string, override bool) error `
32- * ` GetSecret(key string) (AWSSecret, error) `
33- * ` RemoveSecret(key string, noRecovery bool) error `
28+ ## Using environment variables
29+ You can pass required configuration as following environment variables:
30+ * ` AWS_ACCESS_KEY_ID `
31+ * ` AWS_SECRET_ACCESS_KEY `
32+ * ` AWS_REGION `
0 commit comments