Skip to content

ec2:AttachVolume steps fail with timeout #15

@rostskadat

Description

@rostskadat

Either steps involving ec2:AttachVolume (attachNewEBSVolume and attachOriginalVolume) fail with a timeout, leaving the instance in a inconsistent state, as it ends up without any volume attached.

One solution it to change the SSM document to increase the timeout of both these steps to 300 instead of 180.

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