Skip to content

Media Insights Engine 3.0.0
Compare
Choose a tag to compare
@ianwow ianwow released this 23 Jun 02:18
v3.0.0
5c8af8d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version 3.0.0 of MIE features the ability for workflows to input media files that are stored in an S3 bucket which is managed outside the MIE stack. This enables users to trigger workflow executions from S3 events, so workflows can automatically process files when they are copied to an S3 bucket.

New:

  • Workflows can now input media files that are stored in an S3 bucket which is managed outside the MIE stack. Prior to this release workflows required input media files to reside within the MIE data plane bucket. In order to use this capability the ARN for the external S3 bucket must be specified in the ExternalBucketArn parameter in the MIE base template for Cloud Formation (#489)

  • Added a new parameter in the MIE Cloud Formation template that allows users and parent stacks to opt-out from anonymous data collection (#509)

  • Added a new parameter in the MIE Cloud Formation template that allows parent stacks to associate their AWS solution id with MIE's boto3 calls. This helps the AWS Solution Builder team improve the quality of published solutions.

Changes:

  • Media files are no longer copied to the data plane S3 bucket when recording new assets. This change will break backwards compatibility for applications that assume the S3Bucket property for assets is always the data plane bucket. This change is also the only change that caused MIE's major release number to bump from v2.5.0 to v3.0.0. (#489)

  • If input media files cannot be found at the S3 location specified within workflow execution requests then return an error to the HTTP client indicating that the file could not be found. (#507)

Security:

CI/CD Automation:

  • Validate S3 bucket ownership before uploading build artifacts (#499)

Documentation:

  • The implementation guide now explains about how to start workflows programmatically and provides Python code samples for doing so. These examples can be used to set up an S3 trigger for workflow execution. (#489)
Assets 2
Loading