Episode 113: All the great AWS re:Invent news

Published: Nov. 30, 2017, 11 p.m.

b'

There\\u2019s no clever title this week, just straight to the point of covering the highlights of AWS re:Invent this week. They got the kubernetes now! There\\u2019s a passel of releases as well. We also discuss some other news like Meg Whitman leaving HPE (on good standing), net neutrality, WeWork buying Meetup, and Arby\\u2019s. For reals!

\\n\\n

Pre-Roll SDT News

\\n\\n\\n\\n

Misc. news before re:Invent coverage

\\n\\n\\n\\n

AWS re:Invent

\\n\\n
    \\n
  • AWS Business Update\\n\\n
      \\n
    • Amazon Web Services has an $18 billion revenue run rate and the business is growing 42 percent year over year
    • \\n
  • \\n
  • New AWS Services (100+ new total)\\n\\n
      \\n
    • Loosely break into themes of Containers, Databases, AI/ML, and IOT
    • \\n
    • Amazon MQ - Apache ActiveMQ as a Service (lunches eaten?)
    • \\n
    • AppSync - GraphQL as a Service (lunches eaten?)
    • \\n
    • Aurora Serverless - burst database consumption
    • \\n
    • Comprehend - Natural Language Processing across 98 languages
    • \\n
    • DeepLens - video camera with AI embedded
    • \\n
    • DynamoDB Global - similar to Azure/Google initiatives
    • \\n
    • EC2 Bare Metal Instances - lots of competitors try to differentiate on this (lunches eaten?)\\n\\n
        \\n
      • came out of the VMware work
      • \\n
      • i3.metal instance types
      • \\n
      • c5 AMIs can work too (new KVM-based instance type)
      • \\n
    • \\n
    • EC2 Instance types, up to 25Gbps networking\\n\\n
    • \\n
    • Elastic Container Service for Kubernetes (EKS) - called it!\\n\\n
        \\n
      • upstream K8s
      • \\n
      • automatically runs K8s with three masters across three AZs
      • \\n
      • monitoring/healthchecks built in, managed service
      • \\n
    • \\n
    • Fargate - Containers on demand, no host/orchestrator needed\\n\\n
        \\n
      • similar to Azure Container Instances
      • \\n
      • apparently Google has App Engine Flexible which is similar (thanks JP!)
      • \\n
    • \\n
    • So, Matt: why would I use EKS instead of Fargate, etc.? Another write-up.
    • \\n
    • FreeRTOS - AWS bought(?) existing open source IoT operating system vendor
    • \\n
    • Glacier/S3 Select - run SQL-like queries against your buckets and storage (CSV & JSON)
    • \\n
    • GuardDuty - continuous security monitoring & threat detection (lunches eaten?)
    • \\n
    • IoT Analytics - MQTT processing, reporting & storage
    • \\n
    • IoT Device Defender - reporting, alerting & mitigation of existing IoT fleets
    • \\n
    • IoT Device Management - lifecycle, management & monitoring of IoT devices
    • \\n
    • Kinesis Video Streams - video ingestion/processing service
    • \\n
    • Media Services - YouTube as a Service, including monetization. Seems there should be an embeddable player somewhere.
    • \\n
    • Neptune - managed graph database service (lunches eaten?)
    • \\n
    • Rekognition Video - Rekognition now does video
    • \\n
    • SageMaker - framework for building AI services
    • \\n
    • Sumerian - VR/AR/3D IDE and platform?
    • \\n
    • Systems Manager - custom dashboards based off of tags, ties into AWS system management tools
    • \\n
    • Time Sync Service - AWS NTP
    • \\n
    • Translate - Google & MS already have this
    • \\n
    • Transcribe - speech recognition, we should use this!
    • \\n
  • \\n
  • More: The New Stack, The Register.
  • \\n
  • This kind of over-the-top analysis is kinda our thing. BACK OFF, MAN!
  • \\n
  • AWS Strategy Update \\n\\n
      \\n
    • On Hybrid Cloud: \\u201cIn the fullness of time \\u2014 I don\\u2019t know if it\\u2019s five, 10 or 15 years out \\u2014 relatively few companies will own their own data centers. Those that do will have a much smaller footprint. It will be a transition and it won\\u2019t happen overnight.\\u201d Link
    • \\n
    • More: \\u2018Is Multi-Cloud Real?: \\u201cWe certainly get asked about it a lot. Most enterprises, when they think about a plan for moving to the cloud, they think they will distribute workloads across a couple of cloud providers. But few actually make that decision because you have to standardize on lowest common denominator when you go multi-cloud. AWS is so far ahead and you don\\u2019t want to handicap developer teams. Asking developers to be fluent in multiple cloud platforms is a lot. And all the cloud providers have volume discounts. If you split workloads across multi-cloud, you\\u2019re diminishing those discounts. In practice, companies pick a predominate cloud provider for their workloads. And they may have a secondary cloud provider just in case they want to switch providers.\\u2019
    • \\n
  • \\n
\\n\\n

AWS re:Invent Preview Review

\\n\\n

\\u2714SaaS lunches will be eaten?
\\n\\u2714Amazon Kubernetes Service?

\\n\\n

This Week in Kubernetes

\\n\\n\\n\\n

End-roll

\\n\\n

Conferences

\\n\\n
    \\n
  • Cot\\xe9\\u2019s junk:\\n\\n
  • \\n
  • Matt\\u2019s (not) on the Road! Taking it off for the Holidays.
  • \\n
\\n\\n

Recommendations

\\n\\n

Sponsored By:

'