Add Migration Assistant Type Mapping documentation

[AndreKurait]

Description

Add Migration Assistant Type Mapping documentation

Issues Resolved

MIGRATIONS-2385

Version

all (Migration Assistant 2.1.5+)

Frontend features

n/a

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

[peternied]

Thanks for writing this up.

Lets consider reframing this documentation for a user they doesn't know if they use this deprecated feature, this kind of jumps into 'what to do' without enough context for a user to know if they are impacted and why they should make different choices.

[Naarcha-AWS]

@AndreKurait: Let me know once you've implemented @peternied and @mikaylathompson's feedback and I'll begin the writer review process.

[gregschohn]

I'd recommend two solutions - the first would be to pick up a bit more information from the README file for the transformer.

The second would be to simplify the deployment. Redeploying infrastructure isn't very appealing. Instead, we could

1. deploy a new EFS volume (for any deployment configuration) for transformation configurations;
2. Add documentation to give the customer a command to add a configuration file (ssm copy, vi /sharedTransformConfigs/...);
3. have the container entrypoints check for that config file for type mappings sanitization and just add the arguments;
4. Add documentation so to indicate how to run/restart commands

[AndreKurait]

@gregschohn

I'd recommend two solutions - the first would be to pick up a bit more information from the README file for the transformer.

Let me know what additional information you would like me to add here

The second would be to simplify the deployment. Redeploying infrastructure isn't very appealing. Instead, we could

1. deploy a new EFS volume (for any deployment configuration) for transformation configurations;
2. Add documentation to give the customer a command to add a configuration file (ssm copy, vi /sharedTransformConfigs/...);
3. have the container entrypoints check for that config file for type mappings sanitization and just add the arguments;
4. Add documentation so to indicate how to run/restart commands

Tracking this in https://opensearch.atlassian.net/browse/MIGRATIONS-2410

[AndreKurait]

@Naarcha-AWS Ready for review

[peternied]

I know there are still some outstanding comment threads around technical implementation, but I think this is a great starting point that we can refine in future releases. Thanks for iterating on this one @AndreKurait