Trying to get one of my ICANN domain names, thingelstad.xyz, registered on Ethereum Name Service but stumped on DNSSEC error message from ENS, but DNSSEC tests out fine. 🤷♂️
Technology
We hung The Frame by Samsung today and I am impressed with it. It is discrete. The picture quality is good. It is fun to have different art on it and with the press of a button you can watch a show.
Got my Elgato Key Light added to my setup. Having it attach to the desk is key for the standing position. It is also nice to be able to control color and brightness from the Stream Deck. It can get very bright too. 😎
Called up Bevcomm today and upgraded our DSL connection at the cabin to the fastest that we can provision. Hopefully this resolves the lag I’ve been experiencing in Zoom.
Family Screen Time Review
We are trying something new thinking about our family and how we use our devices, most notably our iPhones. We all have enabled Screen Time on our devices and we are doing a weekly Family Screen Time Review. We just did our first review which went really well. We are making it up …
Keep reading · 2 minutes: Family Screen Time ReviewCTO Spotlight: Candid Conversations wth Minnesotan Leaders
I got a chance to join Jac Stark and Nels Pederson of Tech.MN for this CTO Spotlight conversation. We covered a wide range of topics. It was a good conversation. We recorded this in August 2020, but it didn’t get published until December.
Facebook’s opposition to Apple’s privacy enhancements on their platform is a strong positive signal. The fact they are so worried about it validates that these actions must be meaningful in the fight against surveillance.
I’m not sure what happened with our bandwidth usage this month but it was way up from any previous month and we just used our one “free" excess usage month from Xfinity. This would have cost $60 extra this month. I will have to keep an eye on usage and consider adding unlimited data for $30 a month. We didn’t make any notable changes in devices or usage so I’m not sure what drove the jump.
This was the worst production outage I’ve experienced in Amazon Web Services, lasting over 21 hours. AWS has also published the full incident report.
Latest Update (1:18 AM PST): We have restored all traffic to Kinesis Data Streams via all endpoints and it is now operating normally. We have also resolved the error rates invoking CloudWatch APIs. We continue to work towards full recovery for IoT SiteWise and details of the service status is below. All other services are operating normally. We have identified the root cause of the Kinesis Data Streams event, and have completed immediate actions to prevent recurrence.
Previous Update (12:43 PM PST): We have restored all traffic to Kinesis Data Streams via all endpoints and it is now operating normally. We have also resolved the error rates invoking CloudWatch APIs. We continue to work towards full recovery for IoT SiteWise and Elastic Container Service; details of these services’ status is below. All other services are operating normally. We have identified the root cause of the Kinesis Data Streams event, and have completed immediate actions to prevent recurrence.
Previous Update (11:43 PM PST): We have restored all traffic to Kinesis Data Streams via all endpoints, and have resolved the error rates invoking CloudWatch APIs. We are continuing to closely monitor Kinesis and work toward full recovery of all services. We have identified the root cause of the Kinesis Data Streams event, and have completed immediate actions to prevent recurrence. Kinesis and CloudWatch are operating normally.
Previous Update (10:30 PM PST): We have restored all traffic to Kinesis Data Streams from Internet-facing endpoints, and we are continuing to incrementally restore all requests to Kinesis Data Streams using VPC Endpoints. We are also beginning to observe incremental recovery of CloudWatch metrics functionality for new incoming metrics, and working towards full recovery. The backlog of metrics will take additional time to populate.
Previous Update (9:06 PM PST): Over the past two hours, we have continued to bring more traffic in to Kinesis Data Streams, which is leading to gradual recovery of applications that use Kinesis directly, as well as dependent services within the US-EAST-1 Region. We are bringing traffic in more slowly than anticipated while we closely monitor each change to ensure continued stability. We expect that over the next few hours, we will complete restoring Kinesis Data Streams to normal operations.
CloudWatch metrics remain delayed in the US-EAST-1 Region. Once we have restored the throttles for Kinesis to previous levels, we will be restoring CloudWatch metrics functionality. We expect to see recovery of CloudWatch metrics at that stage for new incoming metrics, but the backlog of metrics may take additional time to populate.
Previous Update (6:23 PM PST): We’d like to provide an update on the issue affecting the Kinesis Data Streams API, and other dependent services, within the US-EAST-1 Region. We have now fully mitigated the impact to the subsystem within Kinesis that is responsible for the processing of incoming requests and are no longer seeing increased error rates or latencies. However, we are not yet taking the full traffic load and are working to relax request throttles on the service. Over the next few hours we expect to relax these throttles to previous levels. We expect customers to begin seeing recovery as these throttles are relaxed over this timeframe.
I leveled up my webinar broadcasting capabilities with the addition of a green screen. This setup worked incredibly well with Zoom for our all team meeting today.
Here is what it looks like in Zoom with a virtual background applied.
The theme for the team meeting was a live show where I was the host in the control room. It was a lot of fun to do.
