We would like to use third party cookies and scripts to improve the
functionality of this website.
Approve
Deny
More info
Navigating the Gray with the Known and Unknown framework, a structured approach to achieve continuous clarity of purpose...
By incorporating testing practices into the early stages of software development, teams can not only catch defects early but also shape the architecture, behavior, and interactions of the system...
Self-testing code is “the practice of writing comprehensive automated tests in conjunction with the functional software“. At the heart of self-testing code lies a profound benefit: the confidence to implement changes...
My goto serverless stack for super speed to production web applications, and RESTful APis, is CloudFront, S3, API Gateway, and Lambda. CloudFront provides the front door to the application, serving static content from S3 and providing paths to API Gateway APIs - no CORS here.
Minimise the risk of deployment by using canary deployments to slowly shift traffic to the new version, shifting traffic back to the previous version if error thresholds are passed.
Control AWS DynamoDB encryption by using a Customer managed customer master key (CMK) to encrypt data at rest using server side encryption (SSE).
Using multple CloudFormation stacks can help you better organise your resources
Here is how to use an OpenAPI specification to define an AWS API Gateway API
Take advantage of the automatic versioning and aliasing of your Lambdas to instantly shift traffic to your new API deployments. Rollback by repointing the problematic Lambda’s alias to the previous version.
Use an API Gateway Resource Policy to allow access to your APIs only from certain IPs. This is a handy approach for locking down your non-production APIs so that they are not publicly accessible.
