Skip to content

Metaflow Deployed AWS Batch Job Causes Security Hub To Raise Risk Items #366

@yuminghuang23

Description

@yuminghuang23

Hi, we use batch jobs created via metaflow --with batch option to create metaflow batch jobs on aws. Recently, after new security measures were introduced and enabling of security hub, it is raising high risk items. Below are the items:

  • ECS.1 Amazon ECS task definitions should have secure networking modes and user definitions.
  • ECS.4 containers should run as non-privileged
  • ECS.5 ECS containers should be limited to read-only access to root filesystems
    Details on aws doc for these items can be found here

Are there plans to update metaflow to adhere to these aws security checks?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions