AWS Trusted Advisor

Well 就在今天Amazon 宣布了一個Beta版的新服務，叫做AWS Trusted Advisor，這項服務的功能其實就是之前MeshCloud所提到的系統診斷分析功能，看到的當下我就想到上面那張圖，這些功能本來就是大廠(鋼鐵人，蝙蝠俠)應該要提供卻沒有提供，所以我們小廠(蜘蛛人)，就是找到這些空隙和Niche點，提供加值服務，但是如果大廠真的要自己跳下來做(那我們也只能哭哭)，的確會有不少壓力，不過也沒那麼悲觀，畢竟我們提供的是Hybrid Cloud的服務，所以除了服務Amazon的客戶，還可以同時服務其他IaaS的客戶，更何況，目前這個服務

These new features are available for all Gold and Platinum customers

只給大客戶~~~只給大客戶用~~~~，是要多大才算Gold and Platinum級客戶呢？[1]
呼 ～那我們來看看Amazon 將會提供哪些功能：

1. Security Group - Open Ports - This check inspects your security groups and classifies each open port into one of three categories. Green ports for common protocols such as SSH and HTTP, Red ports for protocols that don't usually need to be open on internet-facing servers (e.g. port 1443 for Microsoft SQL Server), and Yellow for all others. (系統安全分析，看有沒有開哪些port是危險的)
2. Security Group - CIDR Rules - This check inspects your security groups for rules that have errors which might allow more access than may be intended. Some people (me included) often confuse "/0"and "/32" addresses. (幫你檢查Rule是否有設定好)
3. Reserved Instance Recommendations - This check looks at your billing and instance utilization history and recommends optimizations that could be achieved by the purchase of Reserved Instances. (檢視你的用量，建議是否要改用Reserved Instance)
4. Unused Elastic IP Addresses - Elastic IP Addresses that are not attached to an Amazon EC2 instance will be flagged since you pay for them if you don't use them.(幫你檢查是否有申請了Elastic IP卻沒有使用)
5. EBS Snapshots - This check looks for EBS volumes that don't have a snapshot, or which have only aged snapshots. The Red/Yellow/Green model is also used here: Red if there is no snapshot at all or if the most recent one is very old; Yellow if the most recent snapshot is somewhat old, and Green if the most recent snapshot is reasonably recent (we're still fine tuning the thresholds for these checks). (是不是每個EBS都有定期做Snapshot)
6. Amazon EC2 Availability Zone Balance - This check identifies situations where Amazon EC2 instances are not evenly distributed across Availability Zones, or if (even worse) they are all in the same Availability Zone. The Red/Yellow/Green model is used to characterize the situation.(檢查機器是否過度集中，是否有把你的服務均勻的散在不同的Zone，以免一個Zone掛了，你的服務就停擺了)
7. Elastic Load Balancer Optimization - This check determines whether instance allocation across Availability Zones for each Load Balancer is balanced.(檢查Load Balancer 的設定是否是最佳化)
8. Service Limits - This check gives you visibility into the per-account limits and usage of things like instances, Elastic IP addresses, and other resources (in almost every case, limits can be raised using the appropriate online form). (你可以針對所有的Resource設定一個ThreshHold，然後Amazon會幫你確認是否有到達你設定的Threshold)

其實這些東西的確透過API 都很容易查到，下圖就是Amazon 在Blog上所畫的架構圖，唯一的差別就是我們不只是連AWS而已。

Reference:
[1] AWS Support Pricing