Securely assess database schema migrations using AWS SCT, Amazon RDS for Oracle, and AWS Secrets Manager

<section class="blog-post-content"><a href="https://aws.amazon.com/blogs/database/database-migration-what-do-you-need-to-know-before-you-start/" target="_blank" rel="noopener noreferrer">Database migration</a> is a multi-step process comprised of assess, mobilize, and modernize phases with different tools and technologies involved. You can use tools such as <a href="https://aws.amazon.com/dms/schema-conversion-tool/" target="_blank" rel="noopener noreferrer">AWS Schema Conversion Tool</a> (AWS SCT) and <a href="https://aws.amazon.com/dms" target="_blank" rel="noopener noreferrer">AWS Database Migration Service</a> (AWS DMS) to accelerate each of these phases.An important part of AWS SCT is the report that it generates to help you convert your schema. When you want to determine the best target direction for your overall environment that is comprised of multiple servers, the easiest way is to create a multiserver assessment report.A <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_AssessmentReport.Multiserver.html" target="_blank" rel="noopener noreferrer">multiserver assessment report</a> evaluates multiple servers based on input that you provide for each schema definition that you want to assess. Your schema definition contains database server connection parameters and the full name of each schema. After assessing each schema, AWS SCT produces a summary and aggregated assessment report for database migration across the selected servers.When running a multiserver assessment report, it is not recommended to store hardcoded credentials as a plain text in connection parameters, as anyone with access to the connections file would be able to read those secrets. Additionally, it is generally required that you open encrypted connections to a database to protect server-client communications and authentication using Secure Sockets Layer (SSL) certificates. <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_ReleaseNotes.html#CHAP_ReleaseNotes.660" target="_blank" rel="noopener noreferrer">AWS SCT build 660</a> includes support for <a href="https://aws.amazon.com/secrets-manager/" target="_blank" rel="noopener noreferrer">AWS Secrets Manager</a> and SSL features.In this post, we demonstrate how you can create a multiserver assessment report using an <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.Oracle.html" target="_blank" rel="noopener noreferrer">Oracle Database as a source</a> for AWS SCT with integration of Secrets Manager for storing the database credentials and SSL to open encrypted connections to the source.<h2>Solution overview</h2>Our use case for this post involves AWS SCT connecting to an <a href="https://aws.amazon.com/rds/oracle/" target="_blank" rel="noopener noreferrer">Amazon Relational Database Service (Amazon RDS) for Oracle</a> database enabled with SSL encryption using database credentials that you store in Secrets Manager for generating a multiserver assessment report to a target <a href="https://aws.amazon.com/rds/aurora/" target="_blank" rel="noopener noreferrer">Amazon Aurora PostgreSQL-Compatible Edition</a> database. Secrets Manager and SSL features work independently; we show a common use case to demonstrate the integration of both these features with AWS SCT.At a high level, the solution steps are as follows:<ol><li>Enable SSL encryption for an RDS for Oracle DB instance by adding the Oracle <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.Options.SSL.html#Appendix.Oracle.Options.SSL.OptionGroup" target="_blank" rel="noopener noreferrer">SSL option to the option group</a> associated with an Oracle DB instance.</li><li>Download, install, and launch the <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html" target="_blank" rel="noopener noreferrer">latest version of AWS SCT</a>.</li><li>Store database credentials in Secrets Manager.</li><li>Configure <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html#CHAP_Installing.JDBCDrivers" target="_blank" rel="noopener noreferrer">JDBC drivers</a> in AWS SCT global settings.</li><li>Set up AWS SCT specifications to update global settings with AWS service profiles to access Secrets Manager and the <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.Encrypt.RDS.html" target="_blank" rel="noopener noreferrer">SSL trust store to open encrypted connections</a> to the source database.</li><li>Create a multiserver assessment report for database migration using the AWS SCT GUI.</li><li>Create a multiserver assessment report for database migration using the AWS SCT CLI.</li></ol>The following diagram illustrates the architecture.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image001.jpg"><img class="alignnone size-full wp-image-24654" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image001.jpg" alt="" width="681" height="501" /></a>The architecture consists of the following components:<ol><li>An RDS for Oracle DB instance with SSL enabled</li><li>Secrets Manager to store database credentials</li><li>AWS SCT for generating the multiserver assessment report</li><li>A sample AWS SCT target engine (for this post, an Aurora PostgreSQL database)</li></ol><h2>Prerequisites</h2>To implement this solution, you must have an <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.Oracle.html" target="_blank" rel="noopener noreferrer">RDS for Oracle DB instance</a> with the <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Concepts.database-versions.html" target="_blank" rel="noopener noreferrer">latest version</a> inside a VPC. We use <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Concepts.database-versions.html#Oracle.Concepts.FeatureSupport.19c" target="_blank" rel="noopener noreferrer">Oracle Database 19c (19.0.0.0) on Amazon RDS</a> for this demonstration.<h2>Enable SSL encryption for an RDS for Oracle DB instance</h2>Amazon RDS supports SSL encryption for Oracle DB instances. With SSL, you can encrypt a connection between your AWS SCT application client and your Oracle DB instance. To enable SSL encryption for an Oracle DB instance, add the Oracle SSL option to the option group associated with the DB instance. Amazon RDS uses a second port, as required by Oracle, for SSL connections. Doing this allows both clear text and SSL-encrypted communication to occur at the same time between a DB instance and an Oracle client. For example, you can use the port with clear text communication to communicate with other resources inside a VPC while using the port with SSL-encrypted communication to communicate with resources outside the VPC.SSL/TLS connections provide one layer of security by encrypting data that moves between your client and a DB instance. Using a server certificate provides an extra layer of security by validating that the connection is being made to an RDS DB instance. It does so by checking the server certificate that is automatically installed on all DB instances that you provision.<h3>Add the SSL option</h3>To use SSL, your RDS for Oracle DB instance must be associated with an option group that includes the <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.Options.SSL.html#Appendix.Oracle.Options.SSL.OptionGroup" target="_blank" rel="noopener noreferrer">SSL option</a>.<ol><li><a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithOptionGroups.html#USER_WorkingWithOptionGroups.Create" target="_blank" rel="noopener noreferrer">Create a new option group</a> or identify an existing option group to which you can add the SSL option.</li><li>Add the SSL option to the option group.If you want to use only FIPS-verified cipher suites for SSL connections, set the option <code>FIPS.SSLFIPS_140</code> to <code>TRUE</code>. For information about the FIPS standard, see <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.Options.SSL.html#Appendix.Oracle.Options.SSL.FIPS" target="_blank" rel="noopener noreferrer">FIPS support</a>.For information about adding an option to an option group, see <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithOptionGroups.html#USER_WorkingWithOptionGroups.AddOption" target="_blank" rel="noopener noreferrer">Adding an option to an option group</a>.</li><li>Modify an Oracle DB instance to associate the option group with it.</li></ol>For information about creating a DB instance, see <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_CreateDBInstance.html" target="_blank" rel="noopener noreferrer">Creating an Amazon RDS DB instance</a>. For information about modifying a DB instance, see <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html" target="_blank" rel="noopener noreferrer">Modifying an Amazon RDS DB instance</a>.<h3>Set up an SSL connection over JDBC</h3>To use an SSL connection over JDBC, you must create a keystore, and trust the Amazon RDS root CA certificate.<ol><li>To create the <a href="https://docs.oracle.com/cd/E19509-01/820-3503/ggfen/index.html" target="_blank" rel="noopener noreferrer">keystore in JKS format</a>, use the following command. It’s recommended to use the default keystore and run from <a href="http://aws.amazon.com/ec2" target="_blank" rel="noopener noreferrer">Amazon Elastic Compute Cloud</a> (Amazon EC2).You get the following output:Next, take the following steps to trust the Amazon RDS root CA certificate.</li><li><a href="https://s3.amazonaws.com/rds-downloads/rds-ca-2019-root.pem" target="_blank" rel="noopener noreferrer">Download the root certificate</a> that works for all AWS Regions and put the file in a directory.You get the following output:</li><li>Convert the certificate to .der format using the following command (replace the file name with the one you downloaded):You get the following output:</li><li>Import the certificate into the keystore using the following command:You get the following output:</li><li>Confirm that the keystore was created successfully:</li><li>Enter the keystore password when you’re prompted for it.</li></ol>You get the following output:For step-by-step instructions, refer to <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.Options.SSL.html#Appendix.Oracle.Options.SSL.JDBC" target="_blank" rel="noopener noreferrer">Setting up an SSL connection over JDBC</a> and test using the code example.<h2>Download, install, and launch the latest version of AWS SCT</h2>You must download and install AWS SCT either on your local computer, a server in your data center, or an <a href="http://aws.amazon.com/ec2" target="_blank" rel="noopener noreferrer">Amazon Elastic Compute Cloud</a> (Amazon EC2) instance. Make sure your AWS SCT version is the latest one or with <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_ReleaseNotes.html#CHAP_ReleaseNotes.660" target="_blank" rel="noopener noreferrer">build #1.0.660</a> or higher. For step-by-step instructions, refer to <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html" target="_blank" rel="noopener noreferrer">Installing, verifying, and updating AWS SCT</a>.In our use case, we installed AWS SCT on a Microsoft Windows instance on <a href="https://aws.amazon.com/pm/workspaces" target="_blank" rel="noopener noreferrer">Amazon Workspaces</a>.<h2>Store database credentials in Secrets Manager</h2>AWS SCT can use database credentials that you store in Secrets Manager. You can fill in all the values in the database connection dialog box from Secrets Manager. To use Secrets Manager, make sure that you store AWS profiles in the AWS SCT. For more information about using Secrets Manager, refer to the <a href="https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html" target="_blank" rel="noopener noreferrer">AWS Secrets Manager User Guide</a>.On the Secrets Manager console, create a new secret to store the database credentials. AWS SCT supports secrets that have the following structure.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image003.png"><img class="alignnone size-full wp-image-24655" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image003.png" alt="" width="1339" height="438" /></a>In this structure, the <code>username</code> and <code>password</code> values are required, and all other values are optional. Make sure that the values that you store in Secrets Manager include all database credentials.For more information about storing AWS profiles, see <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_UserInterface.html#CHAP_UserInterface.Profiles" target="_blank" rel="noopener noreferrer">Storing AWS service profiles in the AWS SCT</a>.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image005.png"><img class="alignnone wp-image-24656 size-full" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image005.png" alt="" width="1069" height="633" /></a>You can also set the default profile for an AWS SCT project. Doing this associates the AWS credentials stored in the profile with the project.<h2>Configure JDBC drivers in AWS SCT global settings</h2>AWS SCT requires JDBC drivers to connect to your source and target databases. To configure the driver path in AWS SCT, complete the following steps:<ol><li><a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html#CHAP_Installing.JDBCDrivers" target="_blank" rel="noopener noreferrer">Download and install JDBC drivers</a>.</li><li>Navigate to the global settings on the Settings page.</li><li>Choose Drivers in the navigation pane, and enter the file path to the JDBC driver for your source and target database engines.</li></ol>For this post, I added an Oracle driver.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image007.png"><img class="alignnone size-full wp-image-24657" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image007.png" alt="" width="700" height="153" /></a>Make sure you “Test Connection” to validate the credentials stored in Secrets Manager to verify that AWS SCT can connect to your database. For detailed steps, refer to <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_UserInterface.html#CHAP_UserInterface.SecretsManager" target="_blank" rel="noopener noreferrer">Using AWS Secrets Manager</a>.<h2>Set up AWS SCT specifications to update global settings with an SSL trust store</h2>AWS SCT requires SSL settings to connect to your source database. To <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.Encrypt.RDS.html" target="_blank" rel="noopener noreferrer">configure a trust store in AWS SCT</a>, complete the following steps:<ol><li>Navigate to the global settings on the Settings page.</li><li>Choose Security in the navigation pane, and add the trust stores by choosing Select existing trust store.</li><li>Provide values for Trust store name, File path, and Trust store password.</li></ol>For this post, I added the trust store that was created in the previous steps.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image009.png"><img class="alignnone size-full wp-image-24658" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image009.png" alt="" width="1221" height="664" /></a><h2>Create a multiserver assessment report for database migration using the AWS SCT GUI</h2>To determine the best target direction for your overall environment, create a multiserver assessment report. You can use AWS SCT to create a multiserver assessment report for your source Oracle database and target Aurora PostgreSQL database. This solution also supports <a href="https://aws.amazon.com/rds/aurora/mysql-features/" target="_blank" rel="noopener noreferrer">Amazon Aurora MySQL-Compatible Edition</a>.You don’t need to create a new project in AWS SCT to perform a multiserver assessment. Before you get started, make sure that you have prepared a CSV file with database connection parameters as detailed below. Also, make sure that you have installed all required database drivers and set the location of the drivers in the AWS SCT settings. For more information, see <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Installing.html#CHAP_Installing.JDBCDrivers" target="_blank" rel="noopener noreferrer">Installing the required database drivers</a>.<ol><li>In AWS SCT, choose File, New multiserver assessment.The New multiserver assessment dialog box opens.</li><li>Choose Download a connections file example to download an empty template of a CSV file with database connection parameters.</li></ol>To provide connection parameters as input for multiserver assessment report, use a CSV file as shown in the following example.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image011.png"><img class="alignnone size-full wp-image-24659" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/09/20/DBBLOG-2316-image011.png" alt="" width="602" height="274" /></a>You can create a new CSV file or download a template for a CSV file from AWS SCT and fill in the required information. Make sure that the first row of your CSV file reflects the header with column names.The following are header columns related to SSL and Secrets Manager:<ul><li>Use SSL – If you use SSL to connect to your source database, enter <code>true</code>.</li><li>Trust store – The trust store to use for your SSL connection.</li><li>Key store – The keystore to use for your SSL connection.</li><li>SSL authentication – If you use SSL authentication by certificate, enter <code>true</code>.</li><li>Secret Manager Key – The name of the secret that stores your database credentials in Secrets Manager. To use Secrets Manager, make sure that you store AWS profiles in the AWS SCT. For more information, see <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_UserInterface.html#CHAP_UserInterface.SecretsManager" target="_blank" rel="noopener noreferrer">Using AWS Secrets Manager</a>.</li></ul>For a detailed description for each of the header columns, refer to <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_AssessmentReport.Multiserver.html#CHAP_AssessmentReport.Multiserver.Input" target="_blank" rel="noopener noreferrer">preparing an input CSV file</a>.<div class="hide-language"><pre class="lang-code">Name,Description,Server IP,Port,Service Name,SID,Source Engine,Schema Names,Login,Password,Target Engines,Secret Manager Key,Use Windows Authentication,Use SSL,Trust store,Key store,SSL authenticationOracle_SSL_2484,Test RDS Instance,dmaf-test-instance.xxxxxrvgexxx.us-east-1.rds.amazonaws.com,2484,DMAFDB,,ORACLE,DMS_SAMPLE,dms_sample,dms_sample,AURORA_POSTGRESQL;AURORA_MYSQL,,,true,client-trust-store-key,,falseOracle_TCP_1521,Demo RDS Instance,dmaf-test-instance.xxxxxrvgexxx.us-east-1.rds.amazonaws.com,1521,DMAFDB,,ORACLE,DMS_SAMPLE,dms_sample,dms_sample,AURORA_POSTGRESQL;AURORA_MYSQL,,,,,,Oracle_SSL_SM_2484,Sample RDS Instance,,,DMAFDB,,ORACLE,DMS_SAMPLE,,,AURORA_POSTGRESQL;AURORA_MYSQL,ALL.SOURCE.ORACLE_19,,true,client-trust-store-key,,false</pre></div>The preceding example uses a semicolon to separate the two target database migration platforms. Also, three use cases are set up in the preceding example with <code>Name</code>:<ul><li>Oracle_SSL_2484 – Uses SSL trust store <code>client-trust-store-key</code> to open encrypted connections to the source database on port 2484</li><li>Oracle_TCP_1521 – Opens clear text connections to source database on port 1521</li><li>Oracle_SSL_SM_2484 – Uses SSL trust store <code>client-trust-store-key</code> to open encrypted connections to source database and retrieve database credentials, server, and port details from the Secrets Manager secret <code>ALL.SOURCE.ORACLE_19</code></li></ul><ol start="3"><li>Enter values for Project name, Location (to store reports), and Connections file (a CSV file).</li><li>Choose Run.</li><li>When the multiserver assessment report generation is complete, choose Open Report to view the aggregated summary assessment report.</li></ol>The multiserver assessment generates two types of reports:<ul><li>An aggregated report of all source databases</li><li>A detailed assessment report of target databases for each schema name in a source database</li></ul>Reports are stored in the directory that you chose for Location in the New multiserver assessment dialog box.To access the detailed reports, you can navigate the subdirectories, which are organized by source database, schema name, and target database engine, as shown in the following example from the CMD prompt:<h2>Create a multiserver assessment report for database migration using the AWS SCT CLI</h2>To use the AWS SCT CLI to create a multiserver assessment report, you must create an AWS SCT CLI input file with an <code>.scts</code> extension. This file contains the AWS SCT CLI commands and required configuration:<ul><li><code>SetGlobalSettings</code> gives the settings for Oracle driver file path</li><li><code>CreateAggregatedReport</code> gives the settings of the project directory path, project name, and connections file path</li></ul>The following snippet shows the implementation:The <code>.scts</code> input file includes all the mentioned functions, which can be called with a single command:You can configure AWS SCT with different memory performance settings. Increasing memory speeds up the performance of your conversion. For more information, refer to <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_BestPractices.html#CHAP_BestPractices.JVM" target="_blank" rel="noopener noreferrer">Configuring additional memory</a>.You get the following output:<h2>Clean up</h2>To avoid incurring future charges, clean up the manually created resources you made as part of this post.Delete the secrets in Secrets Manager that are used to store database connection details. For instructions, refer to <a href="https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_delete-secret.html" target="_blank" rel="noopener noreferrer">Delete a secret</a>.<h2>Additional references</h2>The post <a href="https://aws.amazon.com/blogs/database/generate-an-assessment-report-for-a-fleet-of-database-servers-using-the-aws-sct-multiserver-assessor/" target="_blank" rel="noopener noreferrer">Generate an assessment report for a fleet of database servers using the AWS SCT multiserver assessor</a> demonstrates on how to configure the <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_AssessmentReport.Multiserver.html" target="_blank" rel="noopener noreferrer">AWS SCT multiserver assessor</a> to generate an aggregated report.The post <a href="https://aws.amazon.com/blogs/database/convert-database-schemas-and-application-sql-using-the-aws-schema-conversion-tool-cli/" target="_blank" rel="noopener noreferrer">Convert database schemas and application SQL using the AWS Schema Conversion Tool CLI</a> demonstrates on how to use the AWS SCT CLI to convert database schema object code, application SQL, and PL/SQL code into PSQL in application files, as part of the migration process from an Oracle database hosted on Amazon EC2 to Aurora PostgreSQL.<h2>Conclusion</h2>In this post, we demonstrated how to create a multiserver assessment report using an Oracle Database as a source for AWS SCT and integrate Secrets Manager. We enabled <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.Encrypt.RDS.html" target="_blank" rel="noopener noreferrer">SSL encryption for an RDS for Oracle DB instance</a> by adding the Oracle SSL option to the RDS option group, then we downloaded and installed AWS SCT, stored and retrieved the database credentials from Secrets Manager, and configured AWS SCT to update global settings. Finally, we <a href="https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_AssessmentReport.Multiserver.html#CHAP_AssessmentReport.Multiserver.Input" target="_blank" rel="noopener noreferrer">generated a multiserver assessment report</a> for database migration using the AWS SCT GUI and AWS SCT CLI options.Leave your thoughts or questions in the comments section.<h3>About the authors</h3><a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/04/27/bhanu.jpg"><img class="wp-image-21364 size-full alignleft" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/04/27/bhanu.jpg" alt="" width="100" height="133" /></a>Bhanu Ganesh Gudivada is a Database Consultant with the Professional Services team at AWS based out of Hyderabad, India and specializes in database migrations. He is helping and enabling customers to build high-available, cost-effective database solutions and migrate their commercial engines to AWS cloud. Curious to learn and implement new technologies around the databases and orchestrate migrations through automation.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/03/14/Jeevan-Shetty.jpg"><img class="size-full wp-image-20542 alignleft" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/03/14/Jeevan-Shetty.jpg" alt="" width="100" height="133" /></a>Jeevan Shetty is a Consultant with the AWS Professional Services Team. He has been supporting and enabling customers to migrate their database from OnPrem data center to AWS cloud and also in migration from commercial database engines to open source database in Amazon.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/04/26/sanadapa.jpg"><img class="wp-image-21352 size-full alignleft" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/04/26/sanadapa.jpg" alt="" width="100" height="133" /></a>Santhosh Kumar Adapa is a Database Consultant with the Professional Services team at AWS. He works as a database migration specialist to help Amazon customers in design and implementing scalable, secure, performant, and robust database solutions in the cloud.<a href="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/01/18/bkhari.jpg"><img class="wp-image-19338 size-full alignleft" src="https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2022/01/18/bkhari.jpg" alt="" width="100" height="133" /></a>HariKrishna Boorgadda is a Senior Consultant with the Professional Services team at Amazon Web Services. He focuses on database migrations to AWS and works with customers to design and implement Amazon RDS and Aurora architectures.</section>

Fish AI Reader

FishAI

联系邮箱 441953276@qq.com

相关标签