Sagemaker example of "deploy your own model"

[jckuester]

Please review only the last commit of this PR, which contains the example itself (the other commits are from rebasing the referenced PRs below, which contain the new SageMaker resources).

This example shows how to use the three new SageMaker resources

• resource_aws_sagemaker_model (New Resource: aws_sagemaker_model #2478),
• resource_aws_sagemaker_endpoint_configuration (New Resource: aws_sagemaker_endpoint_configuration #2477), and
• resource_aws_sagemaker_endpoint (New Resource: aws_sagemaker_endpoint #2479)

to deploy your own model algorithm container.

This PR can only be merged once the referenced PRs above are merged, as this example depends on the three new resources.

[radeksimko]

Hi @jckuester
I appreciate this is still WIP - just so you know we always prefer 1 resource per PR to keep diff small and easier to review. 😉

Just let us know when it's ready for review and we can take a look.

[jckuester]

Hi @radeksimko
Thanks. I know - I hope I've read all of the developer guidelines :-) This PR is the last of 4 PRs that all depend on each other. The first three contain the new sagemaker resources and this last one an example (I rebased the branch of this PR on top of the other ones, so I can get the example working).

Actually, the first PR of the series is now ready to review (#2478). I am looking fwd to your feedback :)

[bflad]

Hey @jckuester 👋 Thanks for submitting this -- since we merged a bunch of the required resources here with changes, this PR is showing conflicts with pretty much every previous file and requires a rebase. If you are interested in submitting this, please re-submit it with only the last commit against master so it can get reviewed. Thanks again.

[jckuester]

Ok, @bflad. Resubmitted and tested that the example is still working: #9948

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!