0:00

Hello and welcome to Last

0:02

Week in AWS. What glorious things

0:04

does AWS have for us? Well,

0:06

strap in. We're about to find

0:08

out. Amazon EBS now supports

0:11

additional resource-level permissions for

0:13

creating EBS volumes from

0:16

snapshots. Joy of Joys!

0:18

Because IAM permissions weren't

0:21

complicated enough. This is going

0:23

to get folks in trouble.

0:26

This episode is sponsored in

0:28

part by my day job. The

0:30

duck bill group. Do you have

0:32

a horrifying AWS bill? That can

0:34

mean a lot of things. Predicting

0:36

what it's going to be, determining

0:39

what it should be, negotiating your

0:41

next long-term contract with AWS, or

0:43

just figuring out why it increasingly

0:45

resembles a phone number, but nobody

0:47

seems to quite know why that

0:50

is. To learn more, visit duckbill

0:52

group.com. Remember, you can't duck the

0:54

duck bill bill. And my CEO

0:56

informs me that is absolutely not

0:58

our slogan. Amazon managed

1:00

service for Prometheus Collector

1:03

adds support for cross-account

1:05

ingestion. Three and a half years

1:07

later, AWS realized that everyone who

1:09

was going to build their own

1:11

cross-account ingestion out of spit,

1:13

popsicle sticks, lambda functions, and

1:15

AWS credits had already done

1:17

so. Therefore, it's time to

1:19

make it a click-the-button level

1:22

of simplicity. Amazon Redshift

1:24

concurrency scaling

1:27

is now available in one

1:29

additional region. It's Malaysia. There.

1:31

I saved you a click.

1:33

AWS headline writer, you should

1:35

be ashamed of this one.

1:37

Go back to Buzzfeed. Amazon

1:40

Q developer. Now troubleshoots

1:42

AWS console errors in

1:44

all AWS commercial regions.

1:46

Isn't this neat? We have an AI

1:49

assistant to tell you what to do

1:51

for the error types we know about?

1:53

Well, why not just make

1:55

the documentation better or solve

1:57

the errors in the first place?

2:00

listen here you little

2:02

shit. Amazon Q developer

2:04

again introduces a new

2:07

simplified setup experience for

2:09

pro-tier subscriptions. I tested this

2:11

out a couple of months ago

2:14

using the old flow and surprisingly

2:16

having to play puzzle quest. AWS

2:18

console edition was not the highlight

2:21

of my week. Hopefully this

2:23

version is better. AWS IAM

2:25

identity center now offers

2:28

improved error messages and

2:30

AWS cloud trail logging

2:33

for provisioning issues. We

2:35

made the error messages

2:37

actually informative. Now dear

2:39

listener, you decide, was

2:41

it AI or intern?

2:44

Place your bets. AWS

2:46

step functions now

2:48

supports 100,000 state

2:50

machines and activities

2:52

per AWS account. Now, state machines

2:55

only charge you per state transition.

2:57

And you know what that means?

2:59

That's right. It's a new free

3:01

database. This episode is sponsored in

3:04

part by my day job, the

3:06

Duck Bill Group. Do you have

3:08

a horrifying AWS bill? That can

3:10

mean a lot of things. Predicting

3:13

what it's going to be, determining

3:15

what it should be. Negotiating your

3:17

next long-term contract with AWS. or

3:19

just figuring out why it increasingly

3:22

resembles a phone number, but

3:24

nobody seems to quite know

3:26

why that is. To learn

3:28

more, visit duckbillgroup.com. Remember, you

3:30

can't duck the duckbill bill.

3:32

And my CEO informs me

3:34

that is absolutely not our

3:36

slogan. Cost optimization hub supports

3:38

more EC2 auto scaling

3:40

group recommendations. I'm always

3:42

intrigued by how elegantly

3:44

the corporate wording is

3:46

around releases like this,

3:48

because the truth of it distills

3:51

down to, if you're not using

3:53

it, turn that shit off. Announcing

3:55

the general availability of

3:58

AWS migration service serverless

4:00

support for files with

4:03

an S3 source and point.

4:05

Excuse me a second, I

4:07

just need to take another

4:09

victory lap around the folks

4:11

who've insisted to me for

4:13

years that S3 isn't a database.

4:15

AI-powered football match

4:18

analysis. SAP Sports One on

4:20

AWS. I can only

4:22

imagine what Lovecraftian horror of

4:24

a corp-dev deal led to

4:26

this monstrosity of an announcement,

4:28

but here's a hint. The

4:30

post starts with, and I

4:32

am not making this up,

4:34

by thanking 11 different people.

4:37

And finally introducing AWS cloud

4:39

formation stack refactoring and holy

4:41

crap I have wanted this

4:43

since cloud formation first came out.

4:46

It sounds ridiculous but until now

4:48

the approach has always been either

4:50

replace it or learn to live

4:53

with it or the next closest

4:55

thing to it via nested

4:57

stacks. This is amazing. And that's

4:59

what happened last week. in

5:02

AWS. I'm cloud economist Corey

5:04

Quinn. Please stick around and

5:06

or tell me what I got

5:08

wrong. Music