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
Copy file name to clipboardExpand all lines: docs/FAQs.md
+33-33Lines changed: 33 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,6 @@ Instead, set a specific classifier of the `aws-crt` to use the one for your targ
79
79
By specifying the specific target runtime, we prevent other target runtimes from being included in the jar file, resulting in a smaller Lambda package and improved cold start times.
80
80
81
81
```xml
82
-
83
82
<dependencies>
84
83
<dependency>
85
84
<groupId>software.amazon.awssdk</groupId>
@@ -108,39 +107,40 @@ Depending on the Powertools module, there is a different way to configure the SD
108
107
109
108
The following example shows how to use the Lambda Powertools Parameters module while leveraging the AWS CRT Client.
// We might instead want to retrieve multiple parameters at once, returning a Map of key/value pairs
136
+
// .getMultiple("/my/secret/path");
137
+
138
+
// Return the result
139
+
return value;
142
140
}
143
-
```
141
+
}
142
+
```
143
+
144
144
The `aws-crt-client` was considered for adoption as the default HTTP client in Lambda Powertools for Java as mentioned in [Move SDK http client to CRT](https://github.com/aws-powertools/powertools-lambda-java/issues/1092),
145
145
but due to the impact on the developer experience it was decided to stick with the `url-connection-client`.
0 commit comments