Background : AWS Lambda
AWS released a long requested feature for the ability to run a packaged code (container image) using the compute service lambda. This feature was available in azure functions for sometime but was missing on AWS. The feature enables the development community to code + package + deploy the container image into AWS ECR and run them using AWS Lambda. It also eliminates some of the earlier lambda limitations on size of packaged code.
AWS Fargate is also a similar compute service that supports running container image. …
Consider an application that has its code stored in a Git repository in GitLab. Developers push code changes every day, multiple times a day. For every push to the repository, you can create a set of scripts to build and test your application automatically, decreasing the chance of introducing errors to your app.
This practice is known as Continuous Integration; for every change submitted to an application — even to development branches — it’s built and tested automatically and continuously, ensuring the introduced changes pass all tests, guidelines, and code compliance standards you established for your app.
GitLab itself is…
AWS Policy allows to restrict the permissions to an S3 resource(s) using pattern. The most often requirement is to restrict a specific users to list hierarchy of folder(s) and read/write/delete actions to certain folders.
Since, S3 is not a conventional file system, every object path is a referenced as S3 prefix. To restrict the users permissions, the AWS policy must include conditions to match the prefix or resource pattern of the objects.
In the above policy, the user attached to policy will have access to list the bucket objects matching the pattern dev/*. …
Decisive and multi-faceted IT professional with 12 years of experience delivering data management projects with 5+ years experience in cloud and big data tech