Import your draw.io diagrams (Beta)

A lot of AWS architectures already live in .drawio files. Now you can bring yours in: pick a .drawio (or draw.io .xml) file on the new-project screen or from an open canvas, and the shapes become real, editable services on the canvas, with your layout preserved, VPC and subnet boxes intact, and your connections drawn. Today's importer reads the AWS shape libraries — current and legacy — and imports your diagram's first page; when a file has more pages, the report says so.

A drawing and a deployable stack are not the same thing, so the import ends with a straight accounting: what mapped, what we had to assume (an API Gateway shape could be a REST or HTTP API — we pick one and tell you), what was skipped because no AWS shape matched, and which connections need you to choose what they mean. From there, the findings panel walks you through what each service still needs before it can ship — the same path every canvas takes to working CloudFormation.

It's a Beta, and we mean that honestly: real-world diagrams are wonderfully messy, and the mapper will keep learning. If a diagram of yours imports wrong, email the file to support@cloudstackcanvas.com — every report makes it better. Available on Pro and Team plans.

Fixes & improvements

• •Connections drawn to an ECS service now grant the running task its permissions — S3, SQS, and Secrets Manager access wired through the task role, with encryption-key access included, and a warning when a connected role's trust policy would keep ECS from using it.
• •The ECS starter templates now wire their task roles explicitly, and three new guides cover role trust and shared task definitions.