aws-samples / aws-net-guides Goto Github PK

Hi,

I am trying to deploy .net core spa with angular cli in lambda serverless model. when I try to access the lambda URL it shows 403-Forbidden error.

.Net core - 2.1
Angular Cli - 6.0.0

Lambda URL as follows
https://p1vu9hp2a8.execute-api.us-east-2.amazonaws.com/Prod

Kindly help me fix this issue.

Thanks
Iyyappan Amirthalingam

Needs updates for product names and screenshots.

• Use of "VSTS" should be replaced with Azure DevOps, including in our own product names
• Screenshots of marketplaces, etc, should be refreshed.
• When creating application in Beanstalk, set context that the Azure DevOps task expects the app and environment to exist (currently not mentioned)
• Update new project workflow to generate an ASP.NET Core 5 project (currently 2.x)
• Use Linux-based EB environment (currently Windows)
• Remove advertorial sections on Visual Studio toolkit; not relevant to this guide

Guide folder: Deployment/ASP.Net_Core_to_ElasticBeanstalk_from_VSTS

Iwas trying to run the serverless sample project Musiquizza-React, but it has a missing reference to AWS cApLib.csproj, i did a clone of the aws-net-guides repo, but i could not find it.

Tnks

Hi,

Managed .net 6 images for EC2 have been referenced here as 'In the near future Elastic Beanstalk will provide managed images that have .NET 6 preinstalled.' for months. Whilst I realise that one can use a self-contained deploy from Visual Studio, that seems to be of little use when attempting to use a codepipeline workflow for deploying apps via elastic beanstalk.

Could you please give a concrete date for when this functionality will be available, as not having any idea when this will be supported is impacting our project planning (and .net 6 has been out for 4 months now!)

Thanks

Hi,
I have deployed lambda serverless app with .Net Core 2.1 + Angular 7.1.4 SPA.

But I don't see any image is rendering from angular.

Please help me with the same.

Thanks

Hey!

I did an automated check for deprecated Lambda runtimes and it seems this project uses the dotnetcore2.0 runtime, which is deprecated since May 2019. If this is using a deprecated runtime, this means that users won't be able to deploy that specific section.

Using grep -nr dotnetcore2.0 *:

Serverless/Serverless Web App with React, DynamoDb, and X-Ray/serverless.template:18:        "Runtime": "dotnetcore2.0",
Serverless/Serverless Web App with React, DynamoDb, and X-Ray/serverless.template:45:        "Runtime": "dotnetcore2.0",

Hello,
I received "Error uploading function" message when I tried to upload my function to AWS Lambda.
The reason of the error is that the framework netcoreapp2.1 is a newer version than Lambda runtime dotnetcore2.0 supports. Please see the picture attached.
I was not able to select the framework version older than netcoreapp2.1 using Upload to AWS Lambda wizard. Please also see the picture attached.

What should I do in order to apply Lambda function implemented in C# language?

Regards
Victor

Examples:

• https://catalog.us-east-1.prod.workshops.aws/v2/workshops/24a39743-7e40-48ca-ba5e-704f2e3d74ec/en-US
• https://catalog.us-east-1.prod.workshops.aws/v2/workshops/c36ccd6e-9145-4e97-b1b5-1069d6d68ed0/en-US
• https://catalog.us-east-1.prod.workshops.aws/v2/workshops/5c59492e-fc61-4a7b-b08a-e0307b70f390/en-US

Small updates to the guide to bring it up to date, and add more samples:

• Switch to new modular PowerShell tools
• Add sample code to show use of the GetParametersByPath api

This is the Documentation that should be referenced as it's directly related to the configuration file you have us set up. Regardless thank you for creating this tutorial! i need to find more info about this particular way of configuring metrics to go to Cloudwatch, and it took me a long time to finally find this link since the method in the tutorial is not mentioned in the CloudWatch documentation pages

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/QuickStartWindows2016.html

Created a DotNet Core 2.1 Console application and added <PackageReference Include="AWSSDK.SimpleSystemsManagement" Version="3.3.118.2" />

Made the changes to Program.cs as per the GitHub code and tried to run.
The error I get in the exception block is "Unable to get IAM security credentials from EC2 Instance Metadata Service."

How are we supposed to test this locally on a development machine?

When is it planned to directly support DotNet 6 (Net 6) runtime Lambda?

Whist it seems it can be done with a custom runtime, it would be great of this was standard.

When will AWS ship the default gravitron instances on Elastic beanstalk with .NET 6 support?

In fact when will all the Elastic beanstalks have .NET 6 runtime support?

https://www.twitch.tv/videos/246611593 does not exist.

Minor updates to freshen the guide

• change to use the modular AWS Tools for PowerShell during backup (restore on the EC2 instance can continue to use pre-installed monolithic tools)
• ensure permissions are scoped down as low as they can be
• revise language in markdown

This guide needs some small updates -

• Update mention of AWS Tools for Windows PowerShell to be AWS Tools for PowerShell, and steer readers to the modular version (so install the AWS.Tools.S3 module)
• As the PowerShell tools handle multi-part upload for you, I think that mention can be removed
• As a best practice, reduce the permissions used to just the bucket involved
• Remove mention of the AWS Tools/PowerShell in the final section, the tools aren't used there (just a standard PowerShell command prompt)

I'm suprised not to see an entry for .Net 8 here yet. It is RTM today.