awslabs / amazon-ecs-nodejs-microservices Goto Github PK

I can't make CloudFormation stack.
When I click create button, 'Template validation error: Template error: Unable to get mapping for AWSRegionToAMI::ap-northeast-2::AMIID' error throws.

Im facing this error when I Run copilot app init on my GitBahs; "
/amazon-ecs-nodejs-microservices (master)
$ copilot app init

What would you like to name our application? [? for help] X prompt get application name: Incorrect function."

BTW
both; copilot and aws --version command confirmed

Hello guys !

Can someone explain what are the rule.json files in each services ?

Thank you

Would it be possible to build a backed with microservices using ECS and then run them through Lambda and API gateway? Would that be recommended for a startup with a couple engs?

navigating to /api/posts fails since there is no router configured for it in server.js
This is as compared to /api/users and /api/threads which return all users and all threads respectively.
Additionally, the tutorial actually recommends testing api and posts services using that url.

The fix is easy...add this to ./3-microservices/services/server.js and /2-containerized/services/api/server.js

router.get('/api/posts', function *() {
  this.body = db.posts;
});

I have done this in a fork (as well as correcting a spelling error).

First I try the output from aws-cli
Got need to use --password-stdin
I change -p to --password-stdin it still not work

It looks like they way your instructions are written you are expecting a node_modules folder to be present in the local directory so that it gets packaged into the container image. As it stands if you clone the repo and then build the image it will not run because npm install has not yet been run. I would suggest either:

1. Update the instructions to have the user run npm install before they docker build so that node_modules gets created. This would obviously also require the user to have Node.js installed on their local workstation, so this leads me to option 2.

2. Add a RUN npm install instruction to your Dockerfile

Unless it's in there and I just missed it - but two people on my team experienced an ERROR 503 when running the app.

Oh, and, this is a great tutorial. Well done!

My students ran into a problem creating a CloudFormation stack with the latest version of ecs.yml.
It seems that AWS Educate accounts cannot execute the GetParameter call.
AccessDenied. User doesn't have permission to call ssm:GetParameters

An earlier version that I downloaded used mappings for the AMIs and does not have this problem. Can you change this back?

As per the npm documentation, a package.json file must contain "name" and "version" fields . But, the "name" and "version" field is missing in all the package.json files in the project.

Hi team,

I am following the link below however after i create a service in the ECS and everything seems to be running fine but i cannot access the site using in my ALB url getting 504 error.

https://aws.amazon.com/getting-started/projects/break-monolith-app-microservices-ecs-docker-ec2/module-two/

Thank you for the tutorial.
I was trying the example in 3-Microservices folder , but I am getting an error when I run CloudFormation template for infrastructure creation.

https://github.com/awslabs/amazon-ecs-nodejs-microservices/blob/master/3-microservices/infrastructure/ecs.yml

Failed to receive 1 resource signal(s) for the current batch. Each resource signal timeout is counted as a FAILURE.

This issue appeared on AWS-CLI v2

An error occurred (InvalidParameterException) when calling the DescribeServices operation: Cluster must match ^[a-zA-Z0-9\-_]{1,255}$, but was myter-HQW81hf613dA