Today we've launched PrivateLink, it's awesome, checkout this blog post ... https://twitter.com/awscloud/status/928356959287431170 … .. then come back, I'm going to tell a small story.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I meant "check out", but you can also checkout while you're at it; it's very easy to spin up an AWS PrivateLink Endpoint. Anyway ... story time ...
Our first iteration of VPC Endpoints is awesome, super popular too. With it you can use an AWS service securely from your VPC, no internet routing, and lock down access to resources with permissions by VPC, but it preserves the services normal public IP addresses.
With the new AWS PrivateLink, we make the service appear and behave as private IPs in your VPC, and they work with security groups, and from direct connect to your office or data center.
(I had to delete and reword the next one due to an error!)
I've always known that 'on prem' is a big market, on the roadmap, etc ... but a huge personal game-changing "AHA!" moment for me was when a customer engineer walked me through how hard the old way made it to write code for the cloud.
She showed me Eclipse running on her laptop and how she had to disable dependencies and integration tests. They couldn't reach the VPC Endpoint, because she was on her laptop at the office, not in the cloud.
For me, fixing that became a personal key goal, because writing and testing reliable code for the cloud should be painless, and networking shouldn't get in the way!
I know that people are going to find all sorts of cool ways to use AWS PrivateLink Endpoints from on-prem, Kinesis for your Intranet! etc ... but I'm super excited for the in-your-IDE end-to-end integration test cases.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.