Getting "identity cache miss occurred" log entry with AWS Lambda

[vladaman]

I get the following log entry in Cloudwatch when running Rust runtime in AWS Lambda. Is that a configuration issue or a bug?

INFO Lambda runtime invoke{requestId="9f50ca91-e776-4aec-90bc-57d3d003d8b0" xrayTraceId="Root=1-658162c3-fe3f11cc0b249b792cec2b0c;Parent=2542046d007332d4;Sampled=0;Lineage=4dc74012:0"}:lazy_load_identity: 354: identity cache miss occurred; added new identity (took Ok(16.254µs))

Getting client:

let shared_config = aws_config::defaults(BehaviorVersion::latest()).load().await;
let cli = Client::new(&shared_config);

Logger Configuration:

#[tokio::main]
async fn main() -> Result<(), Error> {
    env_logger::init();
    tracing_subscriber::fmt()
        .with_max_level(tracing::Level::INFO)
        .with_line_number(true)
        // disable printing the name of the module in every log line.
        .with_target(false)
        // disabling time is handy because CloudWatch will add the ingestion time.
        .without_time()
        .init();

    run(service_fn(function_handler)).await
}

[jdisanti]

It's perfectly normal. It just means the credentials weren't already cached, so it cached them. It also happens when the credentials expire and it needs to refresh them. You can change the log level for the aws-smithy-runtime to warn if you don't want to see it in the logs.

[orf]

IMO this shouldn't be an info log though? It's more of a debug message

[orf]

#1107