@hounddog22030 after I migrated to asp.net core2.1
<PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.0"/>
<PackageReference Include="Amazon.Lambda.Core" Version="1.0.0" /><PackageReference Include="Amazon.Lambda.APIGatewayEvents" Version="1.1.3" />
<PackageReference Include="Amazon.Lambda.AspNetCoreServer" Version="2.0.4" /><PackageReference Include="Amazon.Lambda.Serialization.Json" Version="1.2.0" />
<!-- <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
<PackageReference Include="AWSSDK.Extensions.NETCore.Setup" Version="3.3.4" />
<PackageReference Include="Amazon.Lambda.AspNetCoreServer" Version="2.0.3" /> -->
asp.net logging is controlled by settings in the appsettings.json,
{
"Logging": {
"LogLevel": {
"Default": "Debug",
"System": "Information",
"Microsoft": "Information"
}
}or you can configure it programmatically in Startup.cs, https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-2.1
Hi All,
I have a lambda function which calls REST APIs. I am getting a '404 Client Error: Not Found for url.
But, I am able to access the url from my local machine.
Also, the lambda function can access the internet. I am doing a couple of things which requires internet access.
Is there anything that I may be missing...?
Would appreciate any help here?
Thanks. :)
e.g.
private readonly JsonSerializerSettings _serializerSettings = new JsonSerializerSettings
{
NullValueHandling = NullValueHandling.Ignore,
Formatting = Formatting.None,
MissingMemberHandling = MissingMemberHandling.Ignore,
DefaultValueHandling = DefaultValueHandling.Ignore
};@aabragan We could do like we did for passing in custom converters https://github.com/aws/aws-lambda-dotnet/blob/07ce8b4f06c12e96f357c1647575a63b66d206af/Libraries/test/TestFunctionFSharp/FSharpJsonSerializer/FSharpJsonSerializer.cs
Have a constructor that takes in a JsonSettings. Then you could extend the the serializer and pass your JsonSettings to the base constructor. Then use your serializer in the Lambda serializer attribute.
/// <summary>
/// Constructs instance of serializer.
/// </summary>
public JsonSerializer() : this(null, null)
{
}
/// <summary>
/// Constructs instance of serializer using custom converters.
/// </summary>
public JsonSerializer(IEnumerable<JsonConverter> converters)
: this(converters, null)
{
}
/// <summary>
/// Constructs instance of serializer using custom converters and custom serialization settings.
/// </summary>
public JsonSerializer(IEnumerable<JsonConverter> converters, JsonSerializerSettings settings)
{
if (settings == null)
settings = new JsonSerializerSettings();
settings.ContractResolver = new AwsResolver();
serializer = Newtonsoft.Json.JsonSerializer.Create(settings);
if (string.Equals(Environment.GetEnvironmentVariable(DEBUG_ENVIRONMENT_VARIABLE_NAME), "true", StringComparison.OrdinalIgnoreCase))
{
this.debug = true;
}
if (converters != null)
{
foreach (var c in converters)
{
serializer.Converters.Add(c);
}
}
} /// <summary>
/// Custom Json Serializer based on Amazon's implementation
/// </summary>
public class CustomJsonSerializer : JsonSerializer
{
private static readonly JsonSerializerSettings SerializerSettings = new JsonSerializerSettings
{
NullValueHandling = NullValueHandling.Ignore,
Formatting = Formatting.None,
MissingMemberHandling = MissingMemberHandling.Ignore,
DefaultValueHandling = DefaultValueHandling.Ignore
};
/// <summary>
/// Constructs instance of serializer using custom serialization settings.
/// </summary>
public CustomJsonSerializer() : base(null, SerializerSettings)
{
}
}
Hi there... I use a URL Rewrite to make use a Lambda behind a reverse proxy. (/acme/abc should execute <lambda>/prod/acme/abc). This works fine, but within my code I create an Url with the UrlHelper. Running on my local maschine everything seems to be fine (The link is created as /acme/xyz) but when running within Lamba it ist created as /prod/acme/xyz.
Any Ideas?
Are there any tricks to get the LambdaLogger to log the request id with every message? The closest I've gotten is by using scopes. This gives me a consistent ID for every message within a request, but this is not the actual requestid that AWS generates (see below). I've tried turning on EventIDs, but this doesn't appear to do anything useful. I'm on Amazon.Lambda.Logging.AspNetCore 2.3.0.
Example:
START RequestId: 0398a3a7-a36f-47c4-acf8-62baf867b25c Version: $LATEST
[Information] RequestId:0HLQ7DJ3PSAU1...
I'm looking to have both of RequestIDs to be the GUID assigned by AWS.
