Drupal Optimised AWS Hosting
Zoocha Drupal optimised AWS hosting leverages the Amazon Web Services toolset to provide a high performance hosting solution for Drupal in the cloud. It reduces the time required to obtain and boot new server instances, allowing you to quickly scale capacity, both up and down, as your computing requirements change.
Features
- Drupal Optimised AWS Hosting Infrastructure
- Suitable for OFFICIAL (formerly IL2/IL3) and/or SENSITIVE workloads
- 7 availability zones, 3 EU regions (including the UK)
- NCSC Cloud Security Principles aligned, Security Cleared (SC) staff available
- Elastic, web-scale computing made easier for developers
- Complete control of your computing resources
- Choice of multiple instance types, operating systems, and software packages
- Select configuration of memory, CPU, and instance storage
- Tools to build failure resilient and scalable applications
Benefits
- High performance Drupal hosting on tailored AWS infrastructure
- Comprehensive, cross service API audit logging and security (CloudTrail)
- Integration with other AWS services (24x7 support and consolidated billing)
- Training and architectural patterns/guidance (well architected)
- Quickly scale capacity, both up and down
- Obtain and configure capacity with minimal friction
- Pay only for capacity you actually use
- Highly reliable environment
- Migrate services by importing VMs from Vmware and HyperV
Pricing
£150 an instance a month
Service documents
Request an accessible format
Framework
G-Cloud 13
Service ID
7 8 3 4 2 6 7 5 6 5 9 1 2 3 8
Contact
Zoocha Limited
William Huggins
Telephone: 441992256700
Email: info@zoocha.com
Service scope
- Service constraints
- N/A
- System requirements
-
- Drupal
- PHP
User support
- Email or online ticketing support
- Email or online ticketing
- Support response times
- 15 minutes for critical support
- User can manage status and priority of support tickets
- Yes
- Online ticketing support accessibility
- WCAG 2.1 A
- Phone support
- Yes
- Phone support availability
- 24 hours, 7 days a week
- Web chat support
- No
- Onsite support
- No
- Support levels
- Zoocha provide a single tier support service which is contracted as 'support days per month' @ £675 per day. There is no limit to the number of tickets raised, but support time above the contracted amount is charged at £150 per hour. Contracted support time can be increased or decreased (to a minimum of 1 day per month) at any time during the contract, by providing 30 days notice. Account management can be provided at an additional cost of £700 per day.
- Support available to third parties
- Yes
Onboarding and offboarding
- Getting started
- Zoocha provide a fully managed service for Drupal hosting on AWS. In addition, AWS provides a range of resources to help customers get started. These include: comprehensive documentation (in multiple formats), introductory videos, hands-on labs, online and in-person training, access to a large ecosystem of partners and support from the public sector account team.
- Service documentation
- Yes
- Documentation formats
-
- HTML
- End-of-contract data extraction
- As part of the Zoocha managed service, all client data will be extracted and securely transferred to the client at the end of the contract. In addition, data may be copied out directly from AWS using OS-level tools (such as xopy or rsync).
- End-of-contract process
-
Buyer may terminate the relationship with Supplier for any reason by (i) providing Supplier with notice and (ii) closing Buyers account for all services for which Supplier provide an account closing mechanism.
Supplier customers retain control and ownership of their data. Supplier will not erase customer data for 30 days following an account termination. This allows customers to retrieve content from Supplier services so long as the customer has paid any charges for any post-termination use of the service offerings and all other amounts due.
Using the service
- Web browser interface
- Yes
- Using the web interface
-
Almost all functionality for each of our services is exposed through the web console.
The web console facilitates management for all aspects of the AWS account in a consolidated view whilst providing access to all services and their respective functionalities.
In some cases, specific configuration parameters of a service are dedicated to, and only available from, the CLI, SDK, or API interface. - Web interface accessibility standard
- None or don’t know
- How the web interface is accessible
- You can sign in to the Support Center at https://console.aws.amazon.com/support/home#/ by using the email address and password associated with your AWS account. To log in with other credentials, see Accessing AWS Support.
- Web interface accessibility testing
- None
- API
- Yes
- What users can and can't do using the API
- All functionality is exposed via an API.
- API automation tools
-
- Ansible
- Chef
- SaltStack
- Terraform
- Puppet
- Other
- Other API automation tools
-
- Wide range of 3rd party services hook into AWS APIs.
- SDKs for Python
- SDKs for Ruby
- SDKs for PHP
- SDKs for JavaScript
- SDKs for Java
- SDKs for .NET
- SDKs for Node.js
- API documentation
- Yes
- API documentation formats
-
- HTML
- Other
- Command line interface
- Yes
- Command line interface compatibility
-
- Linux or Unix
- Windows
- MacOS
- Using the command line interface
- All functionality is available via the CLI.
Scaling
- Scaling available
- Yes
- Scaling type
- Automatic
- 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. EC2) ensure that customers are segregated via security management processes/controls at the network and hypervisor level.
AWS continuously monitors service usage to project infrastructure needs to support availability commitments/requirements. AWS maintains a capacity planning model to assess infrastructure usage and demands at least monthly, and usually more frequently. In addition, the AWS capacity planning model supports the planning of future demands to acquire and implement additional resources based upon current resources and forecasted requirements. - Usage notifications
- Yes
- Usage reporting
-
- API
- SMS
- Other
Analytics
- Infrastructure or application metrics
- Yes
- Metrics types
-
- CPU
- Disk
- HTTP request and response status
- Network
- Number of active instances
- Other
- Other metrics
-
- AWS resources: e.g. Amazon EC2/Amazon RDS DB instances, DynamoDB tables
- Custom metrics generated by customers’ applications and services
- Metrics associated with log files generated by the application
- Reporting types
-
- API access
- Real-time dashboards
- Regular reports
- Reports on request
Resellers
- Supplier type
- Reseller providing extra features and support
- Organisation whose services are being resold
- AWS
Staff security
- Staff security clearance
- Other security clearance
- Government security clearance
- Up to Baseline Personnel Security Standard (BPSS)
Asset protection
- Knowledge of data storage and processing locations
- Yes
- Data storage and processing locations
-
- United Kingdom
- European Economic Area (EEA)
- Other locations
- User control over data storage and processing locations
- Yes
- Datacentre security standards
- Supplier-defined controls
- Penetration testing frequency
- At least every 6 months
- Penetration testing approach
- Another external penetration testing organisation
- Protecting data at rest
- Other
- Other data at rest protection approach
-
AWS adheres to independently validated privacy, data protection, security protections and control processes. (Listed under “certifications”).
AWS is responsible for the security of the cloud; customers are responsible for security in the cloud. AWS enables customers to control their content (where it will be stored, how it will be secured in transit or at rest, how access to their AWS environment will be managed).
Wherever appropriate, AWS offers customers options 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
- Hardware containing data is completely destroyed
- Equipment disposal approach
- In-house destruction process
Backup and recovery
- Backup and recovery
- Yes
- What’s backed up
- Machine Image
- Backup controls
- Manual or scheduled API call
- Datacentre setup
- Multiple datacentres with disaster recovery
- Scheduling backups
- Users schedule backups through a web interface
- Backup recovery
- Users can recover backups themselves, for example through a web interface
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
- Data protection within supplier network
- 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
- Guaranteed availability
-
AWS currently provides SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, SLAs are best reviewed directly on the website via the links below:
• Amazon EC2 SLA: http://aws.amazon.com/ec2-sla/
• Amazon S3 SLA: http://aws.amazon.com/s3-sla
• Amazon CloudFront SLA: http://aws.amazon.com/cloudfront/sla/
• Amazon Route 53 SLA: http://aws.amazon.com/route53/sla/
• Amazon RDS SLA: http://aws.amazon.com/rds-sla/
• AWS Shield Advanced SLA: https://aws.amazon.com/shield/sla/
Well-architected solutions on AWS that leverage AWS Service SLA’s and unique AWS capabilities such as multiple Availability Zones, can ease the burden of achieving specific SLA requirements. - Approach to resilience
-
The AWS Business Continuity plan details the process that AWS follows in the case of an outage, from detection to deactivation. AWS has developed a three-phased approach: Activation and Notification Phase, Recovery Phase, and Reconstitution Phase. This approach ensures that AWS performs system recovery and reconstitution efforts in a methodical sequence, maximizing the effectiveness of the recovery and reconstitution efforts and minimizing system outage time due to errors and omissions.
AWS maintains a ubiquitous security control environment across all regions. Each data centre is built to physical, environmental, and security standards in an active-active configuration, employing an n+1 redundancy model, ensuring system availability in the event of component failure. Components (N) have at least one independent backup component. All data centres are online and serving traffic. In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites.
Customers are responsible for implementing contingency planning, training and testing for their systems hosted on AWS. AWS provides customers with the capability to implement a robust continuity plan, including the utilization of frequent server instance back-ups, data redundancy replication, and the flexibility to place instances and store data within multiple geographic regions across multiple Availability Zones. - Outage reporting
- Public dashboard; personalised dashboard with API and events; configurable alerting (email / SMS / messaging)
Identity and authentication
- User authentication
-
- 2-factor authentication
- Identity federation with existing provider (for example Google apps)
- Limited access network (for example PSN)
- Dedicated link (for example VPN)
- Username or password
- Other
- Other user authentication
-
AWS controls access via unique user ID/password authentication. No actions are permissible without authentication. Remote access is multi-factor, login attempts are limited, remote administrative access attempts are logged and reviewed by Security. Suspicious activity initiates incident response procedures.
A session lock out policy that is systematically enforced: locks are retained until identification/authentication procedures are concluded.
AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost. - Access restrictions in management interfaces and support channels
-
IAM provides user access control to AWS services, APIs and specific resources. Other controls include time, originating IP address, SSL use, and whether users authenticated via MFA devices.
API calls to launch/terminate instances, change firewalls, and perform other functions are signed by customers’ Amazon Secret Access Key (either the root AWS Account’s Secret Access Key or the Secret Access key of a user created with AWS IAM). Amazon EC2 API calls cannot be made on customers’ behalf without access to customers’ Secret Access Ke.
API calls can be encrypted with TLS/SSL for confidentiality and customers can use TLS/SSL-protected API endpoints. - Access restriction testing frequency
- At least every 6 months
- Management access authentication
- 2-factor authentication
- Devices users manage the service through
- Dedicated device on a segregated network (providers own provision)
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
- User-defined
- Access to supplier activity audit information
- You control when users can access 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
- ISO/IEC 27001 certification
- Yes
- Who accredited the ISO/IEC 27001
- EY CertifyPoint
- ISO/IEC 27001 accreditation date
- 11/11/2016
- What the ISO/IEC 27001 doesn’t cover
- N/A
- ISO 28000:2007 certification
- No
- CSA STAR certification
- Yes
- CSA STAR accreditation date
- 11/11/2016
- CSA STAR certification level
- Level 2: CSA STAR Attestation
- What the CSA STAR doesn’t cover
- N/A
- PCI certification
- Yes
- Who accredited the PCI DSS certification
- Coalfire Systems Inc
- PCI DSS accreditation date
- 11/07/2016
- What the PCI DSS doesn’t cover
- N/A
- Cyber essentials
- Yes
- Cyber essentials plus
- Yes
- Other security certifications
- Yes
- Any other security certifications
-
- Cyber Essentials Plus
- ISO 27001
Security governance
- Named board-level person responsible for service security
- Yes
- Security governance certified
- Yes
- Security governance standards
- ISO/IEC 27001
- Information security policies and processes
-
Both Zoocha and AWS implement formal, documented policies and procedures that provide guidance for operations and information security within the organisation. Policies address purpose, scope, roles, responsibilities and management commitment.
Employees maintain policies in a centralised and accessible location. AWS Security Assurance is responsible for familiarizing employees with the AWS security policies.
AWS has established information security functions that are aligned with defined structure, reporting lines, and responsibilities. Leadership involvement provides clear direction and visible support for security initiatives.
The output of AWS Leadership reviews include any decisions or actions related to:
• Improvement of the effectiveness of the ISMS.
• Update of the risk assessment and treatment plan.
• Modification of procedures and controls that affect information security to respond to internal or external events that may impact the ISMS.
• Resource needs.
• Improvement in how the effectiveness of controls is measured.
Policies are approved by AWS leadership at least annually or following a significant change to the AWS environment.
Operational security
- Configuration and change management standard
- Supplier-defined controls
- Configuration and change management approach
-
Changes to AWS 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 AWS 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 AWS incident response procedures. Exceptions to change management processes are documented and escalated to AWS management. - Vulnerability management type
- Supplier-defined controls
- Vulnerability management approach
-
AWS Security performs vulnerability scans on the host operating system, web applications, and databases in the AWS 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.
AWS Security monitors newsfeeds/vendor sites for patches and receives customer intelligence via http://aws.amazon.com/security/vulnerability-reporting/.
Zoocha are responsible for all scanning, penetration testing, file integrity monitoring and intrusion detection for their Amazon EC2 and Amazon ECS instances/ applications. Scans should include customer IP addresses (not AWS endpoints). AWS endpoint testing is part of AWS compliance vulnerability scans. - Protective monitoring type
- Supplier-defined controls
- Protective monitoring approach
-
AWS deploys (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 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 visible after turning on AWS CloudTrail. - Incident management type
- Supplier-defined controls
- Incident management approach
-
Zoocha Drupal hosting benefits from AWS three-phased approach to managing incidents:
1. Activation and Notification Phase
2. Recovery Phase
3. Reconstitution Phase
To ensure the effectiveness of the AWS Incident Management plan, AWS 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
- Approach to secure software development best practice
- Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)
Separation between users
- Virtualisation technology used to keep applications and users sharing the same infrastructure apart
- Yes
- Who implements virtualisation
- Supplier
- Virtualisation technologies used
- Other
- Other virtualisation technology used
- AWS proprietary
- How shared infrastructure is kept separate
-
Customer environments are logically segregated, preventing users and customers from accessing unassigned resources. Customers maintain full control over their data access. Services which provide virtualized operational environments to customers, ensure that customers are segregated and prevent cross-tenant privilege escalation and information disclosure via hypervisors and instance isolation.
Different instances running on the same physical machine are isolated from each other via the Xen hypervisor. The Amazon EC2 firewall resides within the hypervisor layer, between the physical network interface and the instance's virtual interface. All packets pass through this layer. The physical random-access memory (RAM) is separated using similar mechanisms.
Energy efficiency
- Energy-efficient datacentres
- Yes
- Description of energy efficient datacentres
-
AWS is committed to running our business in the most environmentally friendly way possible. In addition to the environmental benefits inherently associated with running applications in the cloud, AWS has a long-term commitment to achieve 100% renewable energy usage for our global infrastructure footprint. We’ve made a lot of progress on this commitment. In January 2018, AWS achieved 50% renewable energy usage.
To date, we have announced nine new renewable energy projects (three wind farms and six solar farms), and these projects will deliver a total of 2 million MWh of energy annually onto the electric grid powering AWS data centers located in the AWS US East (Ohio) and AWS US East (N. Virginia) Regions. The electricity produced from these projects is enough to power the equivalent of over 190,000 U.S. homes annually, which is approximately the size of the city of Atlanta, Georgia.
More information is available on the AWS and Sustainability page.
AWS introduced its first carbon-neutral region in 2011. Today, AWS offers customers five AWS Regions that are carbon-neutral:
• US West (Oregon)
• AWS GovCloud (US-West)
• EU (Frankfurt)
• EU (Ireland)
• Canada (Central)
Social Value
- Fighting climate change
-
Fighting climate change
Zoocha are ISO 14001 certified for Environmental Management and are working towards net zero/ carbon neutrality. Our policies and procedures aim to influence our team, client and supply partners to consider and minimise the environmental impact of our activities. With an office based in Brazil, we are acutely aware of the impact of climate change and aim to minimise our impact as much as possible. This is covered in our ISO 14001 certification that is shared through each level of our business, it also includes proactively encouraging our team to make suggestions and recommendations to further reduce our environmental impact outside of our baseline EMS. - Covid-19 recovery
-
Covid-19 recovery
Zoocha have implemented additional staff services to support the mental health of the team in light of COVID-19 and the impact it has had on wellbeing. We have also invested in additional facilities and workplace conditions that support the COVID-19 recovery effort
including effective social distancing and hybrid working arrangements. This includes facilitating remote working and encouraging our team to make the most of our global offices to further foster a collaborative and supportive team environment. - Tackling economic inequality
-
Tackling economic inequality
Zoocha strive to create a diverse working environment which includes seeking candidates from different social and economic backgrounds. We promote retraining for people re-entering the workforce and we work with our client partners to explore opportunities for training and development of their teams and communities. Additionally, we recognise our proximity to London and ensure to pay all employees above the London Living Wage, with the flexibility to work from home to further ensure everyone is able to work comfortably at Zoocha. Additionally, we are proud to offer salary transparency through published and communicated pay scales for each role within our team, alongside the requirements to meet each level of pay and responsibility. This ensures we are proactively fostering transparency that eliminates the potential for discriminatory pay distribution. - Equal opportunity
-
Equal opportunity
Zoocha believe that policies alone are not enough to build an inclusive culture or workplace and that promoting diversity shouldn’t be a box-ticking exercise. At Zoocha, it is about ensuring that no one feels left out, excluded or undermined because of their age, disability, gender reassignment, race, religion or belief, sex, sexual orientation, marriage/ civil partnership, pregnancy and maternity, or factors such as social background. Zoocha actively promotes an inclusive working environment which allows and encourages people to be themselves at work. This means creating a culture where discrimination is eliminated, and an environment of equal opportunities where everyone recognises the positive contribution a diverse workforce and community can make. - Wellbeing
-
Wellbeing
Zoocha strive to support the health and wellbeing of the team, including physical and mental health, through the facilities we provide and benefits we offer. For example, everyone is entitled to free gym membership and we provide access to a mental health service that gives everyone access to self help and counselling experts. We recognise that many of our team members have conflicting personal responsibilities that need to be managed alongside their work responsibilities. This is why we offer flexible working hours, extended maternity and paternity leave and private healthcare to support our team as much as possible inside and outside of work. This approach has resulted in our recognition as a Great Place to Work and several nominations for workplace wellbeing.
Pricing
- Price
- £150 an instance a month
- Discount for educational organisations
- No
- Free trial available
- No