AWS Snowball Edge is a 100TB data transfer device with on-board storage and compute. AWS Snowball Edge is used to move large amounts of data into and out of AWS, as a temporary storage tier for large local data sets, or to support independent local workloads in remote locations. https://aws.amazon.com/documentation/snowball/
- Suits OFFICIAL (IL2) and OFFICIAL-SENSITIVE / HIGH workloads (IL3)
- NCSC Cloud Security Principles aligned, Security Cleared (SC) staff available
- Connectivity options: N3, HSCN, PSN, Police (ex-PNN), Janet, RLi, others
- Available in the UK, EU and internationally
- Deploy into automated Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) architectures
- Transports multiple terabytes of data into/out of AWS
- 256-bit encryption, plus industry standard Trusted Platform Module (TPM)
- Jobs are created direct from the AWS Management Console
- Analyse data streams or process data locally using AWS Lambda
- Faster, more cost-effective than internet transfer for large migrations
- Excellent for rapid retrieval of data in DR scenarios
- Secure, efficient, cost-effective data transfer when decommissioning data centres
- Highly effective mechanism for sharing large amounts of data
- Up to one-fifth cheaper than internet transfer
- Perfect for customers in areas with poor internet connections
- Use as an alternative to expensive network infrastructure upgrades
- Increase durability and capacity by using the Clustering feature
- Uses E Ink shipping label for tracking
£185.19 per unit
Amazon Web Services
+44 (0) 7825112477
|Email or online ticketing support||Email or online ticketing|
|Support response times||
AWS Support case response time depends on severity. The support response times for Developer, Business and Enterprise Support tiers are listed below:
General guidance cases < 24 business hours; system impaired cases < 12 business hours.
General guidance cases < 24 hours; system impaired cases < 12 hours; production system impaired cases < 4 hours; production system down cases
< 1 hour.
General guidance cases < 24 hours; system impaired cases < 12 hours; production system impaired cases < 4 hours; production system down cases < 1 hour; business-critical system down cases < 15 minutes
|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||Yes, at an extra cost|
|Web chat support availability||24 hours, 7 days a week|
|Web chat support accessibility standard||None or don’t know|
|How the web chat support 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 chat accessibility testing||None|
|Onsite support||Yes, at extra cost|
24/7 customer service, support forums, 4 Core “Trusted Adviser” checks, personal health dashboard. No TAM. Free
As above + business hours access to technical/architural Cloud Support Associates via email (one primary contact). No TAM. 3%x monthly AWS usage.
As above + 24/7 access to Cloud Support Engineers via email, chat and phone for unlimited contacts; architecture, 3rd party software and programmatic case management support. TAM. Greater of $100 or spend-dependent percentage (pm).
As above, plus architectural review, operations support, training, assigned concierge, proactive guidance, TAM. Greater of $15,000 or spend-dependent percentage (pm).
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||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.|
|Other documentation formats||Kindle|
|End-of-contract data extraction||This service is used to import or export large amounts of data into Amazon S3.|
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.
Buyers pay for the services they use to the point of account termination. Please see the AWS UK G-Cloud 10 Pricing Document affiliated with this Service in the Digital Marketplace.
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.|
|What users can and can't do using the API||All 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 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||No|
|Supplier type||Not a reseller|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Developed Vetting (DV)|
|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. (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||
|Equipment disposal approach||In-house destruction process|
Backup and recovery
|Backup and recovery||No|
|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 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
AWS currently provides SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, SLAs are best reviewed directly on our 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
|Other user authentication||
AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. No actions are permissible without authentication. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost.
AWS CoudTrail allows you to log, continously monitor and retain events related to API calls across your AWS infrastructure.
|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||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||15/12/2017|
|What the ISO/IEC 27001 doesn’t cover||N/A|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||15/12/2017|
|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||25/1/2018|
|What the PCI DSS doesn’t cover||N/A|
|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.
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/.
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||
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 incidents, based on AWS Service/Security Team-set thresholds.
Requests to AWS KMS are logged/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 to the customer after turning on AWS CloudTrail in their account.
|Incident management type||Supplier-defined controls|
|Incident management approach||
AWS 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 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.
|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||£185.19 per unit|
|Discount for educational organisations||No|
|Free trial available||No|
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|