Remove reading secret manager

README.md

@@ -298,7 +298,9 @@ This document describes the abbreviated process below:
                 "iam:TagUser",
                 "iam:GetUser",
                 "iam:DeleteUser",
-                "iam:CreateAccessKey"
+                "iam:CreateAccessKey",
+                "iam:ListAccessKeys",
+                "iam:DeleteAccessKeys"
             ],
             "Resource": "arn:aws:iam::{{AWS ACCOUNT ID}}:user/smtp_user"
         }

modules/signoz/README.md

@@ -16,12 +16,10 @@ A number of items are needed:
 
 ## Setting up SMTP for alertmanager
 Alertmanager is an additional tool that is deployed to the kubernetes cluster that
-handles forwarding an alert out to 1 or more streams that will recieve the alert.
-The first stream setup is SMTP (Email) through gmail. In order to accomplish this
-the following tasks need to be completed:
-
-1) Create an [App Password](https://support.google.com/accounts/answer/185833?hl=en)
-2) In the account where this application is deployed create an AWS secretmanager secret named: `{cluster_name}/alertmanager_smtp_password` Example: `dpe-sandbox/alertmanager_smtp_password`
+handles forwarding an alert out to 1 or more streams that will receive the alert.
+Alert manager is set to to send emails through AWS SES (Simple Email Service) set up
+by the `modules/sage-aws-ses` terraform scripts. See that module for more information
+about the setup of AWS SES.
 
 ## Accessing signoz (Internet)
 

modules/signoz/templates/values.yaml

@@ -1041,7 +1041,7 @@ alertmanager:
     ALERTMANAGER_SMTP_HOST: email-smtp.us-east-1.amazonaws.com
     ALERTMANAGER_SMTP_PORT: "465"
     ALERTMANAGER_SMTP_AUTH_USERNAME: <Set during helm install>
-    ALERTMANAGER_SMTP_AUTH_PASSWORD: <retrieved from aws secret manager>
+    ALERTMANAGER_SMTP_AUTH_PASSWORD: <Set during helm install>
 
   initContainers:
     init: