![]() For those new to AWS S3, the term S3 means “ Simple Storage Service”, which is object storage that, according to Amazon, “aims to provide scalability, high availability, and low latency at commodity costs”. Leveraging other AWS services to scale out incident responseįor this post, we’re only going to cover setting up a S3 bucket, creating a new user, creating a S3 bucket policy to limit access control for our user, and cover some common ways to upload data to your S3 bucket.Ease of automation (SQS/Lambda for example).Granular control over data storage, lifecycle and versioning.I’ve outlined some of the main reasons I use AWS below: There are many options for storage mediums, but by storing data in the Amazon AWS ecosystem your team can leverage many of the AWS services to store, process, and collaborate on incident response activities, enabling your team to scale response efforts. One significant challenge I’ve experienced performing incident response is working with the large amounts of data needed by responders storage mechanisms need to be accessible, fast, secure, and allow integrations with post-processing tools. When an incident occurs, time is everything. Leveraging AWS for Incident Response: Part 1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |