u/Wide_Impact_9392

I am running Prometheus on an EC2 instance scraping node exporter from other EC2 servers using static private IPs in prometheus.yml.

Trying to understand what is considered production practice:

• Do teams manually update prometheus.yml or use GitOps / IaC to generate it?
• Is EC2 service discovery commonly used instead of static IPs?
• In AWS setups, do people rely on tags (like monitoring=true) for target discovery, or is that just for automation tools?
• Is node exporter always kept on private subnets with SG restricted only to Prometheus?
• Do production setups ever expose node exporter outside VPC (with protections), or always internal only?
• At what scale does static config become a problem, and what is usually the first upgrade path?

Current setup works, but not sure if this is a “lab pattern” or something actually acceptable in production. Here is the screenshot of the config file that I used. I removed the content marked in yellow because that wasn't working. Seeking your suggestions.

https://preview.redd.it/fwcd4ezpt5ah1.png?width=1111&format=png&auto=webp&s=17b25ad5676a7a32a73956c429184d435dd95680

https://preview.redd.it/mbfhga9xs5ah1.jpg?width=1866&format=pjpg&auto=webp&s=690e79d3d89e3dc3f084ab43b3c55513f5d15619

Hi everyone,
I am new to AI and want to start using it in my DevOps learning and projects. There are so many tools and resources available that I am not sure where to start.
Could you recommend any websites, courses, youtube channels etc that genuinely helped you understand AI in the context of Devops, automation, kubernetes, cloud or infrastructure?
I am interested in practical use cases rather than purely theoretical content.

Hi everyone,
I am new to Kubernetes and understand how YAML files work for Deployments, Services and other resources.
I am trying to understand how Helm fits into this process. I know that Helm creates charts, but I am confused about whether I need to modify all of my existing YAML files and convert them into Helm templates.
For example, if I already have deployment.yaml, service.yaml and ingress.yaml files, do all of these files need to be moved into the templates directory and updated with Helm variables such as {{ .Values.image.tag }}?
I do not fully understand the workflow of attaching existing Kubernetes YAML files to a Helm chart and how teams typically do this in real projects and production environments.
Could someone explain the process in simple terms or provide an example of converting an existing Kubernetes application into a Helm chart?
Thank you!

I am currently looking for a paid internship or junior opportunity in DevOps, Cloud Engineering, or Site Reliability Engineering roles based in Perth, Australia, or remote.
I come from an IT infrastructure background with:
- 9 years experience in Oracle DBA and IT support environments
- AWS Solutions Architect – Associate Certified
- Microsoft Azure Fundamentals Certified
- AWS Community Builder
- Strong Linux and production support experience
- Currently building skills in Docker, Kubernetes, and CI/CD pipelines
I also had a planned career break, during which I focused on upskilling in cloud computing and Devops skills and preparing for a transition into DevOps engineering.
I am open to:
- Paid internships programs
- Junior DevOps / Cloud Engineer roles
- Cloud support or platform support roles with growth into DevOps

Thank you!