Actually, it is only broke for deploying lambdas.  You can also work around it by using the previous providor:


```
terraform {
  required_providers {
    aws = "<= 3.16.0"
  }
}
```

The reason it broke is it using the new aws feature for code signing lambdas.  Those new APIs are not implemented or mocked in a reasonable way in localstack.

Is there a plan to mock or implement those APIs?



┆Issue is synchronized with this [Jira Bug](https://localstack.atlassian.net/browse/LOC-347) by [Unito](https://www.unito.io/learn-more)

def get_java_handler(zip_file_content, main_file, func_details=None):
    """Creates a Java handler from an uploaded ZIP or JAR.
    :type zip_file_content: bytes
    :param zip_file_content: ZIP file bytes.
    :type handler: str
    :param handler: The lambda handler path.
    :type main_file: str
    :param main_file: Filepath to the uploaded ZIP or JAR file.
    :returns: function or flask.Response
    """
    if is_zip_file(zip_file_content):
        def execute(event, context):
            result = lambda_executors.EXECUTOR_LOCAL.execute_java_lambda(
                event, context, main_file=main_file, func_details=func_details)
            return result
        return execute
    raise ClientError(error_response(
        'Unable to extract Java Lambda handler - file is not a valid zip/jar file', 400, error_type='ValidationError'))
def set_archive_code(code, lambda_name, zip_file_content=None):
    
    lambda_arn = func_arn(lambda_name)
    lambda_details = ARN_TO_LAMBDA[lambda_arn]
    is_local_mount = code.get('S3Bucket') == BUCKET_MARKER_LOCAL
    if is_local_mount and config.LAMBDA_REMOTE_DOCKER:
        msg = 'Please note that Lambda mounts (bucket name "%s") cannot be used with LAMBDA_REMOTE_DOCKER=1'
        raise Exception(msg % BUCKET_MARKER_LOCAL)
    
    LAMBDA_EXECUTOR.cleanup(lambda_arn)
    if is_local_mount: