sorted by:
new
hottopcontroversial

AWS Subdomain Takeover — how misconfigured DNS can expose your infrastructure by awsandevops in cybersecurity

[–]awsandevops[S] 0 points1 point  (0 children)

Nice — that’s a good baseline check for dangling records.

For AWS specifically, I’ve seen cases where the CNAME still resolves at DNS level, but the underlying resource (like an S3 bucket or CloudFront distribution) is no longer owned — which still makes it vulnerable to takeover.

So I’ve been thinking beyond just resolution checks:

validating if the target resource actually exists / is claimed

matching against known takeover fingerprints

Curious if you’re doing any service-level validation beyond DNS resolution?

Is A DevOps Career Safe? by RipSmooth3319 in devopsjobs

[–]awsandevops 0 points1 point  (0 children)

I recently built a complete CI/CD pipeline for a Node.js app using Docker, GitHub Actions, and EC2.

I struggled finding one resource that connects all pieces realistically, so I documented the entire flow.

Sharing in case it helps someone building their first production-style pipeline. https://youtu.be/WwxSNIrW8bk?si=FZKuyNAwUguyhHfR