Using Amazon SQS dead-letter queue and lambda function to replay messages

Amazon Simple Queue Service (Amazon SQS) is a fully managed message queuing service. It enables you to decouple and scale microservices, distributed systems, and serverless applications. how to add automated resilience to an existing SQS queue. It monitors the dead-letter queue and moves a message back to the main queue to see if it can be processed again.
reference: aws.amazon.com/blogs/compute/....

[@truongtuan2198]

why not set main sqs url in attribute?

[@banalas12]

nice content . Thanks you for making videos . can you please make video how to setup REST API with AWS ECS fargate with SSL

[@raaviblog105]

sure...will work on this one soon.

[@raaviblog105]

Are you trying to do end to end ssl comms? https request terminating on ecs fargate container instead of ALB?

[@raaviblog105]

Incase you are looking to terminate SSL/TLS at ecs fargate container, then would like to know the usecase for it. In my opinion there is no great benefit to use https between the ALB and containers. Comms between ALB target group and container are within AWS network(VPC). You can terminate the SSL connection at target group and send traffic on HTTP to container from there. user ---HTTPS (443)--->ALB----HTTPS(443)--->targetgroup-----HTTP(80)--->ecs fagater