Advisory · Low severity
SES Identity Unverified / Unusable
Mail sent from this identity is rejected, so a notification path that looks configured is silently delivering nothing.
Free to start. No card. The playground just needs your work email.
AWSprovider
Lowseverity
Advisorywhere it shows up
Guidedfix, after a review
AWS
Found, explained, fixed.
What we would change and why, with no savings claim and no policy behind it.
01
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
02
Explain
Every finding says exactly what to change: Verify SES identity.
03
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- SES Identities on AWS
- Category
- Advisory. Findings worth knowing about that carry no dollar figure and no one-click action. Each comes as a numbered playbook.
- Where it appears
- The Advisory tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1526- Full reference
Related checks
See the advisory findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.