This is related to the Lab: S3 Kafka connect task 5/9 in the Event Streaming with Kafka course

DevOps
#1

When updating the config/kraft/server.properties file in task 5/9 Setting up Apache Kafka on Amazon Linux EC2 instance in the Lab: S3 Kafka connect, the instructions mentions to replace the EC2-PRIVATE-IP in the advertised.listeners with the private IP address of your EC2 instance.
While using the Private IP address works, (as I have not faced any issues when using private IP address in the lab), I noticed that the instructor copies the Public IP address and not the Private IP address in his Demo’s.

Screenshot 2025-09-23 at 12.51.13
Screenshot 2025-09-23 at 12.51.131504×292 116 KB

Thanks,
@ewiklund

#2

While I think the “53.x.x.x” IP address he uses is indeed a public IP, I don’t think there’s any problem with having you substitute the private IP of the EC2 instances, since, as you correctly point out, it works for purposes of the lab.

#3

Thanks for clarifying it Rob. That’s exactly what I thought.