YES! ! AWS Secrets!!
I’d say secrets in parameter store are like Serverless credentials in Jenkins while secrets in secrets manager are like Serverless hashicorp vault. The difference for now is in the limits of use – SSM is free but would not work well when saturated with many calls – you are expected to use it moderately, while in AWS secrets you are not limited cause you pay. I believe in the future AWS secrets will be more feature-rich.
New feature in AWS Redshift allows automatic audit logs shipping to S3 for complete backward analysis beyond the few days log kept inside Redshift
The latest Cloud Forms from Redhat targets the easy use of AWS Cloud Formation and OpenStack Heat templates import, customization, creation, deployment.
It offers a service catalog of Cloud resources setups including load balancers, servers and more.
It also makes it easier to customize your Cloud templates by offering forms and variables per the templates you pick.
Then it triggers Ansible Tower for in depth deployment and configuration management of your instances.
The Cloud Management portal shows you your Cloud components, instances, operating systems and applications including general Linux and Windows as well.
Sounds perfect?
Maybe it sounds like an enterprise vendor trying to grab it all..and maybe this time this vendor actually makes it..
I still would like to see TerraForm there as well..
Anyway there's the video
You can set a Highly Available Kubernetes cluster by adding worker node pools and master replicas.
That's true as of Kubernetes version 1.5.2. It is supported using the kube-up/kube-down scripts for GCE (as alpha): http://blog.kubernetes.io/2017/02/highly-available-kubernetes-clusters.html?m=1
For AWS you have support for HA Kubernetes cluster using KOPS scripts:
GCP Big Table – main facts:
Is the basis of many google products
Object storage system
Does not offer indexes except for a single range index you can use
Is the basis for Hadoop big data system
You pay for storage separately
You pay for min 3 nodes and can expand as you need
Nodes are needed just for read / write – not for storage
Support for massive amounts of reads / writes but not locking or transaction support
Is not completely and highly available since sometimes data is not available as it is moved around
Great for big queries, less for short quick rapid ones
Here are the main points in this brilliant session by Ade McCormack on the new age of workplace, employment and skills
Managers were needed in the Industrial Age to keep an eye on employees that did not like the automatic tasks they had to do
Now automation took over those jobs
There is no room for laziness
The need is for talented people and leaders
Those are passionate people who are eager to do much more than any manager could demand
Talents look for innovation, mobility/flexibility/fun-ability , work/life balance, playing with other great people – all those so much worthy than money, yet so hard to create
When you create a great workplace, great people will join, driving great customers to you as they provide massive value
Nowadays risk is hooked to value
You have to bring risk into your work plans to make real progress
As you play in risky arenas you need some peripheral sensory – data about new risks
You need to spend time trying out the new risk related technologies even if there is no guarantee they will materialize into actual danger
Leaders must make sure their teams don't have any interference to gain and maintain a state of "flow" – joyful focus on exercising their maximum abilities
Treat your career as a lean startup – choose what you are passionate about, have great skills at, and got market demand for
Ask yourself everyday- am I working in a place that allows me to gain my maximum market value
How hard do you practice and learn to become world class in your arena?
Infinit storage solution similar to GlusterFS but with a wide set of hybrid options such as S3, GCS and more. Just beautiful!
Recently acquired by Docker..
Are you using it already?
I have seen a peered Mongo!https://www.mongodb.com/blog/post/introducing-vpc-peering-for-mongodb-atlas
Using a DE-Centralized (Master-Less) Puppet stack has its benefits for dynamic fast morphing environments.
Yet you'd still love to get all changes made to your environment recorded in a central repo.
Check out factbeat from Elasticsearch community. It's a beat that ships Puppet Facter facts to Elasticsearch, where they can be stored, analyzed, displayed and compared over time.
Factor can be easily customized to ship new types of configuration information as your heart desires.
What are you using?
What I liked:
