Moortec Solutions Ltd

Ansible Control Node Deployment and Support

Moortec’s Ansible Service for the Cloud provides a managed hosting platform (control node) for the Ansible Provisioning Platform, and integrates this with the managed nodes.

Available on a range of commercial and secure underlying cloud hosting platforms (including AWS, VMware, Azure), for entry level and enterprise scale Ansible applications.


  • Available on several cloud platforms including AWS and Azure.
  • Platform designed and planned to meet functional and non-functional requirements.
  • Daily Backups included and Disaster Recovery available.
  • Development, Test and Production instances to support development lifecycle.
  • Industry Standard Tool for Operations Management.
  • Supports CI/CD Pipelines
  • Integrates with other tooling like Jenkins, Terraform, etc.


  • Linux and Windows infrastructure available for ease of enterprise integration.
  • Cloud hosting agnostic to ensure competitive pricing and portability.
  • Fully scalable solution will grow with your organisation.
  • UK hosting available for sensitive data storage.
  • Reliable Machine Builds via templates (Terraform, etc.)
  • Repeatable, Reliable Provisioning via Ansible Playbooks.


£150 per instance per month

  • Free trial available

Service documents

G-Cloud 11


Moortec Solutions Ltd

Peter Burke

07771 973310

Service scope

Service scope
Software add-on or extension No
Cloud deployment model
  • Public cloud
  • Private cloud
  • Community cloud
  • Hybrid cloud
Service constraints Limited to platforms supported by Ansible / Ansible Tower.
System requirements N/A

User support

User support
Email or online ticketing support Email or online ticketing
Support response times Within 2 hours. Same at weekends if 24x7 support purchased.
User can manage status and priority of support tickets Yes
Online ticketing support accessibility WCAG 2.1 AA or EN 301 549
Phone support Yes
Phone support availability 9 to 5 (UK time), 7 days a week
Web chat support No
Onsite support Yes, at extra cost
Support levels Support Levels: Gold Service 24 x 375 Priority 1 incidents are responded to within 1 hour. Priority 2 within 4 hours. Priority 3 within 24 hours. Priority 4 within 48 hours. Silver Service Mon-Fri 7am - 9pm Priority 1 incidents are responded to within 4 hours. Priority 2 within 12 hours. Priority 3 within 48 hours. Priority 4 within 5 working days. Bronze Service Mon-Fri 9am - 5pm Priority 1 incidents are responded to within 8 hours. Priority 2 within 24 hours. Priority 3 within 72 hours. Priority 4 within 7 working days. The support costs are included in the compute platform costs, and start from £100 per month per instance. We provide cloud support engineers.
Support available to third parties Yes

Onboarding and offboarding

Onboarding and offboarding
Getting started There is an extensive onboarding process for getting the customers set-up to start to create and manage playbooks within the managed service.

Specific features of the service, such as integration with corporate systems for user authentication will be fully documented.
Service documentation Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction This is not really applicable, customers will manage playbooks using whatever configuration management software they normally use.

At the end of the contract the Ansible control node(s) remain with the customer.
End-of-contract process There are no additional charges for terminating the contract. But network and media charges may apply for extracting large volumes of data.
Customers always retain control and ownership of their data.

Using the service

Using the service
Web browser interface No
Application to install No
Designed for use on mobile devices No
Service interface No
What users can and can't do using the API We support the standard Ansible interfaces for connecting to target nodes.
API documentation No
API sandbox or test environment Yes
Customisation available Yes
Description of customisation The service is the provision of a core Ansible Control Node (or Nodes) for secure software provisioning and operations management. Customers will then be able to develop their own playbooks for use with the Ansible software.


Independence of resources Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. Services which provide virtualized operational environments to customers (i.e. AWS EC2) ensure that customers are segregated via security management processes/controls at the network and hypervisor level.


Service usage metrics No


Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Conforms to BS7858:2012
Government security clearance Up to Developed Vetting (DV)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations Yes
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency At least once a year
Penetration testing approach ‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest Other
Other data at rest protection approach Moortec can provide database encryption, or employ the cloud infrastructure provider's services, such as AWS, to add additional security layers to data at rest, via scalable and efficient encryption features. AWS offers flexible key management options and dedicated hardware-based cryptographic key storage.
Data sanitisation process Yes
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach In-house destruction process

Data importing and exporting

Data importing and exporting
Data export approach Customer staff can be provided with access to the Ansible configuration data and file transfer software, for the purpose of exporting data.

By default customer staff do not have access to this module for security purposes, but this can be requested at no extra charge for data export purposes.
Data export formats
  • CSV
  • Other
Other data export formats Standard Ansible formats.
Data import formats Other
Other data import formats Standard Ansible Formats

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection between networks Network devices, including firewall and other boundary devices, are in place to monitor and control communications at the external boundary of the network and at key internal boundaries within the network. These boundary devices employ rule sets, access control lists (ACL), and configurations to enforce the flow of information to specific information system services. ACLs, or traffic flow policies, are established on each managed interface, which manage and enforce the flow of traffic. ACL policies are approved by Amazon Information Security.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • Other
Other protection within supplier network Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. AWS gives customers ownership and control over their content by design through simple, but powerful tools that allow customers to determine how their content will be secured in transit. AWS enables customers to open a secure, encrypted channel to AWS services using TLS/SSL, and/or IPsec or TLS VPN (if applicable), or other means of protection the customer wish to use. API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS.

Availability and resilience

Availability and resilience
Guaranteed availability The managed service offers availability SLAs of 99.8% for the Ansible control nodes.

Failure to achieve the SLA in any service measurement period (typically a month) will result in a service credit equal to 10% of the monthly service charge.
Approach to resilience Multiple Ansible control nodes can be deployed to provide resilient configurations (no single point of failure in hardware or software) spread across multiple data centres if applicable.
Outage reporting Via email alerts and SMS messages.

Identity and authentication

Identity and authentication
User authentication needed Yes
User authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels AWS IAM provides user access control to AWS hosting services, APIs and specific resources.

Other controls for the CMS application include time, originating IP address, SSL use, and whether users authenticated via MFA devices.
Access restriction testing frequency At least once a year
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password

Audit information for users

Audit information for users
Access to user activity audit information Users have access to real-time audit information
How long user audit data is stored for At least 12 months
Access to supplier activity audit information Users have access to real-time audit information
How long supplier audit data is stored for At least 12 months
How long system logs are stored for At least 12 months

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification No
ISO 28000:2007 certification No
CSA STAR certification No
PCI certification No
Other security certifications No

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance certified No
Security governance approach Moortec's services confirm to ISO27001, but does not have formal accreditation. The underlying infrastructure has ISO27001 accreditation.
Information security policies and processes Cyber Essentials Plus; ISO 27017; ISO 27018; SOC 1/2/3

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Changes to services and features follow secure software development practices, including security risk reviews prior to launch. Developer access to production environments is via explicit access system requests, subject to owner review and authorisation. Teams set bespoke change management standards per service, underpinned by standard Moortec guidelines. All production environment changes are reviewed, tested and approved. Stages include design, documentation, implementation (including rollback procedures), testing (non-production environment), peer to peer review (business impact/technical rigour/code), final approval by authorised party. Emergency changes follow incident response procedures. Exceptions to change management processes are documented and escalated to Moortec management.
Vulnerability management type Supplier-defined controls
Vulnerability management approach Moortec Security performs vulnerability scans on the host operating system, web applications, and databases in the hosted environment. Approved 3rd party vendors conduct external assessments (minimum frequency: quarterly). Identified vulnerabilities are monitored and evaluated. Countermeasures are designed and implemented to neutralise known/newly identified vulnerabilities.
Protective monitoring type Supplier-defined controls
Protective monitoring approach Moortec relies upon AWS deployed (pan-environmental) monitoring devices to collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth usage. Devices monitor: • Port scanning attacks • Usage (CPU, processes, disk utilization, swap rates, software-error generated losses) • Application metrics • Unauthorized connection attempts Near real-time alerts flag potential compromise incidents, based on AWS Service/Security Team- set thresholds. Requests to AWS KMS are logged and visible via the account’s AWS CloudTrail Amazon S3 bucket. Logs provide request information, under which CMK, and identify the AWS resource protected through the CMK use. Log events are available via AWS CloudTrail.
Incident management type Supplier-defined controls
Incident management approach Moortec adopts a three-phased approach to manage incidents: 1. Activation and Notification Phase 2. Recovery Phase 3. Reconstitution Phase To ensure the effectiveness of the Incident Management plan, Moortec conducts incident response testing, providing excellent coverage for the discovery of defects and failure modes as well as testing the systems for potential customer impact. The Incident Response Test Plan is executed annually, in conjunction with the Incident Response plan. It includes multiple scenarios, potential vectors of attack, the inclusion of the systems integrator in reporting and coordination and varying reporting/detection avenues.

Secure development

Secure development
Approach to secure software development best practice Conforms to a recognised standard, but self-assessed

Public sector networks

Public sector networks
Connection to public sector networks No


Price £150 per instance per month
Discount for educational organisations No
Free trial available Yes
Description of free trial Moortec will provide access to a development Ansible tools node instance for up to 3 months for customers to evaluate the service. Note that this is limited capacity and unsuitable to test the application of Ansible to existing large scale installations.

Service documents

pdf document: Pricing document pdf document: Skills Framework for the Information Age rate card pdf document: Terms and conditions
Service documents
Return to top ↑