Skip to content

Commit

Permalink
Update documentation detail links
Browse files Browse the repository at this point in the history
  • Loading branch information
hsoerensen committed Feb 5, 2024
1 parent df6cffc commit f06ebc4
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/notification-guides/amazon-ses.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ A solid understanding of DNS and Amazon AWS is required, including knowledge on
## Configuring Amazon SES

!!! info
Full configuration options and capabilities are available via [Apprise](https://github.com/caronc/apprise/wiki/Notify_pushbullet)
Full configuration options and capabilities are available via [Apprise](https://github.com/caronc/apprise/wiki/Notify_ses)

1. Create an IAM user that has access to SES. The user should have a programmatic access key and secret key.
2. Attach the [following policy](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/control-user-access.html) to the user:
Expand Down
2 changes: 1 addition & 1 deletion docs/notification-guides/email.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ The current setup allows you to use your own email provider, and we do not have
## Using Live.com to Send Email

!!! note
Full configuration options and capabilities are available via [Apprise](https://github.com/caronc/apprise/wiki/Notify_pushbullet)
Full configuration options and capabilities are available via [Apprise](https://github.com/caronc/apprise/wiki/Notify_email)
and may be required depending on your email provider and/or SMTP configuration.

1. Create a new email account used only for notifications. This is to ensure that your main email account is not compromised if the notification email account is compromised.
Expand Down

0 comments on commit f06ebc4

Please sign in to comment.