Skip to content

Commit a3c7af4

Browse files
committed
Revise blog content for AWS Step Functions and API Gateway
1 parent 9ec349e commit a3c7af4

4 files changed

Lines changed: 4 additions & 4 deletions

File tree

content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/79stnH5l6.png renamed to content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/architecture-overview.png

File renamed without changes.

content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/TEHFmfnqq.jpg renamed to content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/postman.jpg

File renamed without changes.

content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/xllkWB6Fm.jpg renamed to content/en/posts/aws-step-functions-with-api-gateway-and-sam/images/workflow-triggered.jpg

File renamed without changes.

content/en/posts/aws-step-functions-with-api-gateway-and-sam/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Let's start!
1818

1919
In this post, we will deploy a basic Step Functions workflow behind an API Gateway that a simple POST request as below will trigger:
2020

21-
![Architecture Overview](images/79stnH5l6.png)
21+
![Architecture Overview](images/architecture-overview.png)
2222

2323
And because we use AWS SAM, it will only take us a few lines of YAML. Nothing more!
2424

@@ -206,13 +206,13 @@ Our work is now deployed on AWS and ready to be triggered!
206206

207207
For instance, with Postman:
208208

209-
![Postman](images/TEHFmfnqq.jpg)
209+
![Postman](images/postman.jpg)
210210

211211
And the associated result in AWS:
212212

213-
![Workflow triggered](images/xllkWB6Fm.jpg)
213+
![Workflow triggered](images/workflow-triggered.jpg)
214214

215-
### Conclusion
215+
## Conclusion
216216

217217
You attached an API Gateway to a Step Functions workflow with AWS SAM! 🎉🎉
218218

0 commit comments

Comments
 (0)