Paul Marcelin sqlxpert

Jump to: Pinned repos • Contribution graph • All repos ↗ • LinkedIn🔒↗ • Blog ↗

Technical Competencies

Unfold ( ▸ ) for short, specific examples.

Infrastructure	Programming	Security
Terraform Secure private network: Editable configuration map feeds `for_each` sets and maps Strict reciprocal security group egress and ingress rules permit traffic only between identified hosts, not within entire private IP address blocks Data-driven, not hard-coded, validation and error Intuitive defaults with minimal code, for an AWS API data type that can't be reduced to a Terraform HCL type specification New S3 object version triggers a Terraform change (most users forget `versionID` )	Python Object-oriented programming (OOP): Harmonize AWS API inconsistencies — method names; input argument names, types (ID versus ARN), and cardinality; output object keys Accommodate disparate AWS resource types Define capabilities Support extensibility OpenAPI provides a clear API specification and automatic input validation with minimal, focused code Clear and consistent error-handling functions Typed, structured JSON log entries, machine-readable and searchable by humans Self-documenting regular expression	IAM Enforce KMS encryption in S3: One central resource control policy (RCP) covers buckets in many accounts Tags and self-service documentation reduce developers' dependence on the infrastructure team Templated test buckets support thorough, realistic, automated tests Keywords communicate properties of test buckets without duplicate code Enforce S3 storage class: One central resource control policy (RCP) covers buckets in many accounts History of S3, IAM, and AWS Organizations feature releases provides an architectural decision record Safe permissions delegation trick ( `Detailed semantics` , Item 4) Restrict Lambda function permissions using attribute-based access control, then protect ABAC tags with a service control policy (SCP) Restrict instead of rewriting an AWS-managed policy, for self-documenting, maintainable least-privilege IAM policy variables avoid code duplication: Explanation with examples, in response to a user request CloudFormation parameter Insertion into IAM policy
CloudFormation Same template for individual stacks or a centrally-managed, multi-account, multi-region StackSet: "Partial ARN" parameters are not region-specific Conditions replace 3 separate templates Validation rules and a condition accommodate different kinds of inputs and different cardinalities Least-privilege CloudFormation service role protects each workload and reduces "confused deputy" risk Placeholder parameters help new (AWS Console) users to name stacks and find documentation	Reliability Diagnosing and fixing race conditions (timing bugs): Comparison with existing solutions Visual Article: "5 AWS Services, 5 Different Approaches to Idempotence" Rejecting legacy AWS SDK retry mode, years early AWS SDK pagination Loose coupling — queue, retries, timeout, dead-letter queue
Containers/Docker Simple container definition yields a small and secure image Elastic Container Service (ECS) and load balancing support scalable orchestration

Navigation Menu

Paul Marcelin sqlxpert

Achievements

Achievements

Highlights

Block or report sqlxpert

Technical Competencies

Pinned Loading

Uh oh!