
First I created a notification rule for my pipeline.

Rule creation would require a name ( obviously ) and events that should be notified and a target system that the notification should send.
Since I would prefer to receive all the events, I choose all and Slack as the target.

Since my newly created Slack channel is not yet registered as a target I attempted target creation.

Not it is time for me to configure the chatbot. I create a new client.

AWS offered me two options for the client Slack and AWS Chime, I proceed with Slack and it directed me to Slack for authorization for the Slack workspace.


Once I authorized, there are a few more additional configurations needed to do.
What Slack channel should be connected to? What sort of privileges I should allow to the chatbot and what are the guard rules I should create?

Since my only intention is to view what's going on with my CI/CD pipeline, I just set AWS read-only access for both allowed rule and guard conditions.
I triggered my pipeline and started to flood my channel with all the events.


Microservices have become a popular architectural style for building large-scale and complex applications. One of the key aspects of microservices is how they communicate with each other. In this blog post, we'll explore different communication patterns used in microservices and take a closer look at REST APIs, which are widely used for inter-service communication. We'll also discuss the advantages and disadvantages of using REST APIs based on my experience in a current project.
Beiryu
Contributor

Public speaking is a skill that can open doors to countless opportunities, both in personal and professional life. However, for many people, the thought of standing in front of an audience and delivering a presentation can be daunting. The fear of public speaking, also known as glossophobia, is one of the most common phobias. But with the right mindset and techniques, anyone can overcome this fear and become a confident presenter.
Beiryu
Contributor