Call for round the year submissions for Rootconf in 2020

Call for round the year submissions for Rootconf in 2020

Submit a proposal at any time in the year on DevOps, infrastructure security, cloud, and distributed systems. We will find you a suitable opportunity to share your work.

Make a submission

Accepting submissions till 31 Dec 2020, 12:00 PM

##About Rootconf:

Rootconf is HasGeek’s annual conference -- and now a growing community -- around DevOps, systems engineering, DevSecOps, security and cloud. The annual Rootconf conference takes place in May each year, with the exception of 2019 when the conference will be held in June.

Besides the annual conference, we also run meetups, one-off public lectures, debates and open houses on DevOps, systems engineering, distributed systems, legacy infrastructure, and topics related to Rootconf.

This is the place to submit proposals for your work, and get them peer reviewed by practitioners from the community.

##Topics for submission:

We seek proposals -- for short and long talks, as well as workshops and tutorials -- on the following topics:

  1. Case studies of shift from batch processing to stream processing
  2. Real-life examples of service discovery
  3. Case studies on move from monolith to service-oriented architecture
  4. Micro-services
  5. Network security
  6. Monitoring, logging and alerting -- running small-scale and large-scale systems
  7. Cloud architecture -- implementations and lessons learned
  8. Optimizing infrastructure
  9. SRE
  10. Immutable infrastructure
  11. Aligning people and teams with infrastructure at scale
  12. Security for infrastructure

##Contact us:

If you have questions/queries, write to us on rootconf.editorial@hasgeek.com

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Bharadwaj Embar

@bharadwajrembar

Secrets management across Microservices with HashiCorp Vault

Submitted Apr 1, 2019

In today’s world of web scale applications, secrets management is a daunting task and is often overlooked, until the product is evaluated for Compliance certifications. Often times, this overhead usually falls on the Execution Platform team as rotation of secrets must also ensure that there is no downtime in the product. The kind of secrets can range from key/value pairs, cloud access credentials, data store access credentials, encrypted data in transit, etc.

At this rate, how does a team scale secrets management and stay complaint?

Enter HashiCorp Vault. In this talk, using a custom built application as an example, we will be looking at how we can leverage Vault in various domains of access control, the challenges behind scaling various secret engines to fit our application’s need, the challenges behind ensuring an HA cluster and idiomatic practices.

Outline

What is secrets management and why everyone needs to implement it as early as possible?
Why not just use a key store for all secrets?
What does HashiCorp Vault bring to the table?
Demo: Generating secrets for an application using Vault (KV, AWS and PostgreSQL)
Patterns to Access Vault
Operational challenges of an HA Setup
Idiomatic Practices

Requirements

There are no requirements. This is for participants who are looking to evaluate/implement secrets management and consider HashiCorp Vault as a prime candidate.

Speaker bio

Bharadwaj is an MTS/Platform Engineer for Nutanix BEAM. A big fan of Open Source and related talks/technologies. Loves to hack open and question everything.

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Make a submission

Accepting submissions till 31 Dec 2020, 12:00 PM

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more