Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    aburkleaux-amazon
    @aburkleaux-amazon
    Thanks for confirming. One more question, you mentioned that you are adding your operators via the custom resource. Did you add them to the OperatorLibrary stack?
    Jack Liddiard
    @deadcore
    We're adding them through custom resources in CDK and the provided custom resource Lambda in MIE. Something in the spirit of this:
    const resource = new cdk.CustomResource(this, `${operatorName}Operation`, {
      serviceToken,
      properties: {
        ResourceType: "Operation",
        Name: operatorName,
        Type: type,
        Configuration: configuration,
        StartLambdaArn: this.startLambda.handler.functionArn,
      },
    });
    
    const cfnResource = resource.node.defaultChild as cdk.CfnResource;
    cfnResource.overrideLogicalId(`${operatorName}Operation`);
    Jack Liddiard
    @deadcore
    Screenshot 2021-06-29 at 08.40.38.png
    So during some further digging yesterday we discovered yesterday that the names are being truncated by what I assume is CDK - and removing the key word OperatorLibrary
    Screenshot 2021-06-29 at 08.40.16.png

    Shorting the prefix to something like j1 was one work around but this does go against the spirit of our project - each developer has their own stack instead of sharing the same MIE insights.

    Are you aware of any other possible work arounds/fixes/hacks? Or are we looking at bitting the bullet and sharing a MIE stack?

    p.s. I really do appreciate your support @aburkleaux-amazon :)

    aburkleaux-amazon
    @aburkleaux-amazon
    One workaround would be to disable that block of code that dynamically adds lambda policies and put in a more permissive pattern-based policy for the role that is being built up. There is already a pattern-based policy for the OperatorLibrary lambdas, but it is going to hit a variation of this same bug because we're relying on that string always being embedded in the name of the lambda function. Here's where you would need to add the policy: https://github.com/awslabs/aws-media-insights-engine/blob/62f2fb78aa24e68740ef6cda47cf65e7070e62bf/deployment/media-insights-stack.yaml#L490
    BTW - I entered a new issue for this. Feel free to update it if you discover more info. awslabs/aws-media-insights-engine#522
    Ian Downard
    @ianwow
    MIE 3.0.1 was released on Github today. It includes minor documentation and security improvements. Most notably, the Implementation Guide now has up-to-date API docs. https://github.com/awslabs/aws-media-insights-engine/releases/tag/v3.0.1
    Ian Downard
    @ianwow
    We’re looking for someone outside the core MIE development team to validate the manual build instructions documented in the MIE readme file. Is anyone here able to help us with that?
    7 replies
    Ian Downard
    @ianwow
    MIE 3.0.2 was released on Github today. It includes minor bug fixes and improved test coverage for Amazon Translate operations. https://github.com/awslabs/aws-media-insights-engine/releases/tag/v3.0.2
    Zoltan Arvai
    @zoltanarvai_twitter
    Hi @ianwow! We have developed a pretty cool solution on top of Media Insights for a big client and we'll be processing over 100k videos from their media library. We are planning a spike to see how many videos we can process concurrently. We are aware of some AWS default quotas / limitations but we are wondering if there is anything specific you can think of that could be a bottleneck or some non-obvious AWS quotas that could block us. (let's say kicking off 10k jobs). (yes we are aware it'll be very costly :D)
    9 replies
    Ian Downard
    @ianwow

    I've released version 2.0.0 of Content Analysis on Github: https://github.com/awslabs/aws-content-analysis/releases/tag/v2.0.0

    This release includes big back-end changes but very few UX/UI changes. Most notably, MIE has been decoupled from Content Analysis, thus greatly improving code maintainability.

    Ian Downard
    @ianwow
    Version 2.0.0 of the AWS Content Analysis solution has been published on the AWS Solutions catalog. Release notes here: https://github.com/awslabs/aws-content-analysis/releases/tag/v2.0.0 . Notable user interface changes include:
    • Allow users to control playback speed in the video player.
    • New in-app dialog window shows users how to run search queries via the command line.
    Ian Downard
    @ianwow
    MIE 3.0.3 was released on Github today. It includes improvements in control plane scalability, build automation, and documentation. https://github.com/awslabs/aws-media-insights-engine/releases/tag/v3.0.3
    6 replies
    Ian Downard
    @ianwow
    MIE 3.0.4 was released today. This release includes relatively minor improvements to CloudFormation organization and IAM policy scope. See: https://docs.aws.amazon.com/solutions/latest/aws-media-insights-engine and https://github.com/aws-solutions/aws-media-insights-engine/releases/tag/v3.0.4
    Jason Tadros
    @winston1000
    @ianwow would you mind sharing the command to quickly sync the build to an existing web? It seems way more complicated than it should be. At the moment I am creating new webstacks each time but only keeping the mie. Is that right?
    1 reply
    Really just trying to shorten the cycle for making changes.. I tried sync but it failed.
    It sync'd but then I couldn't log in
    Jason Tadros
    @winston1000
    @ianwow ok I figured it out I think, I'm having trouble sending metadata as a dict though. Do you have an example post payload for metadata?
    8 replies
    João Guimarães
    @jccguimaraes
    Hi! I have been trying to get the step function arn for the workflow on MIE but no success. Can any one tell me if that's possible and how? Thanks
    8 replies
    UnkleRikko
    @UnkleRikko
    I noticed that AWS Content Analysis had trouble with Cues, specifically beginning and ending credits, on a cooking show since recipes were shown on screen throughout the show. Something to be aware, thought I'd mention it.
    2 replies
    UnkleRikko
    @UnkleRikko
    How could hundreds or even thousands of files be batched via automation to the Content Analysis solution at once for analysis?
    5 replies
    Jack Liddiard
    @deadcore

    Afternoon @ianwow - have a quick question about a PR you recently merged in (ref: aws-solutions/aws-media-insights-engine#635). We're looking at 'Restarting' a failed job and noticed they would always pass through and get marked as completed. After tracking it down we realised you have already fixed it (coincidental timing huh 😅)

    Our question is - would the fix be able to be merged into v3 of MIE and released? I did notice it would technical be a 'breaking change' as the new field is referenced in exchange for old behaviour. Could this be mitigated against by checking for the new 'MediaType' key and if not present default to old behaviour. Something to this effect:

    media_type = retrieve_asset["results"]["MediaType"] if "MediaType" in retrieve_asset["results"] else s3key.split('.')[-1]

    Hope I managed to explain our problem enough, if not please feel free to say and I'll try and expand more 🙂

    12 replies
    UnkleRikko
    @UnkleRikko
    Is it possible to use metadata tags for analysis of specific objects instead of every object min an S3 bucket?
    4 replies
    Ian Downard
    @ianwow
    MIE 4.0.0 was released today. It includes new support for Amazon Transcribe (custom language models and source language auto-detection), and a new checkin/checkout capability to mutex lock assets. https://github.com/aws-solutions/aws-media-insights-engine/releases/tag/v4.0.0
    Russ B
    @htartisan
    I have been trying to do some testing / experimentation with the "aws-solutions/aws-content-analysis" MEI open source software on GitHub. I tried clicking on "US West -> Launch Stack", but the stack creation always seems to fail. The "Nested" stack seems to fail with the following error...
    Status reason - The following resource(s) failed to create: [WorkflowSchedulerLambda].
    The mail stack seems to fail with the following error...
    Status reason - The following resource(s) failed to create: [MieStack].
    Anyone have any suggestions about what I might be doing wrong, or what I need to do to get this to work?
    2 replies
    Ian Downard
    @ianwow
    Version 4.0.1 of MIE was released today. It includes a small but high priority fix that is needed to avoid an error that was occurring in v4.0.0 when creating workflows. https://github.com/aws-solutions/aws-media-insights-engine/releases/tag/v4.0.1
    Ian Downard
    @ianwow
    Content Localization v2.0.0 was released today. It features support for custom language models and source language autodetection in Amazon Transcribe. It also includes a several bug fixes and performance enhancements. https://github.com/aws-solutions/aws-media-insights-content-localization/releases/tag/v2.0.0
    Ian Downard
    @ianwow
    MIE version 5.0.0 was released today. This is a major update that gives users more control over the encryption keys used by MIE resources and data. https://github.com/aws-solutions/aws-media-insights-engine/releases/tag/v5.0.0
    Yemane Yohannes
    @yemaney
    just tried to use the MIE v5.0.0. But it automatically rolls back as soon as it gets set up. Any ideas what may be causing this issue?
    1 reply
    sknadella87
    @sknadella87
    Hello Everyone, I was successfully able to deploy the stack and log into the application with the user account that's provided during the stack creation
    But when I try to setup the Cognito to authenticate via Google - I get redirected but I'm getting prompted to the login page instead of automatically signing in to the google account
    @ianwow / @brandold Would you be able to assist with this issue?
    18 replies