やわらかVault - Pepabo Tech Portal
最近、5kgの重しを背負って懸垂していますプリンシパルエンジニアの @linyows です。 みなさん、NHKの「筋肉は裏切らない！」（正しくは筋肉体操）見てますか？ … はい。ですよね。 GMOペパボは、ロリポップ！やminneなど様々なサービス（microservices的なものではない）を運営しており、それぞれにおいて、秘密情報を管理している状態にあります。この秘密情報を独自に管理するのは、専門のスキルやノウハウとしてあらゆるコストがかかります。 そこで僕（ら）は、秘密情報管理ソフトウェアであるHashiCorp Vaultを各サービスに導入し、サービスを堅牢にするというゴールをもとに社内でVaultのWorkshopを幾度となく開催しています。 今回は、そのWorkshop「やわらかVault」のご紹介です。 やわらかVault これは、HashiCorp Vaultを正しく理解し
Vault with Consul storage reference architecture | Vault | HashiCorp Developer
This guide applies to Vault versions 1.7 and above and Consul versions 1.8 and above. This guide describes recommended best practices for infrastructure architects and operators to follow when deploying Vault using the Consul storage backend in a production environment. This guide includes general guidance as well as specific recommendations for popular cloud infrastructure platforms. For producti
Use HashiCorp Vault in production environment
After see how install localy Vault, we want now use in production environment. We want High availability, Active directory authentication. HA backend storage We use Consul to store data because it allow HA mode. Best practice is to install Consul local agent on same computer (or VM or container). This local agent run in client mode, that mean local agent forwards all RPCs to a server. We create on
Distil Networks securely stores and manages all their secrets with Vault and Consul
PackerBuild and manage images as code
Setting up a secure Vault with a Consul backend
With this blogpost we continue working with a secure Consul environment: We are configuring a secure Vault setup with Consul as backend. YMMV, but this is what I needed to configure to make it work. Environment We should have an working Consul Cluster environment. If you don’t have one, please take a look at here for creating one. With this blogpost we expect a secure Consul cluster with SSL certi
Vault Configuration as Code
Here at Space Ape we use Vault extensively. All of our instances authenticate with Vault using the EC2 auth backend which allows us to restrict the scope of secrets any instance has access to. Behind Vault, we use Consul as a backend to persist our secrets with a good level of durability and make use of Consul’s snapshot feature to create backups, which means we can restore both Consul and Vault f
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
HashiCorp Vault and the Magic of Consul Templates
Vault and Consul – TechLady Blog
Using Hashicorp Vault for Secrets Management