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
which looks for credentials in a set of defined locations and use those
38
-
credentials to authenticate requests to AWS.
39
-
40
-
The default credentials provider chain searches for credentials in one of the following locations using a predefined sequence:
41
-
42
-
1. Java system properties
43
-
2. Environment variables
44
-
3. Web identity token from AWS Security Token Service
45
-
4. The shared credentials and config files
46
-
5. Amazon ECS container credentials
47
-
6. Amazon EC2 instance IAM role-provided credentials
48
-
49
-
## AWS S3 Config Provider
37
+
## AWS S3 Configuration Provider
50
38
The Oracle DataSource uses a new prefix `jdbc:oracle:thin:@config-awss3:` to be able to identify that the configuration parameters should be loaded using AWS S3.
51
39
Users only need to indicate the S3 URI of the object that contains the JSON payload.
52
40
@@ -85,8 +73,7 @@ And the JSON Payload for the file **payload_ojdbc_objectstorage.json** in **mybu
85
73
"user": "scott",
86
74
"password": {
87
75
"type": "awssecretsmanager",
88
-
"value": "test-secret",
89
-
"key_name": "db-password"
76
+
"value": "test-secret"
90
77
},
91
78
"jdbc": {
92
79
"oracle.jdbc.ReadTimeout": 1000,
@@ -128,11 +115,6 @@ For the JSON type of provider (AWS S3, AWS Secrets Manager, HTTP/HTTPS, File) th
128
115
- Base64 Encoded password (if base64)
129
116
- GCP resource name (if gcpsecretmanager)
130
117
- AWS Secret name (if awssecretsmanager)
131
-
- Text
132
-
- key_name
133
-
- Optional
134
-
- Possible values
135
-
- Name of the key, if stored as key-value pairs in AWS Secrets Manager
The JSON Payload retrieved by AWS Secrets Manager Provider follows the same format in [AWS S3 Configuration Provider](#json-payload-format).
150
132
133
+
## Common Parameters for Centralized Config Providers
134
+
AWS S3 Configuration Provider and AWS Secrets Manager Configuration Provider
135
+
share the same sets of parameters for authentication configuration.
136
+
137
+
### Configuring Authentication
138
+
139
+
The Centralized Config Providers in this module use the
140
+
[Default credentials provider chain](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials-chain.html) to provide authorization and authentication to S3 and Secrets Manager services.
141
+
The user can provide an optional parameter `AUTHENTICATION` (case-ignored) which is mapped with the following Credential Class.
which searches for credentials in one of the following locations using a predefined sequence:
165
+
166
+
1. Java system properties
167
+
2. Environment variables
168
+
3. Web identity token from AWS Security Token Service
169
+
4. The shared credentials and config files
170
+
5. Amazon ECS container credentials
171
+
6. Amazon EC2 instance IAM role-provided credentials
172
+
173
+
For more details, please refer to [Default credentials provider chain](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials-chain.html).
174
+
175
+
### AWS Region
176
+
177
+
In this project, region can be specified from two places:
178
+
1.`AWS_REGION` as an optional parameter in URL
179
+
2.[Default region provider chain](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/region-selection.html#automatically-determine-the-aws-region-from-the-environment).
180
+
181
+
If `AWS_REGION` is specified in the URL, the provider uses it as the value of Region for authentication. Otherwise, the value from default region provider chain will be applied.
182
+
151
183
## Caching configuration
152
184
153
185
Config providers in this module store the configuration in caches to minimize
0 commit comments