Okay. Hello, cloud gurus,
Scott Pletcher here with another week's worth of AWS news goodness.
IOT device defender gets smarter,
living the container life on AWS just got a little bit larger and S3 has a
nifty new trick plus something that has caused me a
measurable disappoint.
Is now fixed, right here on AWS This week.
There are 31 billion IOT devices coexisting with us here on
earth and another 127 being added every second.
As the Stuxnet and Mirai viruses demonstrated our IOT devices can quickly and
unknowingly become weaponized for nefarious activities.
The responsibility is therefore on us to take the appropriate measures to best
secure our devices.
IOT device defender is a tool AWS began offering in 2018 to keep
tabs on our IOT devices by periodically scanning them for security
issues. Now, recently,
AWS has added some machine learning into the mix with the general availability
of ML detect.
ML detect can identify anomalies in the behavior of your IOT
devices and proactively trigger alerts. For example,
if one of your devices is suddenly listening on a bunch of New ports ML Detect
can recognize that situation as out of the ordinary and trigger an
alarm.
This functionality can be very valuable in reacting and responding to threats,
especially if you're responsible for thousands of devices.
Much like a fine wine,
Our longtime friend S3 just keeps improving with age.
Recently AWS announced that it's now possible to create our own custom Lambda
functions to preprocess S3 data Before it's served up via the normal
get requests.
This enables some pretty nifty tricks that previously would have required some
intermediate layer like a custom API or middleware.
One example is using this functionality to redact sensitive data
Before letting the requester download the object.
We could create a bit of custom code use the PII detection feature in AWS
comprehend and identify potentially sensitive data.
Then just replace that data with nonsensitive placeholder values.
From the client standpoint,
this would simply look like a normal S3 API get request.
And that's pretty cool I think. Yes, my friends,
we are solidly in the age of the container and cloud providers have been working
feverishly to build all sorts of tooling and integration to help us with our
containers. AWS has elastic container service, elastic Kubernetes service,
fargate, proton, app2container, copilot,
and a few other container related features that I'm sure I'm leaving out.
Through a special partnership with red hat,
AWS began previewing red hat OpenShift service in November last year
as a managed service. And now that service is generally available.
Red hat created a new pay as you go license that's managed and billed right
through your AWS invoice.
So no need for additional contracts or vendor agreements.
There's no upfront investment and customers pay for only the containers and
nodes that are used. You know what really grinds my gears.
It's when a new AWS service with the capacity to create hundreds of entries has
no way to select multiple entries for deletion.
And that was exactly the case with AWS backup recovery points until recently
when AWS proudly announced that AWS backup now supports bulk deletion.
We no longer have to delete each and every recovery point one by one by
one by one by one. Hey, AWS, this is a crazy idea,
but just hear me out. Next time,
When you're creating a service that has the potential to generate hundreds of
entries,
maybe multiple selection should be one of those things that qualifies as part of
the minimum releasable product. Just saying.
And that my friends is all the AWS news that's fit to print this week.
If you're so inclined, like, and subscribe.
Also head on over to our brand spanking new ACG community hub on
discord - there you can interact with our training architects exam prep with
other students and learn about new content drops.
We'll share the link down below. Stay safe,
take care of one another and keep being awesome Cloud Gurus.
[Inaudible].