TechCuriosity

In the world of cloud computing, efficiency and scalability are paramount. Amazon Simple Storage Service (S3) is one of the most widely used cloud storage solutions, offering unparalleled durability, availability, and scalability. However, managing large-scale operations on S3 objects, such as copying or tagging thousands or even millions of objects, can be challenging and time-consuming. This is where S3 Batch Operations come into play—a powerful feature provided by AWS to automate and streamline such tasks. In this article, we'll delve into S3 Batch Operations, understand their significance, and walk through the process of creating one step-by-step. Understanding S3 Batch Operations S3 Batch Operations enable you to perform large-scale batch operations on S3 objects, such as copying objects between buckets, tagging objects, replacing object tags, or running Lambda functions on objects. These operations are designed to be highly scalable, allowing you to process thousands, million...

In the digital age, ensuring the security of data is very important. As businesses increasingly migrate their operations to the cloud, they face the challenge of safeguarding sensitive information from unauthorized access. Amazon Web Services (AWS) offers a robust solution to this challenge through its Key Management Service (KMS) and the concept of KMS keys. In this article, we'll explore KMS keys in simple terms, understand their significance, delve into various use cases, and discuss best practices for working with them. What are KMS Keys? Let's start with the basics. Imagine you have a treasure chest filled with valuable items. You wouldn't leave it unlocked for anyone to access, right? Similarly, in the digital world, sensitive data needs to be protected using encryption — a process of converting information into a code to prevent unauthorized access . KMS keys are like the keys to that treasure chest, but for your digital data. In AWS, KMS keys are cryptographic keys ...

AWS Lambda is a serverless computing service provided by Amazon Web Services (AWS) that allows you to run code without provisioning or managing servers. It lets you execute code in response to events such as changes in data, HTTP requests, or scheduled events, without the need to manage infrastructure. So, we can invoke lambda directly from Amazon Event Bridge rule or from SQS. Here are some important points to keep in mind while working with AWS Lambda: 1. Serverless Architecture : With AWS Lambda, you don't need to provision or manage servers. You upload your code and AWS takes care of scaling and managing the infrastructure needed to run it. But keep one thing in mind, it is possible to upload the code directly to Lambda in AWS in zip format, but use this approach only when you want to develop the Lambda locally.  For production ready applications, it is always advisable to deploy Lambda using CICD pipelines. It means build the Lambda code and publish to ECR repository and then...

In the last 2 posts, we looked at what is Docker and why it is needed. In this post, we will try to install docker and see how the docker client works. To install Docker, download it from the below link as per your OS and install using the installer command  Docker Download Link Once installation is done, execute the “ docker ” command on your terminal or command prompt to see if it got installed correctly or not. If it got installed correctly then you will see the following output on the terminal: As we are going to use our terminal to write docker commands, we need to log in to Docker Hub from our terminal. Use the below command to log in to Docker Hub from the terminal:  “ docker login ”  It will then ask you about your username and password, enter those to log in.  You should be able to see Login succeeded message on the terminal. To check the docker version run “ docker version ” command    Execute the below command to understand how docker actually wo...