Amazon Redshift is a totally managed, petabyte-scale, cloud information warehouse service. You should use Amazon Redshift to run complicated queries in opposition to petabytes of structured and semi-structured information shortly and effectively, integrating seamlessly with different AWS companies.
Amazon Redshift Serverless helps you run and scale analytics in seconds with out having to arrange, handle, or scale information warehouse infrastructure. It robotically provisions information warehouse capability and intelligently scales the underlying assets to ship quick efficiency for demanding workloads and also you pay just for the compute capability you employ. Moreover, with Amazon Redshift managed storage, you possibly can additional optimize your information warehouse by scaling storage and compute independently and also you pay just for the storage you employ.
Upgrading your information warehouse from Amazon Redshift dense compute (DC2) situations to Amazon Redshift Serverless unlocks these benefits and supplies an enhanced consumer expertise and simplified operations, providing a extra environment friendly, scalable resolution for information analytics.
On this put up, we present you the improve course of from DC2 situations to Amazon Redshift Serverless. We’ll cowl:
- Assessing your present setup and figuring out if an improve is best for you
- Planning and making ready for the improve
- Step-by-step directions for the improve course of
- Put up-upgrade optimization and finest practices
Why improve to Amazon Redshift Serverless
By utilizing Amazon Redshift Serverless, you possibly can run and scale analytics with out managing information warehouse infrastructure. If you improve from DC2 situations to Amazon Redshift Serverless, you get the next advantages:
- Simplified operations: Entry and analyze information without having to arrange, tune, and handle compute clusters.
- Computerized efficiency optimization: Ship persistently excessive efficiency and simplified operations for demanding and risky workloads with computerized scaling and AI pushed scaling and optimization.
- Pay-as-you-go pricing: The versatile pricing construction fees you solely throughout energetic utilization; you pay just for what you employ.
- On-line upkeep: Amazon Redshift Serverless robotically manages system updates and patches with out requiring upkeep home windows, serving to to facilitate seamless operation of your information warehouse.
- Decoupled storage and compute: Management prices by scaling and paying for compute and storage individually with Amazon Redshift managed storage.
- Entry to new capabilities: Use superior options together with information sharing writes, Redshift Streaming Ingestion, zero-ETL, and different capabilities.
Sizing steering
To improve from DC2 to Amazon Redshift Serverless, it’s essential perceive the dimensions equivalency. The next desk reveals urged sizing configurations when upgrading from the DC2 node sort.
Be aware that availability of Redshift Processing Unit (RPU) configurations varies by AWS Area.
| Present node sort | Present variety of nodes | Amazon Redshift Serverless improve |
| DC2.giant | 1–4 | Begin with 4 RPUs |
| DC2.giant | 5–7 | Begin with 8 RPUs |
| DC2.giant | 8–32 | Add 8 RPUs per 8 nodes of DC2.giant |
| DC2.8xlarge | 2–32 | Add 16 RPUs per node (as much as a most of 1,024 RPUs) |
These sizing estimates present a versatile start line tailor-made that can assist you profit from Amazon Redshift Serverless. The perfect configuration to your wants will rely on components resembling your required stability of value and efficiency and the particular latency and throughput necessities of your workload. To additional optimize the sizing primarily based in your particular necessities, you should utilize a number of of following approaches:
- Take a look at your workload beforehand: Earlier than migrating to Amazon Redshift Serverless, consider your workload’s efficiency necessities in a non-production atmosphere. The Amazon Redshift Take a look at Drive utility simplifies this course of by simulating your manufacturing workloads throughout completely different serverless configurations. You should use the outcomes to assist establish the optimum stability between efficiency and value and make knowledgeable choices about your configuration. For step-by-step steering on utilizing the Take a look at Drive utility for DC2 to Serverless upgrades, see the Amazon Redshift Migration Workshop. Operating these efficiency checks earlier than migration lets you establish any obligatory changes to your configuration earlier than deploying to manufacturing
- Monitor in manufacturing: After you’ve deployed your workload, intently monitor the efficiency and useful resource utilization for over a time frame that represents your typical workloads. Primarily based on the noticed metrics, you possibly can then scale the assets up or down as wanted to attain the very best stability of efficiency and value.
- AI-driven scaling and optimization: Think about using Amazon Redshift Serverless with AI-driven scaling and optimization to robotically dimension Amazon Redshift Serverless to your workload wants.
A methodical strategy to sizing validation, combining each pre-production testing and ongoing manufacturing monitoring, helps guarantee your Amazon Redshift Serverless configuration aligns together with your workload.
Improve to Amazon Redshift Serverless
To improve to Amazon Redshift Serverless, you should utilize a snapshot restore to maneuver immediately from Amazon Redshift to Amazon Redshift Serverless, as proven within the following determine. A snapshot restore restores information and objects along with customers and their related permissions, configurations, and schema buildings. By utilizing snapshot restore for migration, you possibly can validate the goal Amazon Redshift Serverless warehouses with out impacting your manufacturing Amazon Redshift DC2 cluster. You may as well use snapshot restore emigrate your Amazon Redshift DC2 workloads to completely different Areas or Availability Zones.
Conditions emigrate utilizing a snapshot restore
- Create an Amazon Redshift Serverless workgroup with a namespace. For extra data, see creating workgroup with a namespace.
- Amazon Redshift Serverless is encrypted by default. Amazon Redshift Serverless additionally helps altering the AWS KMS key for the namespace so you possibly can adhere to your group’s safety insurance policies.
- Confirm that the Amazon Redshift Serverless namespace you’re making an attempt to revive to is hooked up to an Amazon Redshift Serverless workgroup.
- To revive from a provisioned Amazon Redshift cluster to Amazon Redshift Serverless, the AWS Identification and Entry Administration (IAM) consumer or position will need to have the next permissions:
redshift-serverless:RestoreFromSnapshot,CreateNamespace, andCreateWorkgroup. For extra data, see Amazon Redshift Serverless restore.
Improve utilizing the console
Use the next steps within the AWS Administration Console for Amazon Redshift to improve your DC2 cluster to Amazon Redshift Serverless utilizing the snapshot restore methodology.
- On the Redshift console, select Clusters within the navigation pane. Choose your cluster after which select Upkeep.
- Select Create snapshot to create a handbook snapshot of the present Amazon Redshift provisioned cluster.
- Enter a snapshot identifier, choose the snapshot retention interval, after which select Create snapshot.
- Choose the snapshot you need to restore to Amazon Redshift Serverless from the record after which select Restore snapshot and choose Restore to serverless namespace.
- Underneath Choose namespace, choose your goal serverless namespace from the dropdown record after which select Restore.
- The restoration time will differ primarily based in your information quantity.
- After the restoration completes, confirm your information migration by connecting to your Amazon Redshift Serverless workspace utilizing both the Amazon Redshift Question Editor v2 or your most popular SQL consumer.
For extra data, see Making a snapshot of your provisioned cluster.
Improve utilizing the AWS CLI
Use the next steps within the AWS Command Line Interface (AWS CLI) to improve your DC2 cluster to Amazon Redshift Serverless utilizing the snapshot restore methodology.
- Create a snapshot from the supply cluster:
- Confirm that the snapshot exists:
- Restore the snapshot to your Amazon Redshift Serverless namespace:
For extra data, see Restore from cluster snapshot utilizing AWS CLI.
Greatest practices for upgrading to Amazon Redshift Serverless
The next are advisable finest practices when upgrading from Amazon Redshift to Amazon Redshift Serverless.
- Pre-upgrade:
- Put up-upgrade:
- Replace present connections: If you migrate to Amazon Redshift Serverless, a brand new endpoint will probably be created. Replace any present connections to enterprise intelligence and different reporting instruments.
- Observability and monitoring: When you have any information monitoring instruments utilizing methods views, confirm that there aren’t any open or empty transactions. It’s vital as a finest apply to finish transactions. For those who don’t finish or roll again open transactions, Amazon Redshift Serverless will proceed to make use of RPUs for these transactions.
- Entry: When utilizing IAM authentication with
dbUseranddbGroups, your purposes can entry the database utilizing the GetCredentials API. For extra data, see Connecting utilizing IAM. - System views: Evaluate the record of unified system views accessible in Amazon Redshift Serverless.
In case your workloads aren’t fitted to Amazon Redshift Serverless due to their nature or any of the concerns listed in Concerns when utilizing Amazon Redshift Serverless, you possibly can improve to Amazon Redshift RA3 situations by following the RA3 sizing steering.
Price concerns
On this part, we offer data that can assist you perceive and handle your Amazon Redshift Serverless prices.
- You possibly can cut back your serverless computing prices by reserving capability prematurely when you have got predictable utilization patterns.
- Amazon Redshift Serverless robotically adjusts capability primarily based on workload. By setting a most RPU restrict, you possibly can management prices by capping how a lot the system can scale up.
- Amazon Redshift Serverless makes use of RPUs as a compute unit. Whereas it begins with a default of 128 RPUs, you possibly can alter the bottom RPU wherever from 4 to 1,024 RPUs to match your particular workload wants and SLA requirement. For extra data, see Billing for Amazon Redshift Serverless.
- Amazon Redshift Serverless robotically creates restoration factors each half-hour or at any time when 5 GB of information modifications per node happen, whichever occurs first. The minimal interval between restoration factors is quarter-hour. All restoration factors are retained for twenty-four hours by default.
If it’s essential protect backups for an extended interval, you possibly can create handbook backups. Handbook backups will incur further storage prices.
Clear up
To keep away from incurring future fees, delete the Amazon Redshift Serverless occasion or provisioned information warehouse cluster created as a part of the prerequisite steps. For extra data, see Deleting a workgroup and Shutting down and deleting a cluster.
Conclusion
On this put up, we mentioned the advantages of upgrading Amazon Redshift DC2 situations to Amazon Redshift Serverless, along with the assorted choices for upgrading and a few finest practices. It’s important to find out the goal Amazon Redshift Serverless configuration and validate it utilizing Amazon Redshift Take a look at Drive utility in take a look at and improvement environments earlier than upgrading.
Get began upgrading to Amazon Redshift Serverless right now by implementing the steering on this put up. When you have questions or want help, contact AWS Help forarchitectural and design steering, along with help for proofs of idea and implementation.
Concerning the authors
