aws-samples / container-patterns Goto Github PK

In what area(s)?

Describe the proposal

I have a long Python script which takes 20+ minutes to run. It generates a report after a user submits details in the client. This needs to take unique parameters each run, access third party APIs whilst running and be scalable but also have a limited number of maximum runs to ensure third party API rate limits aren't breached.

I have been playing around with AWS but unable to find something straightforward to meet these needs, although I'm sure does exist.

Good evening

Let me first say thank you for providing this tutorial

nginx-reverse-proxy-sidecar-ecs-fargate-task

I have followed the tutorial and when it came to deploying using the command below:

sam deploy \
  --template-file parent.yml \
  --stack-name nginx-reverse-proxy \
  --resolve-s3 \
  --capabilities CAPABILITY_IAM \
  --parameter-overrides AppImageUrl=$APP_URI NginxImageUrl=$NGINX_URI

I came across the following error
Error: Invalid value for '--parameter-overrides': AppImageUrl= is not in valid format. It must look something like 'ParameterKey=KeyPairName,ParameterValue=MyKey ParameterKey=InstanceType,ParameterValue=t1.micro' or 'KeyPairName=MyKey InstanceType=t1.micro'

This article explains why:

invalid-value-for-parameter-overrides

Therefore I replaced the variables withAppImageUrl=APP1 and NginxImageUrl=NGINX1 and was able to deploy.

If this was what one is supposed to do, then the article does not state this or maybe things have change since the article was published. I thought I would mention in case anyone who is new to AWS might encounter this issue.

many thanks.

Numel

On page pattern/ecs-ec2-bottlerocket-cluster/index.md the content points to a previous version and older variant of Bottlerocket.

I'm glad to take the updates, if that's amenable.

When deploying the application, the tasks are not starting due to Cuda Error.
The image put in the CDK (with tag 9.0) is not found and so the task is not starting.

I would like to have a template to be able to deploy the same container image to either lambda or Fargate.

As #24 has been merged, it's still unclear to users how to use the L3 construct in the CDK code. I have created aws/aws-cdk#26435 in hope to include this in the upstream aws-ecs-patterns module. Will update here when we have new progress.

ECS service running with Fargate and API Gateway through VPC link and Cloud Map service discovery is an interesting pattern. As this has recently been discussed on Twitter, I would like to wrap it up and contribute to container-patterns.

This is a tracking issue and the PR will be created soon.