Add AsyncInferenceConfig block to aws_sagemaker_endpoint_configuration

[zachchurchill]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS announced on Aug. 20, 2021 that SageMaker Endpoints can now be called asynchronously via a new parameter block when creating Endpoint Configurations, namely the AsyncInferenceConfig block. This additional block will signal to the AWS infrastructure that the Endpoint will only take asynchronous invocations, so no other changes are needed from the user's standpoint besides including the AsyncInferenceConfig block when creating the Endpoint Configuration.

New or Affected Resource(s)

• aws_sagemaker_endpoint_configuration

Potential Terraform Configuration

resource "aws_sagemaker_endpoint_configuration" "main" {
  async_inference_config {
    client_config {
        max_concurrent_invocations_per_instance = 1
    }

    output_config {
      kms_key_arn = aws_kms_key.main.arn

      s3_output_path = "s3://${aws_s3_bucket.main.id}/output"

      notification_config {
          error_topic   = aws_sns_topic.error.arn
          success_topic = aws_sns_topic.success.arn
      }
    }
  }
  ... etc
}

References

• https://aws.amazon.com/about-aws/whats-new/2021/08/amazon-sagemaker-asynchronous-new-inference-option/
• CreateEndpointConfig request parameters

[zachchurchill]

One thing to note from creating these Endpoint Configurations in the AWS UI is that an Endpoint Configuration that has an AsyncInferenceConfig can only have 1 production variant. Not sure if it should be left up to AWS to return the error to the user upon terraform apply or if this check should be baked into the Terraform schema check.
Unfortunately I can't find anywhere in the documentation where this limitation is explicitly stated so it may just be a feature of the option being new and multiple production variants not being supported yet. (Though it is worth pointing out that the InvokeEndpointAsync action doesn't include parameters for the variant name - docs)

[github-actions]

This functionality has been released in v3.59.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.