Learning #Microsoft terminology is baffling. Try to register an application for [AzureAD|Entra ID].
- Join the [Cloud Partner Program | Microsoft AI Cloud Partner Program]
- Use your [Partner ID|MPNID|MPN|Partner One ID|GlobalPartnerID]
One MS document may use 3 terms for the same thing.
Well, lambda should be at least
SDN and overlay networks are coming for you. We will find a way to overabstract these concepts yet.
I also appreciated this candor. It was respectful of the time and experience of their audience. For devs, "hard down" means "It's not just slow. It's broken. Don't even try. Do something else for a while."
Very interesting! I think I only have capacity to have my mind blown and my workflow supplanted once every few months, but I'll definitely be checking this out.
Is this your project?
Bah!
I've got a workflow with Firefox and container tabs. And that's the way I likes it!
And for changes, it's fantastic! I can change a DNS zone name, and it handles changing and deleting resources that need to be adjusted accordingly.
I feel like I can essentially make an install wizard for my entire cloud environment, including their applications.
Now I no longer need to care about whether a security group gets created before its rules, or a DNS zone gets created before its certificate and Cloudfront instance. I just define all the things that I need, and Terraform figures out the order.
I don't know why I didn't understand that before.
I appreciate Ansible for its flexibility. You can do anything with it at scale. But for Cloud infrastructure deployments, which are more prescriptive than the rest of the universe, Terraform handles the Order of Operations. This was one of the trickiest things for me.
I have been using Ansible to deploy my Cloud infrastructure. I did this because one command could bring my application from zero to fully deployed. Now I'm implementing Terraform for the infrastructure piece. I can't believe how much easier it is.
Listening to Werner Vogels talk about time sync in #awsreinvent. I wonder how they harden for the eventuality of electronic warfare targeting their signals.
gpsjam.org has lots of red dots on it. What happens when one of those is over a DSQL AZ?
The hardest thing about listening to Werner Vogels speak is keeping my mind from running away with ideas. Settle down, he's still speaking. Run over to the whiteboard after he's done. #awsreinvent
There is a lot of technical innovation to appreciate about #awsreinvent. But one thing I keep enjoying on a human level is the flash of panic on presenters' faces when there is a delay in the slide change or teleprompter. Even high powered tech execs have the same stage fright as us mortals.
I am super interested to see how the newly announced AWS Education Equity Initiative might mesh with my work.
I believe this is also what you find at an upscale KFC. "Darling, please pass the table bucket"
#awsreinvent just announced quite the threat to Windows ecosystem. Q Developer is designed to migrate applications to Linux. Year of the Linux Desktop 2005-2025
Good to know! This information might keep me out of a time wasting pickle someday.
Resource Control Policies seem like a common sense approach to avoid a ton of data loss due to unintended configuration changes.
Yep! And then authorizing each individual VPC to use the resolver endpoint.
I wonder if this includes Route53 private zones. Sharing a private zone among many adjacent accounts is pretty Byzantine and expensive currently. Like $150/mo minimum just for private DNS sharing.
It feels like a missed opportunity to name this AWS SneakerNet to really emphasize this product’s historical roots.
