Next steps - AWS Prescriptive Guidance

Next steps

We recommend that you consider the following next steps:

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

  2. 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 in the Teradata documentation.

  3. 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 in the Teradata documentation.

  4. Assess the costs of running Teradata VantageCloud Enterprise on AWS. For more information, see Teradata VantageCloud Pricing in the Teradata documentation.

  5. Make sure that you meet all the prerequisites for a migration based on the Prerequisites section of this guide. Teradata makes a commercially reasonable effort to make Teradata Vantage available on AWS systems 24/7/365. Teradata targets an SLA (excluding planned downtime) of 99.9 percent measured monthly. For operating model and services options, see Teradata Vantage on AWS in the Teradata documentation.

  6. Define your security requirements. For more information on security compliance, see Cloud Data Security as-a-service in the Teradata documentation.