logo
Menu

Build On Answered | All About Resilient Architecture | S01 EP07

Join us for Build On Answered, the Twitch show where expert hosts review top viewed questions from the AWS Stack Overflow Collective live on air!

Julie Gunderson
Julie Gunderson
Amazon Employee
Cobus Bernard
Cobus Bernard
Amazon Employee
Seth Eliot
Seth Eliot
Amazon Employee
Published Jun 21, 2022

Streaming session with Rohini and Cobus with a shared browser tab showing a Stack Overflow question

Join us for Episode 7 of Build On Live: Answered, the Twitch show where expert hosts review top viewed questions from the AWS Stack Overflow Collective live on air!

In this episode we will be focusing on resilient architectures. We have selected some of the top viewed questions in the AWS Collective and built code and demos around the best answers to those questions!

  1. Cannot ping AWS EC2 instance
  2. Does AWS S3 cross-region replication use same URL for multiple regions?
  3. What is the difference between Amazon ECS and Amazon EC2?

Why did Reachability Analyzer still claim the security group was the problem, even after Seth added in inbound rule for ICMP?

  • This was definitely a case of PEBCAK. Remember when setting up the path to be analyzed, it asks for a protocol? Seth, specified TCP (from the choices TCP or UDP). Well, ICMP (the new rule Seth added), is not TCP, so analyzer correctly determined there was no TCP path to the instance.

Can we just re-run an analysis on an already defined path in Reachability Analyzer?

Analyze path button in Reachability Analyzer

Let us know HERE

Users who join the AWS Stack Overflow Collective will find curated, centralized community resources to help them more easily discover the most up-to-date answers including those recommended or written by AWS subject matter experts, technical articles such as how-to guides, and Bulletins for upcoming events and releases.

Members can keep tabs on where they rank on the leaderboard and be promoted to Recognized Member status based on their contributions. By bringing knowledge and users together, the AWS Collective will help the community continue to learn, share, and grow.