Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New serverless pattern: s3 trigger fargate task #2379

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jeromevdl
Copy link
Contributor

Issue #, if available: #2378

Description of changes:

Adding a new pattern: S3 -> EventBridge -> Fargate, using CDK / Typescript

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link
Contributor

@ellisms ellisms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeromevdl Thanks for the submission. Requesting a few minor changes.

@@ -0,0 +1,83 @@
# Amazon S3 to AWS Fargate

This pattern demonstrates how to trigger an AWS Fargate task when an object is uploaded to Amazon S3.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This pattern demonstrates how to trigger an AWS Fargate task when an object is uploaded to Amazon S3.
This pattern demonstrates how to invoke an AWS Fargate task when an object is uploaded to Amazon S3.

```
2. Change directory to the pattern directory:
```
cd serverless-patterns/s3-teventbridge-fargate-cdk
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be s3-eventbridge-fargate-cdk.

# get log streams
aws logs describe-log-streams --log-group-name /ecs/doc-ingestion
# use the latest log stream name in the next command to get logs
aws logs get-log-events --log-group-name /ecs/doc-ingestion --log-stream-name doc-ingestion-logs/DocIngestion/...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify getting the stream name from the previous output.

aws logs get-log-events --log-group-name /ecs/doc-ingestion --log-stream-name doc-ingestion-logs/DocIngestion/...
```

4. You should see the content of your file in the logs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
4. You should see the content of your file in the logs.
4. The file contents are displayed in the log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants