Next steps

We recommend that you consider the following next steps:

• Learn how organizations use Teradata Vantage to connect and analyze data across their entire ecosystems, including data lakes, object stores, and cloud services.

• Identify the migration workloads in your on-premises environments or other cloud environments. Then, review your deployment options and identify your destination environment. For more information, see Teradata Vantage on AWS on the Teradata website.

• Choose either a rehost (that is, lift and shift) or replatform (that is, make some workload changes) migration strategy. For more information, see Lift-and-shift Cloud Migration and A Guide to Cloud Migration on the Teradata website.

• Assess the costs of running Teradata VantageCloud on AWS. For more information, see Teradata VantageCloud Pricing on the Teradata website.

• Make sure that you meet all the prerequisites for a migration based on the Prerequisites section of this guide.

Note

Teradata makes a commercially reasonable effort to make Teradata Vantage available on AWSall day, every day. Teradata targets an service-level agreement (SLA) of 99.9 percent (excluding planned downtime), measured monthly. For operating model and services options, see Teradata Vantage on AWS on the Teradata website.