Let’s talk
INSIGHTS / KNOWLEDGE, SHARED

Ideas for
your next move.

Practical thinking for teams building software, securing systems and operating modern infrastructure. Explore our engineering field notes.

500 insights · Page 20 of 42

ECR Lifecycle Policies: Preview the Release Impact — conceptual 3D-style vector showing Release inventory, Rule priority, Preview result, Image digest, Manifest list, Rollback release.ENGINEERING JOURNAL ↗
AWS Operations

ECR Lifecycle Policies: Preview the Release Impact

Review ECR lifecycle rules against deployed digests, rollback requirements, tag patterns, and multi-architecture manifests before applying retention.

Read field note ↗
Cognito M2M Tokens: Connect Custom Scopes to API Actions — conceptual 3D-style vector showing Backend client, Client secret, Token endpoint, Custom scopes, API verifier, Business action.ENGINEERING JOURNAL ↗
AWS Operations

Cognito M2M Tokens: Connect Custom Scopes to API Actions

Set up Cognito client-credentials authorization with a confidential client, explicit resource-server scopes, secure token handling, and API enforcement tests.

Read field note ↗
Cognito Callback Errors: Trace the Exact Redirect URI — conceptual 3D-style vector showing Browser origin, Application proxy, Authorization URL, App-client allowlist, Callback handler, Token exchange.ENGINEERING JOURNAL ↗
AWS Operations

Cognito Callback Errors: Trace the Exact Redirect URI

Resolve Cognito callback failures by comparing app-client registration, authorization and token requests, proxy-derived URLs, and a complete test sign-in.

Read field note ↗
EventBridge Scheduler: Make Time-Zone Behavior Explicit — conceptual 3D-style vector showing Business calendar, IANA time zone, Cron or rate, Flexible window, Target execution, Completion ledger.ENGINEERING JOURNAL ↗
AWS Operations

EventBridge Scheduler: Make Time-Zone Behavior Explicit

Set EventBridge Scheduler recurrence with an explicit time zone, daylight-saving policy, flexible window, and evidence that scheduled work completed.

Read field note ↗
SQS FIFO: Find the Message Group That Limits Progress — conceptual 3D-style vector showing Producer events, Group key, Group A, Group B, Worker A, Worker B, Effect ledger.ENGINEERING JOURNAL ↗
AWS Operations

SQS FIFO: Find the Message Group That Limits Progress

Diagnose FIFO queue backlog through message-group distribution, in-flight work, deduplication identifiers, and the business ordering boundary.

Read field note ↗
SQS Visibility: Match the Lease to the Work — conceptual 3D-style vector showing Visible message, Worker receipt, Visibility clock, Business commit, Delete request, Retry worker.ENGINEERING JOURNAL ↗
AWS Operations

SQS Visibility: Match the Lease to the Work

Reduce avoidable SQS duplicate work by measuring processing time, extending visibility deliberately, and verifying deletion with the current receipt handle.

Read field note ↗
SNS Filters: Match the Scope to the Published Message — conceptual 3D-style vector showing Publisher, SNS topic, Attribute scope, Body scope, Subscription filter, Subscriber.ENGINEERING JOURNAL ↗
AWS Operations

SNS Filters: Match the Scope to the Published Message

Diagnose SNS messages missing from a subscription by comparing filter scope, attribute types, JSON body shape, and controlled matching and nonmatching events.

Read field note ↗
Step Functions Retry and Catch: Preserve Business Effects — conceptual 3D-style vector showing Task input, Task attempt, Retry delay, Catch route, Effect ledger, Operator review.ENGINEERING JOURNAL ↗
AWS Operations

Step Functions Retry and Catch: Preserve Business Effects

Design Step Functions error handling around named failures, bounded retries, retained input, and verification of business effects after ambiguous timeouts.

Read field note ↗
Lambda Python Layers: Match Runtime and Architecture — conceptual 3D-style vector showing Dependency lock, Linux builder, Python tree, Layer version, Runtime and CPU, Import test.ENGINEERING JOURNAL ↗
AWS Operations

Lambda Python Layers: Match Runtime and Architecture

Diagnose Lambda layer import failures by checking archive paths, Python versions, Linux compatibility, native architecture, and the exact published layer version.

Read field note ↗
Lambda Async Destinations: Verify the Failure Record — conceptual 3D-style vector showing Async caller, Lambda queue, Function attempts, Outcome record, Destination, Recovery owner.ENGINEERING JOURNAL ↗
AWS Operations

Lambda Async Destinations: Verify the Failure Record

Trace Lambda asynchronous failures from retry settings to destination permissions, record delivery, and an idempotent business recovery procedure.

Read field note ↗
Lambda Concurrency: Separate Capacity from Warm Environments — conceptual 3D-style vector showing Requests, Function ceiling, Qualified alias, Warm environments, On-demand pool, Downstream limit.ENGINEERING JOURNAL ↗
AWS Operations

Lambda Concurrency: Separate Capacity from Warm Environments

Choose Lambda reserved and provisioned concurrency using measured demand, downstream limits, alias routing, and evidence of throttling or provisioned spillover.

Read field note ↗
DynamoDB Streams: Recover a Lambda Batch Deliberately — conceptual 3D-style vector showing Table changes, Stream shard, Lambda batch, Success checkpoint, Failed sequence, Recovery destination.ENGINEERING JOURNAL ↗
AWS Operations

DynamoDB Streams: Recover a Lambda Batch Deliberately

Investigate DynamoDB stream backlog with iterator age, record-level failures, partial batch configuration, and a durable recovery plan for discarded work.

Read field note ↗