Can we not have general layers for dotnet based lambdas?

[varkey98]

I have some config files which I would like to be put in as a lambda layer zip.
I create the layer like this:

 aws s3 cp ./build/config-${RUNTIME}-${FRAMEWORK}.zip s3://${BUCKET_NAME}/dotnet/${zip_name}

aws lambda publish-layer-version --layer-name ${layer_name} \
  --content S3Bucket=${BUCKET_NAME},S3Key=dotnet/${zip_name} \
  --compatible-runtimes ${COMPATIBLE_RUNTIME} --compatible-architectures ${COMPATIBLE_ARCHITECTURE}  \
  --description "Lambda Layer targeting .NET" --query 'LayerVersionArn' --output text

But looks like these fies are not accessible to my lambda. Can someone pls help?

[ashishdhingra]

@varkey98 Please refer to similar issue #599 reported in 2020. There is a blog post shared by user in comment #599 (comment) which could be helpful.

[normj]

What do you mean by the layer not being accessible? I assume when you are deploying your Lambda function you are assigning the layer to the function. The files will be accessible in the /opt directory in the Lambda environment.