<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SoftBank &#8211; Best DevOps</title>
	<atom:link href="https://www.bestdevops.com/tag/softbank/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.bestdevops.com</link>
	<description>Lets Learn, Do it &#38; Share! Thats a Best DevOps!!!</description>
	<lastBuildDate>Tue, 13 Oct 2026 12:29:24 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>How SoftBank Used Red Hat Ansible Tower to Cut SSL Certificate Update Time by 99%</title>
		<link>https://www.bestdevops.com/softbank-selects-red-hat-ansible-tower-to-improve-efficiency-and-reduce-deployment-times/</link>
					<comments>https://www.bestdevops.com/softbank-selects-red-hat-ansible-tower-to-improve-efficiency-and-reduce-deployment-times/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Thu, 29 Aug 2019 11:43:35 +0000</pubDate>
				<category><![CDATA[Ansible]]></category>
		<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Efficiency]]></category>
		<category><![CDATA[SoftBank]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=7360</guid>

					<description><![CDATA[SoftBank deployed Red Hat Ansible Tower to automate SSL certificate updates across load balancers, reducing update time from up to two hours down to 20 seconds and cutting total work hours by 99%.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>Source: <a href="https://www.businesswire.com" rel="noopener">businesswire.com</a>. This article summarizes a case study originally published by Red Hat in August 2019.</em></p>



<h2 class="wp-block-heading">Background: SoftBank&#8217;s Automation Strategy</h2>



<p class="wp-block-paragraph">Headquartered in Tokyo, SoftBank is one of Japan&#8217;s largest telecommunications service providers. The company has pursued an aggressive internal efficiency programme over several years. In 2015, SoftBank adopted the internal slogan <strong>&#8220;Half &amp; Twice&#8221;</strong> — a commitment to cut manual effort and costs by half through technology adoption while simultaneously doubling productivity and creativity. The following year, the 2016 slogan <strong>&#8220;Smart &amp; Fun!&#8221;</strong> reinforced the message, encouraging employees to redirect time saved by automation toward innovative and higher-value activities.</p>



<p class="wp-block-paragraph">As a practical expression of these goals, SoftBank identified SSL certificate management as a prime candidate for automation. The process of updating SSL certificates on load balancers — used for back-end server access on public-facing websites as well as internal systems — was entirely manual, operator-dependent, and increasingly burdensome.</p>



<h2 class="wp-block-heading">The Problem: Manual SSL Certificate Updates at Scale</h2>



<p class="wp-block-paragraph">SSL certificates are critical to securing server connections, but managing them across a large, heterogeneous infrastructure introduces significant operational overhead. At SoftBank, the challenge was compounded by several factors:</p>



<ul class="wp-block-list">
<li><strong>Different procedures per system:</strong> Each load balancer or system type required its own operator and its own update procedure, meaning no single workflow could be reused across environments.</li>
<li><strong>Manual documentation burden:</strong> Engineers had to prepare a separate operations manual for each update cycle.</li>
<li><strong>Variable update times:</strong> Depending on the system and the individual operator&#8217;s skill level, a single certificate update could take anywhere from 30 minutes to two hours.</li>
<li><strong>High update frequency:</strong> Changes to industry standards and certificate validity rules meant SoftBank needed to perform approximately <strong>800 certificate updates per year</strong> — a volume that made the manual approach unsustainable.</li>
<li><strong>After-hours work:</strong> Many updates were performed at night to avoid impacting production systems, placing an additional burden on operations staff.</li>
</ul>



<h2 class="wp-block-heading">The Solution: Red Hat Ansible Tower</h2>



<p class="wp-block-paragraph">To address these challenges, SoftBank deployed <strong>Red Hat Ansible Tower</strong> (now known as Red Hat Ansible Automation Platform&#8217;s controller component). Ansible Tower provides a web-based UI, role-based access control, job scheduling, and centralised logging on top of the core Ansible automation engine — capabilities that made it well-suited to standardising and delegating certificate update tasks across a large operations team.</p>



<p class="wp-block-paragraph">SoftBank worked closely with <strong>Red Hat Consulting</strong> throughout the implementation to design Ansible Playbooks that encoded the previously manual, per-system procedures into repeatable, auditable automation.</p>



<h2 class="wp-block-heading">Measured Outcomes</h2>



<p class="wp-block-paragraph">SoftBank reported the following results after deploying Ansible Tower for SSL certificate management:</p>



<figure class="wp-block-table"><table><thead><tr><th>Metric</th><th>Before Ansible Tower</th><th>After Ansible Tower</th></tr></thead><tbody><tr><td>Time per certificate update</td><td>30 minutes – 2 hours</td><td>As little as 20 seconds</td></tr><tr><td>Total work hours for updates</td><td>Baseline</td><td>Reduced by 99%</td></tr><tr><td>Update accuracy</td><td>Operator-dependent</td><td>Standardised via Playbooks</td></tr><tr><td>After-hours burden on staff</td><td>Significant</td><td>Substantially reduced</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">By codifying update procedures into shared Ansible Playbooks, SoftBank eliminated the skill-level variability that had previously made update times unpredictable. Updates became consistent, fast, and executable by a broader range of staff without requiring deep per-system expertise.</p>



<h2 class="wp-block-heading">Team Enablement and Skills Development</h2>



<p class="wp-block-paragraph">The Red Hat Consulting engagement extended beyond tooling implementation to include structured skills transfer. As a result, approximately <strong>30% of employees in the department</strong> using Ansible Tower obtained a <strong>Red Hat Expert Certificate — Ansible Automation</strong>. The time freed up from repetitive manual update tasks was redirected toward learning new skills and improving broader operational processes — directly realising SoftBank&#8217;s &#8220;Smart &amp; Fun!&#8221; workforce strategy.</p>



<h2 class="wp-block-heading">Planned Expansion</h2>



<p class="wp-block-paragraph">Following the success of the SSL certificate automation initiative, SoftBank outlined plans to extend Ansible automation to additional infrastructure domains, including:</p>



<ul class="wp-block-list">
<li>Datacenters both inside and outside the company</li>
<li>Network devices and configuration management</li>
<li>Appliance devices used on internal networks</li>
<li>Existing on-premises servers</li>
</ul>



<h2 class="wp-block-heading">Key Takeaways for DevOps and Infrastructure Teams</h2>



<p class="wp-block-paragraph">SoftBank&#8217;s case illustrates several automation principles applicable to any large infrastructure team:</p>



<ol class="wp-block-list">
<li><strong>Target high-frequency, low-complexity tasks first.</strong> SSL certificate updates were a strong automation candidate because they were frequent, well-defined, and performed consistently enough to be encoded in Playbooks without major exception handling complexity.</li>
<li><strong>Standardise before you automate.</strong> Ansible Playbooks forced SoftBank to rationalise the different per-system procedures, which itself improved consistency before any execution benefit was realised.</li>
<li><strong>Pair tooling adoption with formal training.</strong> The Red Hat Consulting engagement ensured the team could maintain and extend automation independently, rather than creating a dependency on external support.</li>
<li><strong>Measure the human impact, not just the technical metrics.</strong> Reducing after-hours work and enabling employees to pursue skill development are outcomes that matter to retention and morale, not just to SLAs.</li>
</ol>



<h2 class="wp-block-heading">Supporting Quotes</h2>



<p class="wp-block-paragraph"><em>Mochizuki Hirokazu, President and Representative Director, Red Hat K.K.:</em><br>&#8220;SoftBank faced the challenge of efficiently managing operations in complicated IT environments. By automating IT operations dependent on individual skills and reducing manual operations, Red Hat Ansible Tower has helped SoftBank improve organizational productivity and quality of services as well as reduce maintenance time.&#8221;</p>



<p class="wp-block-paragraph"><em>Takayori Maeda, Section Manager, Technology Unit, IT &amp; Network Unit, Information Technology Division, IT Infrastructure Division, SoftBank Corp.:</em><br>&#8220;The adoption of Red Hat Ansible Tower has helped enable quicker and more flexible automation of our network infrastructure management work. With Red Hat Consulting we have been able to train our technical personnel to use Red Hat Ansible Tower, which has led to improved operations. We plan to expand our use of Red Hat Ansible Tower to provide a higher-quality and more reliable infrastructure.&#8221;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/softbank-selects-red-hat-ansible-tower-to-improve-efficiency-and-reduce-deployment-times/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
