Unable to deploy CloudFormation stack to localstack

[hem-bhagat-tark]

I am using dotnet lambda deploy-serverless command to deploy a serverless application as CloudFormation stack on localstack. I have created a profile for localstack as follows.

[profile localstack]
region = us-east-1
output = json
endpoint_url = http://localhost:4566

I have mentioned the profile in aws-lambda-tools-defaults.json,

{
    "profile": "localstack",
    "region": "us-east-1",
    "stack-name": "some-stack",
    "s3-bucket": "some-bucket",
    "configuration": "Release",
    "s3-prefix": "lambda/",
    "template": "serverless.template",
}

However, when I run the command dotnet lambda deploy-serverless, I get error

Error uploading to lambda/AspNetCoreFunction-CodeUri-Or-ImageUri.zip in bucket some-bucket: The AWS Access Key Id you provided does not exist in our records.

But, if I set the endpoint URL to http://localhost:4566 using AWS_ENDPOINT_URL env variable before running the command, I get error

Error uploading to lambda/AspNetCoreFunction-CodeUri-Or-ImageUri.zip in bucket some-bucket: No such host is known. (some-bucket.localhost:4566)

This suggests that the dotnet lambda command is not reading the endpoint_url from profile. Also, it seems like it is using virtual-hosted style URLs which is not working with localstack expecting path style URL (ex: http://localhost:4566/some-bucket).

How can I deploy to localstack using this tool?

[ashishdhingra]

@hem-bhagat-tark Good morning. I'm unsure it would work, you may try setting service specific endpoint_url as specified here. Also, we do not support deployments to 3rd party solutions that mimic AWS environment. If it works with some setting, then it's great, but SDK(s) and tools are not guaranteed to work with such 3rd party solutions.

Thanks,
Ashish