3.5 KiB
title, type, source-type, category, tags, date-added, video-source, audio-source, status
| title | type | source-type | category | tags | date-added | video-source | audio-source | status | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CTP Topic 36 SendGrid as an email service | cloud-learning | video | DevOps & SRE/08_Networking |
|
2026-04-14 | nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4 | summarized (Gemini 摘要) |
CTP Topic 36 SendGrid as an email service
Source: NAS /volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4
Type: VIDEO | Category: 08_Networking
Status: 🟡 Awaiting Whisper transcription → Summary
摘要
Cloud Transformation Program: SendGrid Email Service & Cyber Suite Standards
The Cloud Transformation Program session covered the adoption of SendGrid as a standard email service and provided an update on Cyber Suite standards. Rejoy Ganapati and Rajiv presented SendGrid, while Yu-Yan provided the Cyber Suite update.
SendGrid is being adopted as the standard email service for both classic and new landing zones, replacing the existing semantic message gateway and SES solutions. The existing semantic message gateway has security concerns because it relays mail to the public internet through port 25, which is not secure. Additionally, the relay servers are not compatible with cloud environments and are hosted on a soon-to-be-decommissioned on-premises network. The current SES setup has a limitation of only 50 recipients per message.
SendGrid overcomes these issues by allowing up to 1,000 recipients per message and being fully cloud-compatible. Almost 30 billion emails per month customers are already used across the whole country. It offers real-time monitoring logs, two-factor authentication, and end-to-end encryption using TLS. The support plan covers 5 million emails per month. Two architectures are available: direct sending to SendGrid (requires TLS) and relaying via servers for applications lacking TLS support. We were looking for the maximum number of recipients per message. Data flow involves relay servers in various locations (London, India, Tokyo, etc.) sending mail through private circuits to a US-based data center for processing.
Key configuration requirements for direct sending include using the software.microcopy.com domain, connectivity to smtp.sendgrid.net on port 587, and TLS enablement. Domain-specific email blocking is not supported, and the sender email address must use the software.microcopy.com domain. Email logs are retained for seven days, and API keys are rotated every 180 days for security. SPF and DKIM records are essential for valid email sending to avoid emails landing in junk folders or being rejected.
Yu-Yan from PSAC provided an update on Cyber Suite standards, presenting an updated version of the standard Cyber Suite documentation. The updated documentation includes a list of Cyber Suites considered standard by different industry standards like FIPS, Java, Golang, Node.js, and OpenCel for CNC++. An optional Cyber Suite is available for backward compatibility, but it includes CBC (Cipher Block Chaining) which is considered weak. For more choices, products can select cyphers from different portions, including K exchange, authentication, encryption, and hash. It is recommended that products using cyphers outside the standard and optional suites be reviewed by the PSAC team.
关键概念
行动项
相关视频
配对视频笔记链接（生成后填入）
最后更新: 2026-04-14