`/aws-micro: line 745: HOME: unbound variable` when calling `aws-micro s3api head-object` and /dev/fd/63: No such file or directory

[mzy2240]

[sengaya]

Could you provide an example as well as information about your system? is $AWS_CONFIG_FILE set? is $HOME set?

[mzy2240]

Im using the latest debian:bullseye-slim docker image. I do have AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY properly set as environment variables, and because I'm running inside the AWS lambda so I assumed I dont need to explicitly set up $AWS_CONFIG_FILE?

[mzy2240]

Is $HOME required?

[sengaya]

That's surprising... would you mind sharing your full command?

Usually, $HOME is automatically set, e.g. if you run debian:bullseye-slim docker image as root it is set to /root.
AWS_CONFIG_FILE is not required and anyway only used by the --profile option at the moment. I might be able to change it in a way that it only fails when really needed.

It would be also helpful if you could share the aws cli output in your environment. I am not sure if this is possible as you run inside a lambda?

[sengaya]

According to https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime it looks like lambda does not set $HOME. I need to think about how to address this. As a workaround, I think it should work if you simply set HOME to some directory, e.g. export HOME=/tmp/foo.

[sengaya]

I followed https://docs.aws.amazon.com/sdkref/latest/guide/file-location.html and v0.4.1 (just released) uses now ~ instead of $HOME. Let me know if that fixes your issue.

[mzy2240]

Still not working. Here is my command: aws-micro s3 cp /tmp/99430.parquet s3://xxxxx/target.parquet, and the error is aws-micro: line 475: /dev/fd/63: No such file or directory

[sengaya]

That one is tricky, likely again related to the lambda environment... could you try the following?
replace in array_sort() the lines

    sorted=()
    while IFS=$'\n' read -r line; do sorted+=("$line"); done < <(sort <<< "${array[*]}")

with

    sorted=($(printf "%s\n" "${array[@]}" | sort))

If it still fail: Run with --debug and share the output. Thanks!

[sengaya]

aws/aws-sam-cli#622 indicates that /dev/fd is not available inside lambda. It would be interesting to know if this is still the case as the ticket and comments are 5+ years old. If true, all anonymous pipes <( ... ) would fail, which is a rather heavy restriction and hard to work around.