Timeout occurring on an attempt to create an IoT thing using a lambda

[kenseii]

Hello,
I am trying to create an AWS IoT thing using a lambda function however a few errors keep raising if the code is run inside a lambda function. If the same code is run in a local binary the device is created without a single error.

on the AWS settings, the lambda is running in a Custom runtime on Amazon Linux 2 on an Arm64 architecture.

let region_provider = Region::new("ap-northeast-1");
let timeout_config = TimeoutConfig::builder()
    .connect_timeout(Duration::from_secs(5))
    .operation_timeout(Duration::from_secs(10))
    .build();
let config = aws_config::from_env().region(region_provider).timeout_config(timeout_config).load().await;
let iot_client = Client::new(&config);

let device_thing = match client
        .create_thing()
        .thing_name(thing_name)
        .send()
        .await {
            Ok(value) => value,
            Err(e) => {
                println!("Could not create the iot thing {:?}", e);
                return Err("Could not create the iot thing".into())
            }
        };

Dependencies

aws-sdk-iot = { version = "0.21.0" }
aws-config = { version = "0.51.0" }
aws-smithy-client = "0.51.0"
aws-smithy-types = "0.51.0"

The Error

While running inside an arm64 lambda function this error occur.

TimeoutError(
RequestTimeoutError {
kind: "operation timeout (all attempts including retries)",
duration: 10s,
},
)

however if the same code is run locally(Arm CPU) the timeout does not happen and the thing is created in the IoT part.

[Note] if the operation timeout is increased to 20 seconds, the timeout error becomes a TransientError send_operation{operation="CreateThing" service="iot"} while attempting to call the ip of iot.ap-northeast-1.amazonaws.com

Also i tried with a non arm64 architecture lambda and the results were the same so i don’t think its CPU architecture related.
Let me know if i am missing something...
Thank you

[jdisanti]

Without more information, this sounds like a Lambda configuration issue. Is the Lambda part of a VPC that is preventing it from talking to the IoT service? Does it work with another language SDK (maybe Python or JS?) on the same Lambda configuration?

Configuring tracing-subscriber to output debug level messages may also be helpful for seeing what's going on.

[kenseii]

Thank you very much, i removed the lambda from the vpc it was using and the problem was solved

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.