Ashish Dhingra

icon company @aws icon location Seattle WA icon location I work for Amazon Web Services in Dev Support. My thoughts and opinions are my own and do not necessarily represent those of my employer.

Results 383 comments of Ashish Dhingra

Add validation during build time for Handler max length

Also refer https://github.com/aws/aws-lambda-dotnet/issues/1642 where the last character is stripped from the handler name. It's an open issue with the Lambda runtime team and they might plan to fix it in...

Add validation during build time for Handler max length

> While I understand that there is a boundary concern here (still valid), the request is more for the DevX around finding this in the IDE before we execute it...

ec2: Need G6 EC2 Instance support

Per [Amazon EC2 instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html), `G6` is one of the supported instance types. However, it not an option in [InstanceClass](https://github.com/aws/aws-cdk/blob/064cec0ea9e33d34c3217a6435ab5ff9dbfd82ed/packages/aws-cdk-lib/aws-ec2/lib/instance-types.ts#L10). The probable workaround is to use L1 construct. @CambioML Thanks...

Amazon.CDK.AWS.Lex: Property that used to be untyped and is now typed is easy to misuse

Reproducible. It synthesizes into below CFN template (for example): ```YAML Resources: CdktestDotnetStackTestBot: Type: AWS::Lex::Bot Properties: BotFileS3Location: S3Bucket: testbucket S3ObjectKey: testkey DataPrivacy: childDirected: false Description: Bot for the CdktestDotnetStack application. IdleSessionTTLInSeconds:...

Fixed an ElasticBeanstalk deployment issue for Linux platform where Procfile was sometimes being generated with incorrect entrypoint when multiple runtimeconfig.json files were present.

Based on discussion with @normj this is also an issue with AWS .NET Deploy tool. So once we determine optimal fix, we should also port this to deploy tool as...

Fixed an ElasticBeanstalk deployment issue for Linux platform where Procfile was sometimes being generated with incorrect entrypoint when multiple runtimeconfig.json files were present.

Closing this PR in favor of https://github.com/aws/aws-extensions-for-dotnet-cli/pull/363 which was approved and merged.

AWS Lambda Tools for PowerShell: PackageScript & PackageProject parameter sets aren't documented clearly

@sixfootdad Good afternoon. Thanks for opening the issue. Error is reproducible with your scenario giving below message: ```PowerShell Copying local module AWS.Tools.Common(4.1.491) from /Users/REDACTED/.local/share/powershell/Modules/AWS.Tools.Common/4.1.491 Resolved full output package path as...

dotnet-lambda-test-tool-6.0.exe fails with BEX64 Application exception always when launced via Visual Studio, but does not when just ran independently.

@CurtisHerrick Could you try a different machine or an EC2 instance? Refer to similar issue https://learn.microsoft.com/en-us/answers/questions/1878248/after-update-visual-studio-17-10-5-to-17-11-0-our. Could you also try updating your .NET runtime and SDK(s) installed on your machine?...

dotnet-lambda-test-tool-6.0.exe fails with BEX64 Application exception always when launced via Visual Studio, but does not when just ran independently.

@CurtisHerrick Please confirm if you were able to resolve the issue and if it could be closed.

Use SourceGeneratorLambdaJsonSerializer for AspNetCoreServer functions

Needs review with the team.