With re:Invent less than a week out, I figured it was a good time to see how last year’s re:Invent held up. After all, every year we get wowed with all the new services and features that are announced, but how long does it take until we can use those? In fact, it’s a year later now, but can we actually use everything that was promised?
The questions I asked were as follows:
- How many announcements were GA (Generally Available), in preview, or pre-announcements of upcoming services?
- How many of the non-GA announcements are available right now?
- How long did it take for those to become available?
And I repeated those questions specifically for the Sydney region as well, seeing as that is the region I deal with the most on a day-to-day basis.
In order to find answers to these questions, I went through the announcements and grouped these by type (GA, preview, pre-announcement). I then looked at when they became GA and/or became available in Sydney.
In total I compared 82 announcements. I didn’t include program announcements in this list, mostly because they aren’t as interesting to most people and because it’s harder to find out their status. For example, this means that while I included the Well-Architected Tool, I excluded the announcement of the Well-Architected Partner Program.
What kind of announcements were there?
First, let’s have a look at the announcements. Of the 82 announcements, 54 were announced as being immediately available, 24 had a preview, and only 4 were pre-announcements. This means that you would not be able to immediately use a full third of the announcements. There is an asterisk about that though, as several of the previews were public previews, which as the name implies means that everyone could use them. They were just not recommended for production use.
But then the follow up question, how did Sydney fare in this regard? Unfortunately, of the 54 GA announcements, 12 (over 20%) were not immediately available in Sydney. Which means that for us in Australia, 40 announcements were not available from the start.
While we’re looking at the type of announcements, we can differentiate this in another way as well. After all, some announcements improve existing services, while others are completely new. The breakdown for this came down to 31 new services, 45 features, and 6 open source projects.
How many are now Generally Available?
Of the 82 announcements, 4 services are not yet available to most of us. These 4 are:
- AWS Outposts
- IoT SiteWise
- AWS Inferentia
- Amazon Timestream
Another 14 services are available, but not in the Sydney region. This includes services that are unlikely to ever go beyond a single region, such as DeepRacer, and features that went GA for services that are not available in Sydney. But it still means that, one year later, over 20% of the announcements aren’t available in Australia. I wish I could say I was surprised at that, but let’s just say there is a reason we have a section titled “Finally in Sydney” at the local User Group meetup.
Leaving my usual Australia focus aside however, we can have a more positive way of looking at it. After all, of the 28 announcements that were not immediately available, 24 are now indeed available to everyone. Even if that might not be the case in your region of choice. In fact, 95% of all announcements are now available.
How long does it take to become GA?
Unsurprisingly, the answer to this question is “it depends”. On average, it took services almost 177 days to become available. Considering that is almost exactly half a year, it’s pretty clear that these releases were spread out throughout the year.
In fact, the quickest GA announcement happened a mere 11 days after re:Invent when the EC2 p3dn.24xlarge instance type became available. The longest wait1 was for Amazon RDS on VMWare, which took 322 days to became reality.
If we then look at Sydney we can see very similar numbers. On average it took 182 days for services to become available. This number hides the truth a bit though, as it makes it seem that Sydney was on average only 5 days behind North Virginia. Here you need to remember that Sydney had more services that weren’t released yet, as on average Sydney was actually about 150 days behind North Virginia for services that weren’t available there from day one.
For Sydney the first and last service to become available are different as well. The first one was AWS Transit Gateway, which followed its announcement at re:Invent after only 17 days2, while the most recent service to become available happened just last week when we got Amazon Quantum Ledger Database (QLDB). Which to be fair, was a mere 70 days3 after it became available at all.
Taking a closer look at the numbers however shows that while the EC2 p3dn.24xlarge instance type coming within 11 days was great, it was one of only two releases within the first 100 days. The other being the EFS Infrequent Storage Class after 80 days. That is a bit disappointing, and the situation for Sydney was exactly the same. After the Transit Gateway, the only other within 100 days was that same EFS Infrequent Storage Class. I think it’s fair to say based on these numbers that there was a bit of a slow start after the initial rush from re:Invent, but that is to be expected as it takes time to fix assumptions during the preview periods. And there was the holiday period in between as well.
What does this mean for this year?
Let’s be clear, how last year’s announcements performed doesn’t necessarily mean anything about what will happen this year. But it’s likely that things will work out similarly. Which means we can expect a number of announcements we can’t use immediately, no matter how disappointing that is. In addition, you shouldn’t expect anything to come shortly after re:Invent and in fact it can take a very long time before the service you really want becomes available. Especially if your region is one that doesn’t get a lot of love.
On the other hand, the majority of announcements is available immediately and, based on what we’ve seen over the past several weeks4, it seems to me that there are likely a lot of interesting announcements waiting for us. So, I’m quite positive about the new toys we’ll get to play with next week.
- Obviously not counting the services that didn’t get released at all. [return]
- Unfortunately, the Direct Connect integration took far longer to appear in Sydney. [return]
- Less than half the average time! [return]
- This time of year we get both the announcements that didn’t make the cut for re:Invent and those that need to be in place already for the announcement. [return]
Read more like this:
- Week 49, 2017 - re:Invent 2017; macOS root bug
- Week 48, 2017 - GitHub Team Discussions; pre-re:Invent roundup
- Midnight Madness Jet lag
- Keeping an Eye on your Serverless Containers
- Letting Go Of Your Instances
Or always get the latest by subscribing through RSS, Twitter, or email!