Okay. Hello, cloud guru, Scott Pletcher here with another collection of AWS news goodness. Cross account SQS Lambda triggers are now a thing. Cloud control API is released into the world and step functions Step up big time. All right, here on AWS this week Recently, AWS announced that it is now possible for customers to trigger Lambda functions via SQS queues.

In other AWS accounts previously, we could only trigger Lambda functions from SQS queues in the same account, or you had to perform some elaborate shenanigans to get queue messages from account A to account B. This cross account access is a welcome feature. In that most significant organizations on AWS, have many accounts, maybe hundreds of accounts, and with a message queue design pattern being ever so useful for all sorts of integrations, this new feature should open the door for more efficient and seamless cross account information flow. Now, of course, you'll still need to grant cross account permissions for the Lambda function to reach the foreign queue. But once that's done, all you need to do is provide the ARN for the queue and the remote account.

Well, the AWS cloud control API has now made it to general availability. The cloud control API has a common set of APIs that allow us to programmatically manage AWS services in a common way. I know what you're thinking. We already have the AWS SDK for all this. Why on earth do we need the cloud control API? Well you'd be correct in saying that this is a bit redundant, but as all the AWS services grew up consistency and their respective slice of the SDK never seemed a priority. As a result, different services have different syntax for the basic crud operations, those being create, read, update, delete, and sometimes list.

The cloud control API aims to provide a more efficient developer experience through a common set of verbs, input parameters, output, and error types. Additionally, the cloud control API also includes support for some third-party products and services through the same unified syntax and AWS has committed that newly released services will have cloud control API support right out of the gate. AWS step function developers now have access to the AWS SDK expanding the number of supported services from 17 to more than 200 AWS services. Previously, if you wanted to do something with an unsupported service, you had to build a custom Lambda function and incorporate that into your workflow. Now you have access to virtually every service supported by the SDK, right in the workflow studio or via the cloud development kit or Amazon state language, if you like that sort of thing.

You can even access niche services like ground station, braket and mechanical Turk, should you have a need for that. This does indeed create some very interesting low code possibilities. Lastly, we now have the option to run Lambda functions on AWS as ARM-based graviton2 processors, as opposed to the traditional x86 processors. If your code uses a runtime that supports an ARM-based processor, you might just be able to save up to 34% on your compute costs. Speaking of big savings, did you know that you can access a monthly rotating collection of a cloud guru courses completely free. For example, in the month of October,

your free tier account gets you access to a collection of security related courses, including AWS IAM, cloud security fundamentals, Kubernetes security, and an introduction to Azure security. If you're curious about life in other clouds. Last month, you could have binged on Terraform courses for free. It's easy to sign up and costs you absolutely nothing. We'll include a link down below.

That my friends is all the AWS news that I have for you this week. Stay safe, take care of one another and keep being awesome cloud gurus.