transACT AWS Redshift
Amazon Redshift is a fast, fully managed, petabyte-scale data warehouse service that makes it simple and cost-effective to efficiently analyse all your data using your existing business intelligence tools.
Features
- Suits OFFICIAL
- Available in the London Region, EU and internationally
- NCSC Cloud Security Principles aligned, Security Cleared (SC) staff available
- Connectivity options: N3, HSCN, PSN, Police (ex-PNN), Janet, RLi, others
- Deploy into automated Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) architectures
- Fast, simple, cost-effective, fully-managed data warehousing
- Columnular storage parallelizes queries across multiple nodes
- Custom JDBC/ODBC drivers for download from Connect Client console tab
- Permits use of a wide range of familiar SQL clients
- Capacity to use s standard PostgreSQL JDBC and ODBC drivers
Benefits
- Integrated role-based access control across all AWS services (IAM)
- 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)
- Allows you to automate most of the common administrative tasks
- Automates provisioning, configuring and monitoring a cloud data warehouse
- Backups to Amazon S3 are continuous, incremental and automatic
- Enabling disaster recovery across regions takes just a few clicks
- Directly run queries against exabytes of unstructured data (Redshift Spectrum)
Pricing
£0.00 a unit
Service documents
Request an accessible format
Framework
G-Cloud 13
Service ID
7 9 9 8 7 0 4 6 7 5 8 7 8 8 5
Contact
Transact Technology Solutions
Stuart Whitman
Telephone: 07725 367728
Email: stuart.whitman@transactts.co.uk
Service scope
- Service constraints
- N/A
- System requirements
- N/A
User support
- 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:
Developer:
General guidance cases < 24 business hours; system impaired cases < 12 business hours.
Business:
General guidance cases < 24 hours; system impaired cases < 12 hours; production system impaired cases < 4 hours; production system down cases
< 1 hour.
Enterprise:
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
Information: https://aws.amazon.com/premiumsupport/compare-plans/ - User can manage status and priority of support tickets
- Yes
- Online ticketing support accessibility
- None or don’t know
- Phone support
- Yes
- 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
- Support levels
-
Basic
24/7 customer service, support forums, 4 Core “Trusted Adviser” checks, personal health dashboard. No TAM. Free
Developer:
As above + business hours access to technical/architural Cloud Support Associates via email (one primary contact). No TAM. 3%x monthly AWS usage.
Business:
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).
Enterprise
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.
- Service documentation
- Yes
- Documentation formats
-
- HTML
- Other
- Other documentation formats
- Kindle
- End-of-contract data extraction
- Data may be copied out 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.
Buyers pay for the services they use to the point of account termination. Please see the AWS UK G-Cloud 11 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
- 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
-
- SDKs for Python
- Ruby
- PHP
- JavaScript
- Java
- .NET
- 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
- Manual
- 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
- Memory
- Network
- Number of active instances
- Other
- Other metrics
-
- Health metrics
- Maintenance Metrics
- Latency metrics
- Query metrics
- Replication metrics
- Reporting types
-
- API access
- Real-time dashboards
Resellers
- Supplier type
- Not a reseller
Staff security
- Staff security clearance
- Other security clearance
- Government security clearance
- Up to Developed Vetting (DV)
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
-
- Block
- Volume
- 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
- Bonded fibre optic connections
- Legacy SSL and TLS (under version 1.2)
- 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 our website via the link below: https://aws.amazon.com/legal/service-level-agreements/
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’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, continuously 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 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
- Other
- Description of management access authentication
- AWS controls access to systems through authentication that requires a unique user ID and password. AWS systems don't allow actions to be performed without identification or authentication. Remote access requires multi-factor authentication. All remote administrative access attempts are logged and reviewed by the Security team for unauthorized attempts or suspicious activity. Incident response procedure is triggered in case of suspicious activity. AWS employs the concept of least privilege, allowing only the necessary access for users to accomplish their job. User access to AWS systems requires documented approval from authorized personnel.
- 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
- 05/11/2019
- What the ISO/IEC 27001 doesn’t cover
- N/A
- ISO 28000:2007 certification
- No
- CSA STAR certification
- Yes
- CSA STAR accreditation date
- 05/11/2019
- 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
- 13/12/2019
- 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 27017
- ISO 27018
- SOC 1/2/3
Security governance
- Named board-level person responsible for service security
- Yes
- Security governance certified
- Yes
- Security governance standards
-
- ISO/IEC 27001
- Other
- 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.
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/.
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 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 visible to customers 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.
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
transACT are committed to understanding the impact of our operations and setting ambitious sustainability goals across our business. We believe embracing our social and environmental responsibility will bring a sustained, collective value to our customers, partners, and employees. We understand that making the right choices now are for the betterment of our people and planet. transACT will implement real business changes to reduce their Scope 1, 2, and 3 carbon emissions to achieve net-zero carbon emissions by 2040. We are consulting the relevant third-party organisations to accurately collate and report our carbon footprint baseline, and to implement sustained, creditable carbon offsetting. - Covid-19 recovery
-
Covid-19 recovery
transACT implemented several improvements to the workplace conditions whilst transitioning out of COVID-19 restrictions. Staff were encouraged to work from home, if possible, if not social distancing and physical barriers was implemented in all our offices. In supporting the transition for our partners and clients, we utilised our digital workplace department for businesses to manage and improve their return-to-work process with innovative new technologies, these included desk booking systems, visitor management and hybrid meeting rooms. - Equal opportunity
-
Equal opportunity
transACT work closely with Amazon Web Services (AWS) as re/Start Employer. AWS re/Start is a full-time, classroom-based skills development and training program that prepares individuals for careers in the cloud and connects them to potential employers. A technology background is not required to apply. The program is focused on unemployed or underemployed individuals, including military veterans, their families, and young people. transACT additional support individual endeavours, allowing our staff to develop new skills relevant and of interested to them, we will support them with the resources and funding they need.
transACT have taken to initiative to produce a modern slavery statement. This document outlines the practises and policies we are committed to adhering to, ensuring that there is no modern slavery or human trafficking in or associated to our business or supply chain. Furthermore, the actions we’re talking to allow for clear tracking of our diligence through several KPI’s, supported by ongoing staff training.
Pricing
- Price
- £0.00 a unit
- Discount for educational organisations
- No
- Free trial available
- Yes
- Description of free trial
-
Two-month free trial
New customers get 750 free DC2.Large hours per month for 2 months. Conditions apply. - Link to free trial
- https://aws.amazon.com/free