How should I approach a Amazon Web Services upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
ReadMeFeed / Community knowledge
EC2, Lambda, EKS, S3 and resilient AWS architectures.
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
Every Terraform guide on the web provides a partial solution that is almost always not the real picture. I get that not everyone has the same infrastructure needs, but what worries me is that the common scenario, including: Multiple environments (e.g. dev , stage ) Remote backend (e.g. AWS S3) Some basic resources (e.g. S3 buckets or EC2 instances) isn't pre
Just today, whenever I run terraform apply , I see an error something like this: Can't configure a value for "lifecycle_rule": its value will be decided automatically based on the result of applying this configuration. It was working yesterday. Following is the command I run: terraform init && terraform apply Following is the list of initialized prov
I opened a free tier instance for some practice. I tried to terminate it, as I've done many times successfully. But upon selecting Terminate instance from the dropdown; I got the following error: Failed to terminate the instance <instance id> The instance '<instance id>' may not be terminated. Modify its 'disableApiTermination' instance attribute
I am trying to create an external table in Amazon Athena. My query is the following: CREATE EXTERNAL TABLE priceTable ( WeekDay STRING, MonthDay INT, price00 FLOAT, price01 FLOAT, price02 FLOAT, price03 FLOAT, price04 FLOAT, price05 FLOAT, price06 FLOAT, price07 FLOAT, price08 FLOAT, price09 FLOAT, price10 FLOAT, price11 FLOAT, price12 FLOAT, price13 FLOAT,
I have a scenario in which I want to have access to resources within one account from another one in AWS (cross-account access) in code. And I want to implement this access using NodeJs, implemented as lambda function and also as a long-running code on EC2. Reading how to do this online, I know I need temporary credentials generated by aws.STS , like this: c
Slightly tearing my hair out with this one... I am trying to run a Docker image on Fargate in a VPC in a Public subnet. When I run this as a Task I get: ResourceInitializationError: unable to pull secrets or registry auth: pull command failed: : signal: killed If I run the Task in a Private subnet, through a NAT, it works. It also works if I run it in a Publ
When multiple objects are uploaded to a bucket in rapid succession, the application expects the corresponding Lambda functions to process events in the same order as the uploads. The goal is to determine whether S3 event notifications preserve a global order across all object keys, or if ordering is only guaranteed per key, and how Lambda concurrency limits
I am trying to use AWS Cloudwatch Logs insights in order to search in some quite old logs of our lambda functions. I am reading this guide on AWS docs , but nowhere is documented how you can filter by timestamp. I have tried the below: fields @timestamp, @message | filter @timestamp > '2019-12-04T18:09:10.000+01:00' | limit 200 | sort @timestamp desc but
answered · 07 Nov 2025, 08:44 UTC
answered · 24 Oct 2025, 04:40 UTC
commented · 10 Sept 2025, 15:08 UTC
answered · 08 Sept 2025, 16:04 UTC