This service enables customers to run workloads on AWS without the overhead of designing, deploying, monitoring and managing the AWS resources.
Redcentric combines technology expertise, automated services, AWS best practices, design and support expertise to deliver end to end AWS solutions.
- AWS workloads designed to match your requirements.
- Deployed by Redcentric.
- Managed by Redcentric.
- Monitored by Redcentric.
- Optimised by Redcentric.
- Supported by Redcentric.
- Secured by Redcentric.
- Redcentric manages your infrastructure, you manage your business.
- Pay for what you use.
- Scales to meet demand.
- Manage workloads more efficiently.
- Manage workloads more cost-effectively.
- Migration to AWS to get workloads up and running
£0.01 per unit per month
- Free trial available
Redcentric Solutions Limited
|Service constraints||Not Applicable|
|System requirements||Not Applicable|
|Email or online ticketing support||Email or online ticketing|
|Support response times||Redcentric aim's to respond to all questions within 15 minutes, 24 / 7|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
|Support levels||Redcentric’s customer service operation is available 24/7/365 and can be contacted by telephone, email or via the customer portal. Support is included at no additional cost with Redcentric's services. Redcentric has one direct point of contact for customer support, which deals with all aspects of the service. The Redcentric customer services team takes full responsibility for supporting and logging problems and technical support queries. Their specific role is to ensure that all telephone, email and portal queries are answered and resolved as promptly as possible. Redcentric has a team of Technical Account Managers and Cloud Support Engineers available. These teams are not included as a standard service and are charged based on the published SFIA rate card.|
|Support available to third parties||Yes|
Onboarding and offboarding
Redcentric provides Technical Account Manager who coordinates the process of getting your application up and running on AWS. Redcentric also provides a dedicated technical architect to design your infrastructure solution based on best practices.
AWS provides a range of resources to help customers get started on our services. 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.
|End-of-contract data extraction||Depending on the type of AWS services in use, data may be copied out using OS-level tools (such as xopy or rsync) or APIs.|
Buyer may terminate the relationship with Redcentric for any reason by (i) providing Redcentric with 30 days notice and (ii) closing their account for all services for which Redcentric provides an account closing mechanism, or instructing Redcentric in writing to close the services.
Buyers pay for the services they use to the point of account termination.
Redcentric customers retain control and ownership of their data. AWS will not erase customer data for 30 days following an account termination. This allows customers to retrieve content from AWS services so long as the customer has paid any charges for any post-termination use of the service offerings and all other amounts due.
In case for any reasons customers want to end their contract with Redcentric but continue with AWS, Redcentric can assist in transitioning your account directly to AWS or your preferred AWS service provider.
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||
The Redcentric portal is designed using OpenSource technology which is compatible with most accessibility devices.
Text size can be increase and text recognition tools work in most circumstances.
|Web interface accessibility testing||None|
|What users can and can't do using the API||All AWS functionality is exposed via an API.|
|API automation tools||
|Other API automation tools||
|API documentation formats||
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||All AWS functionality is available via the CLI.|
|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.
|Infrastructure or application metrics||Yes|
|Supplier type||Reseller providing extra features and support|
|Organisation whose services are being resold||Amazon Web Services|
|Staff security clearance||Other security clearance|
|Government security clearance||Up to Security Clearance (SC)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing 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.
AWS is responsible for the security of the cloud; Redcentric provides guidance and resources to assist security in the cloud for the customers.
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, we offer 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||
|Equipment disposal approach||In-house destruction process|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||
|Backup controls||Manual or scheduled API call|
|Datacentre setup||Multiple datacentres with disaster recovery|
|Scheduling backups||Users schedule backups through a web interface|
|Data protection between buyer and supplier networks||
|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 wishes to use.
API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS
Availability and resilience
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 AWS 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||
Redcentric will work with customers to understand their disaster recovery/resilience requirements, and will architect a solution designed to meet the defined recovery time / point objectives.
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. In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites.
AWS provides 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
|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 Key.
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||
|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|
|Who accredited the PCI DSS certification||Coalfire Systems Inc|
|PCI DSS accreditation date||11/07/2016|
|What the PCI DSS doesn’t cover||Rackspace fanatical support services for AWS is also PCI certified.|
|Other security certifications||Yes|
|Any other security certifications||
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||
|Other security governance standards||Cyber Essentials Plus; ISO 27017; ISO 27018; SOC 1/2/3|
|Information security policies and processes||
AWS implements 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.
|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. 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.
All customer related changes will be managed through Redcentric change management systems. Redcentric will manage the change as scheduled, keeping you fully informed on progress.
|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/.
AWS customers 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||
Redcentric will confirm any monitoring requirements in addition to our default configuration. Your account manager will provide guidance and consultation around best practices. 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
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.
|Incident management type||Supplier-defined controls|
|Incident management approach||Redcentric will apply a consistent approach to all incidents, except where a specific approach is agreed upon with you in accordance with your custom runbook. Incidents can be initiated by either: named customer contacts, Redcentric , event management tools (e.g., Redcentric Watchman or AWS CloudWatch). All incidents are logged in tickets accessible via the AWS Control Panel. Redcentric Support teams will investigate the incident in accordance with the agreed service level. Redcentric support will carefully review instructions on your account, will communicate regularly with you throughout the incident and may escalate the incident at any time until resolution is achieved.|
|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.
|Price||£0.01 per unit per month|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||AWS consumption fees are waived for a 30 day period, for a limited size trial. Redcentric professional service fees for solution design, deployment and support are negotiable for a trial.|
|Pricing document||View uploaded document|
|Skills Framework for the Information Age rate card||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|