Email notification via SNS when error occurs in CodePipeline

Email notification via SNS when error occurs in CodePipeline. DVA_EN

Email notification via SNS when error occurs in CodePipeline

The content is related to monitoring and troubleshooting, which is also part of the scope of the AWS DVA.

Consider how to notify when an error occurs in a CI/CD environment with CodePipeline.

The AWS official explanation of the notification method is as follows

You can set up notifications so that users of a resource, such as a build project, repository, deployment application, or pipeline, receive emails about the event types you specify according to the notification rule you create.

Notification concepts

This page introduces how to use this notification rule to notify error messages that occur in the pipeline via e-mail through SNS.


Diagram of email notification via SNS when error occurs in CodePipeline.

The basic structure is the same as that described in the following pages.

This is a CI/CD environment for CloudFormation using CodePipeline.

The changes on this page are the following two points

The first is to set up notification rules in CodePipeline.
The rules notify you of any error information that may occur on the pipeline.

The second point is a setting regarding the recipients of notification rules.
The content is notified by e-mail via SNS.

This time, we intentionally cause a failure in the creation of the test stack.
No further action stages in the pipeline will be advanced.
Upon failure, an email is sent via SNS according to the notification rules.

CloudFormation template files

The above configuration is built with CloudFormation.
The CloudFormation templates are placed at the following URL

awstut-dva/05/002 at main · awstut-an-r/awstut-dva
Contribute to awstut-an-r/awstut-dva development by creating an account on GitHub.

Explanation of key points of template files

This page focuses on the contents related to notification rules in CodePipeline.

For other details, please refer to the beginning of this page.

Notification Rule

    Type: AWS::CodeStarNotifications::NotificationRule
      DetailType: BASIC
        - codepipeline-pipeline-action-execution-failed
        - codepipeline-pipeline-stage-execution-failed
        - codepipeline-pipeline-pipeline-execution-failed
        - codepipeline-pipeline-manual-approval-failed
      Name: !Sub "${Prefix}-NotificationRule"
      Resource: !Sub "arn:aws:codepipeline:${AWS::Region}:${AWS::AccountId}:${Pipeline}"
      Status: ENABLED
        - TargetAddress: !Ref TopicArn
          TargetType: SNS
Code language: YAML (yaml)

There are three key points in creating a notification rule.

The first point is the source of the notification.
Specify the ARN of CodePipeline in the Resource property.

The second point is the notification target.
Specify the ARN, etc. of the SNS topic in the Targets property.

The third point is information about the event to be notified.
Specify the ID of the event to be notified in the EventTypeIds property.
The events that can be notified are summarized in the following official AWS page.

Notification concepts - Developer Tools console
Learn about important notification concepts.

In this case, we will specify four Failed notifications related to CodePipeline.



    Type: AWS::SNS::Topic
        - Endpoint: !Ref MailAddress
          Protocol: email
      TopicName: !Ref Prefix
Code language: YAML (yaml)

No special configuration is required.
Specify an e-mail address for the subscriber.

Access Policy

    Type: AWS::SNS::TopicPolicy
          - Principal:
              Service: codestar-notifications.amazonaws.com
            Action: sns:Publish
            Effect: Allow
            Resource: !Ref TopicArn
                aws:SourceAccount: !Ref AWS::AccountId
        - !Ref TopicArn
Code language: YAML (yaml)

When designating an SNS as a notification destination, an important point to consider is the SNS access policy.

Set the access policy according to the following official AWS page

Configure Amazon SNS topics for notifications - Developer Tools console
The easiest way to set up notifications is to create an Amazon SNS topic when you create a notification rule. You can use an existing Amazon SNS topic if it mee...

As above, specify CodeStar as the principal and then allow “sns:Publish”.

CloudFormation-related files

Check the files to run CloudFormation in CodePipeline.

Template File

AWSTemplateFormatVersion: 2010-09-09

    Type: String
    Default: dva-05-002-sample-lambda

    Type: String
    Default: test
    Type: String
    Default: index.lambda_handler
    Type: Number
    Default: 128
    Type: String
    Default: python3.8
    Type: Number
    Default: 5
    Type: AWS::Lambda::Function
        ZipFile: |
          def lambda_handler(event, context):
            print('sample lambda')
      FunctionName: !Sub "${Prefix}-${Environment}-Function"
      Handler: !Ref Handler
      MemorySize: !Ref MemorySize
      Runtime: !Ref Runtime
      Role: !GetAtt LambdaRole.Arn

    Type: AWS::IAM::Role
    DeletionPolicy: Delete
        Version: 2012-10-17
          - Effect: Allow
            Action: sts:AssumeRole
                - lambda.amazonaws.com
        - arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole
Code language: YAML (yaml)

Define Lambda functions and IAM roles.

The key points are the function name (FunctionName) and memory size (MemorySize).
These values are set differently for the test and production stacks according to the template configuration file described below.

Template configuration file for test stack

  "Parameters" : {
    "Environment": "test",
    "MemorySize": "0"
Code language: JSON / JSON with Comments (json)

The value of memory size is the key point.
Dare to specify 0 (MB).
This will cause the stack to fail when it is created.


Use CloudFormation to build this environment and check its actual behavior.

Create CloudFormation stacks

Create CloudFormation stacks.
For information on how to create stacks and check each stack, please refer to the following pages.

After reviewing the resources in each stack, information on the main resources created in this case is as follows

  • SNS Topic: fa-117
  • CodeCommit: dva-05-002
  • CodePipeline: dva-05-002

Email Address Authentication

If you have designated an email address as a subscriber to an SNS topic, you must authenticate that email address.
The following authentication email will be sent to the specified email address.

Detail of SNS 1.

Press “Confirm subscription” to proceed with the authentication.

Detail of SNS 2.

The above page will appear, indicating that authentication has been completed.

Resource Check

Check each resource from the AWS Management Console.
First, check the SNS topic.

Detail of SNS 3.

An email address is specified as a subscriber to the SNS topic.

Check CodePipeline

Detail of CodePipeline 1.

The pipeline is failing to execute.
This is because the pipeline was triggered by the creation of CodeCommit when the CloudFormation stack was created.
Since we are not pushing code to CodeCommit at this time, an error occurred during the pipeline execution process.

Check the notification rules.

Detail of CodePipeline 2.

Indeed, a notification rule has been created.

You can see that the aforementioned SNS topic is specified as the notification destination and that it is enabled.
This means that CodeStar is properly authorized to notify messages to the SNS topic.

Details will also be confirmed.

Detail of CodePipeline 3.

The contents of sending a Failed notification regarding CodePipeline.

Operation Check

Now that you are ready, push the code to CodeCommit.

$ git clone https://git-codecommit.ap-northeast-1.amazonaws.com/v1/repos/dva-05-002
Cloning into 'dva-05-002'...
warning: You appear to have cloned an empty repository.
Code language: Bash (bash)

An empty repository has been pulled.

Add three files (sample-lambda.yaml, test-stack-configuration.json, and prod-stack-configuration.json) to the repository.

$ ls -al
total 12
drwxrwxr-x 3 ec2-user ec2-user  118 Jan 22 11:31 .
drwxrwxr-x 4 ec2-user ec2-user  151 Jan 22 11:31 ..
drwxrwxr-x 7 ec2-user ec2-user  119 Jan 22 11:31 .git
-rw-rw-r-- 1 ec2-user ec2-user   98 Jan 18 12:43 prod-stack-configuration.json
-rw-rw-r-- 1 ec2-user ec2-user 1667 Jan 18 11:40 sample-lambda.yaml
-rw-rw-r-- 1 ec2-user ec2-user   95 Jan 21 11:55 test-stack-configuration.json
Code language: Bash (bash)

Push 3 files.

$ git add .

$ git commit -m 'first commit'
 create mode 100644 prod-stack-configuration.json
 create mode 100644 sample-lambda.yaml
 create mode 100644 test-stack-configuration.json

$ git push
 * [new branch]      master -> master
Code language: Bash (bash)

The push was successful.
The pipeline has now started.

After a short wait, the pipeline fails midway.

Detail of CodePipeline 4.

Failed to create test stack.
As mentioned earlier, this is due to the fact that the memory size of the Lambda function is set to “0”.

An email was immediately sent to

Detail of SNS 4.

Three emails were received.
They indicate that errors occurred in Pipeline execution, Stage execution, and Action execution.

Also check the CloudFormation stack.

Detail of CloudFormation 1.

Indeed, the creation of the test stack has failed.

By creating a notification rule and specifying an SNS topic as the recipient of the notification, we were able to send email notifications of errors during CodePipeline execution.


We have introduced a method of email notification via SNS when an error occurs in CodePipeline.