Crates.io | aws-parameters-and-secrets-lambda |
lib.rs | aws-parameters-and-secrets-lambda |
version | 1.0.0 |
source | src |
created_at | 2023-01-06 17:56:01.435215 |
updated_at | 2024-03-25 22:27:20.214525 |
description | Cache AWS Secrets Manager secrets in your AWS Lambda function |
homepage | https://docs.rs/aws-parameters-and-secrets-lambda/ |
repository | https://github.com/Tom01098/aws-parameters-and-secrets-lambda |
max_upload_size | |
id | 752445 |
size | 53,756 |
Cache AWS Secrets Manager secrets in your AWS Lambda function, reducing latency (we don't need to query another service) and cost (Secrets Manager charges based on queries).
Add the AWS Parameters and Secrets Lambda Extension layer to your Lambda function. Only version 2 of this layer is currently supported.
Assuming a secret exists with the name "backend-server" containing a key/value pair with a key of "api_key" and a value of
"dd96eeda-16d3-4c86-975f-4986e603ec8c" (our super secret API key to our backend), this code will get the secret from the cache, querying
Secrets Manager if it is not in the cache, and present it in a strongly-typed BackendServer
object.
use aws_parameters_and_secrets_lambda::Manager;
use serde::Deserialize;
#[derive(Deserialize)]
struct BackendServer {
api_key: String
}
let manager = Manager::default();
let secret = manager.get_secret("backend-server");
let secret_value: BackendServer = secret.get_typed().await?;
assert_eq!("dd96eeda-16d3-4c86-975f-4986e603ec8c", secret_value.api_key);
Thorough documentation for this crate is available on docs.rs.
This crate is licensed under the MIT or Apache 2.0 license, at your option.