はじめに テクニカルサポートの 片方 です。 AWS ではマネージドノードになっていない原因を調査する方法として、SSM Automation Runbook “AWSSupport-TroubleshootManagedInstance” を提供しています。 この Runbook を使用すると以下の観点で調査を行い、設定不足や誤りがないかを自動で調査してくれます。 セキュリティグループルール VPC エンドポイント ネットワークアクセスコントロールリスト (ACL) ルール ルートテーブルなどインスタンスの VPC 設定 必要なアクセス許可を含む AWS Identity and Access Management (IAM) インスタンスプロファイルがインスタンスにアタッチされているか やってみた 1.　SSM マネジメントコンソール画面へアクセス 2.　下部の左ペイン [共有リソース] セクションの ドキュメントをクリック 3.　Amazon が所有を選択 ⇒ 検索窓に “AWSSupport-TroubleshootManagedInstance” を記載 4.　ドキュメントを選択 5.　右上 [オートメーションを実行する] を選択 6.　Simple execution を選択 7.　Input parameters の InstanceId において、Show all instances を選択 8.　調査対象の EC2 インスタンスを選択 ※ 当該設定をしている IAM ユーザーにドキュメン記載の権限許可が存在しない場合は、当該権限を有するロール作成をしてロールください。その後、AutomationAssumeRole に当該ロールを設定してください。 試したところドキュメント記載の権限ではなぜかエラーが発生するため、以下を参考にロール作成してください。 信頼関係 サンプルポリシー 9.　右下の [Execute] をクリック これで以上です。調査完了まで待ちましょう。 既にマネージドノードの場合 [WARNING] として、VPC エンドポイント、インターネットへのアクセス経路がない場合 参考資料 AWSSupport-TroubleshootManagedInstance – AWS Systems Manager オートメーションランブックリファレンス Troubleshoot why an EC2 instance doesn’t show as a managed instance | AWS re:Post アノテーション株式会社について アノテーション株式会社は、クラスメソッド社のグループ企業として「オペレーション・エクセレンス」を担える企業を目指してチャレンジを続けています。「らしく働く、らしく生きる」のスローガンを掲げ、様々な背景をもつ多様なメンバーが自由度の高い働き方を通してお客様へサービスを提供し続けてきました。現在当社では一緒に会社を盛り上げていただけるメンバーを募集中です。少しでもご興味あれば、アノテーション株式会社WEBサイトをご覧ください。

Emergency AWS job support in USA: EC2 crashes, Lambda failures & S3 issues. 24/7 cloud deployment help. AWS dominates cloud market—constant deployment challenges need expert solutions.

AWS Health now includes two new properties in its event schema - actionability and persona - enabling customers to identify the most relevant events. These properties allow organizations to programmatically identify events requiring customer action and direct them to relevant teams. The enhanced event schema is accessible through both the AWS Health API and Health EventBridge communication channels, improving operational efficiency and team coordination. AWS customers receive various operational notifications and scheduled changes, including Planned Lifecycle Events. With the new actionability property, teams can quickly distinguish between events requiring action and those shared for awareness. The persona property streamlines event routing and visibility to specific teams like security and billing, ensuring critical information reaches appropriate stakeholders. These structured properties streamline integration with existing operational tools, allowing teams to effectively identify and remediate affected resources while maintaining appropriate visibility across the organization. This enhancement is available across all AWS Commercial and AWS GovCloud (US) Regions. To learn more about implementing these new properties, see the AWS Health https://docs.aws.amazon.com/health/latest/ug/aws-health-concepts-and-terms.html and the https://docs.aws.amazon.com/health/latest/APIReference/Welcome.html and https://docs.aws.amazon.com/health/latest/ug/aws-health-events-eventbridge-schema.html schema documentation.

AWS Health now includes two new properties in its event schema - actionability and persona - enabling customers to identify the most relevant events. These properties allow organizations to programmatically identify events requiring customer action and direct them to relevant teams. The enhanced event schema is accessible through both the AWS Health API and Health EventBridge communication channels, improving operational efficiency and team coordination. AWS customers receive various operational notifications and scheduled changes, including Planned Lifecycle Events. With the new actionability property, teams can quickly distinguish between events requiring action and those shared for awareness. The persona property streamlines event routing and visibility to specific teams like security and billing, ensuring critical information reaches appropriate stakeholders. These structured properties streamline integration with existing operational tools, allowing teams to effectively identify and remediate affected resources while maintaining appropriate visibility across the organization. This enhancement is available across all AWS Commercial and AWS GovCloud (US) Regions. To learn more about implementing these new properties, see the AWS Health User Guide and the API and EventBridge schema documentation.

Today, AWS announces that AWS Support Center Console now support screen sharing for troubleshooting support cases. With this new feature, you can request a virtual meeting while in an active chat or call, join support calls with one click through a meeting bridge link. With the new virtual meetings, you will be able to share your screen during the meeting and maintain seamless access to case details for efficient troubleshooting. This enhancement simplifies your support experience by keeping all support interactions within the AWS Support Center console. To learn more visit the AWS Support page.

Today, AWS announces that AWS Support Center Console now support screen sharing for troubleshooting support cases. With this new feature, you can request a virtual meeting while in an active chat or call, join support calls with one click through a meeting bridge link. With the new virtual meetings, you will be able to share your screen during the meeting and maintain seamless access to case details for efficient troubleshooting. This enhancement simplifies your support experience by keeping all support interactions within the AWS Support Center console. To learn more visit the https://docs.aws.amazon.com/awssupport/latest/user/case-management.html.

Amazon EMR now gives you more time, at no additional cost, to migrate off older releases before they reach end of support. If you are actively migrating, your workloads on eligible releases keep receiving support while you move to a current release, with no opt-in and at no charge. To give you more time to plan and migrate, Amazon EMR provides critical security fixes for releases 5.36 and 6.6 through 6.15 on a best-effort basis through June 30, 2027, and extended Standard Support for 7.0 through 7.10 releases through August 31, 2027. To receive an extension, contact AWS Support with your migration plan and any help you need with the upgrade. This applies to all deployment models of Amazon EMR (EMR on EC2, EMR on EKS, and EMR Serverless), in all AWS Regions where Amazon EMR is available. For the full list of releases and their support dates, see the Amazon EMR standard support policy. To get the extended support, contact AWS Support with your migration plan, or use the Apache Spark Upgrade Agent to move your applications to a current release.

Amazon EMR now gives you more time, at no additional cost, to migrate off older releases before they reach end of support. If you are actively migrating, your workloads on eligible releases keep receiving support while you move to a current release, with no opt-in and at no charge. To give you more time to plan and migrate, Amazon EMR provides critical security fixes for releases 5.36 and 6.6 through 6.15 on a best-effort basis through June 30, 2027, and extended Standard Support for 7.0 through 7.10 releases through August 31, 2027. To receive an extension, contact AWS Support with your migration plan and any help you need with the upgrade. This applies to all deployment models of Amazon EMR (EMR on EC2, EMR on EKS, and EMR Serverless), in all AWS Regions where Amazon EMR is available. For the full list of releases and their support dates, see the https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-standard-support.html. To get the extended support, contact AWS Support with your migration plan, or use the https://docs.aws.amazon.com/emr/latest/ReleaseGuide/spark-upgrades.html to move your applications to a current release.

📣 Service Update: AWS Billing Console We are investigating issues with Cost Explorer reflecting inaccurate estimated billing data. 📊 Track status: https://t.co/6qSnkuEzc4 #AWS #AWSSupport

They said they’re “here to help.” They meant help me cry more.

はじめに年月日にAWSSupportの事例Webinarnbspを実施しましたAWSサポ

Troubleshoot why an Amazon ECS task in an Amazon ECS cluster failed to start.