How to Automate CloudFront Cache Invalidation in Your CI/CD Pipeline

·1 views

When deploying websites hosted on Amazon S3 with CloudFront, users can see outdated content for up to 24 hours due to CloudFront's default caching behavior. Automating cache invalidation within a CI/CD pipeline eliminates this problem by triggering a cache clear immediately after each deployment. Tools such as GitHub Actions, AWS CodePipeline with Lambda, Jenkins, and even npm scripts can all invoke the AWS CLI command to create invalidations programmatically. Developers should note that while the first 1,000 invalidation paths per month are free, additional paths incur charges, making targeted or versioned-filename strategies more cost-effective. Using wildcards to invalidate all paths is the simplest approach, but modern best practices recommend versioned asset filenames combined with selective entry-point invalidation for optimal performance and cost control.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why Human Skills Still Matter in the Age of AI Automation

Developer Cesar Aguirre published a short opinion piece on DEV Community on July 6 arguing that tasks AI can complete in minutes should no longer be considered special skills. The article targets beginner and experienced developers navigating the growing influence of AI in software development. Aguirre suggests that professionals need to focus on capabilities that go beyond what AI tools can easily replicate. The piece is framed as practical advice for thriving amid the current AI hype in the tech industry.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How PostgreSQL Handles a Backend Process Crash and Why It Drops All Connections

When a PostgreSQL backend process crashes, the database engine does not isolate the failure to just that session. Because all backend processes share critical memory areas — including shared buffers, lock tables, and transaction status data — PostgreSQL cannot guarantee the integrity of those structures after a crash. As a safety measure, the postmaster immediately terminates all active connections and initiates automatic recovery before accepting new ones. A demonstration using Docker and pgbench showed that connected clients received warnings about the crash and were instructed to reconnect after recovery. This behavior is an intentional design feature of PostgreSQL, prioritizing data consistency over session continuity.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Postgres FOR UPDATE SKIP LOCKED solves concurrent resource allocation

A developer building StashMe, a digital cloakroom management system for venues, encountered a race condition where multiple simultaneous check-ins could assign the same coat hanger to different guests. The naive SQL approach of reading then writing allowed two transactions to claim the same row before either could lock it. Postgres's FOR UPDATE SKIP LOCKED clause, available since version 9.5, resolves this by having concurrent queries skip rows already locked by other transactions rather than waiting on them. This allows multiple check-ins to proceed in parallel, each claiming a distinct free hanger with no queuing or deadlocks. The same pattern underpins popular Postgres-based job queue libraries and can be applied broadly to any system distributing finite resources under concurrent load.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Learns ACME Protocol Basics After Debugging HTTPS Certificate Failures

A developer encountered repeated HTTPS certificate issuance failures while deploying an application using Caddy as a reverse proxy and Let's Encrypt for SSL certificates. Despite correct DNS records, open firewall ports, and proper Caddy configuration, certificates consistently failed to issue. The root cause turned out to be a networking problem that prevented Let's Encrypt from reaching the server during ACME domain validation — not a misconfiguration in Caddy or TLS itself. The ACME protocol requires Let's Encrypt to actively validate domain ownership by contacting the applicant's server, a detail the developer had initially overlooked. Reading ACME logs and following a structured checklist — verifying DNS, checking external port reachability, and confirming challenge responses — ultimately resolved the issue and highlighted that certificate failures often stem from underlying network problems.

0 comments Read more at DEV Community