- Newest
- Most votes
- Most comments
AWS Diagrams and Lucidchart are both tools for creating diagrams, but they have different capabilities and pricing models.
AWS Diagrams is a tool provided by Amazon Web Services (AWS) that allows users to create diagrams of their AWS infrastructure. It is integrated with other AWS services, such as Amazon Elastic Compute Cloud (EC2) and Amazon Simple Storage Service (S3), and can automatically update diagrams based on changes to the underlying infrastructure. It is priced based on the AWS resources used to create and store the diagrams.
Lucidchart is a separate third-party tool that can be used to create a wide variety of diagrams, including flowcharts, wireframes, and UML diagrams. It is not specific to AWS and can be used to create diagrams for any purpose. It is priced on a per-user basis, with different pricing plans available for individuals, teams, and enterprise users.
In summary, AWS Diagrams is a specialized tool for creating diagrams of AWS infrastructure, while Lucidchart is a more general-purpose diagramming tool that can be used for a wide range of purposes. AWS Diagrams is integrated with other AWS services and is priced based on the resources used, while Lucidchart is priced on a per-user basis.
Thanks very much! I'm still struggling a bit with getting WD spun up -- some kind of account quota issue so probably nothing to do with the solution itself. It would be great to hear your impressions about the two.
Anytime. My demo with CloudCraft is today. I'll be sure to reply my thoughts on both solutions.
So far, I've been happy with WD; however, I need to do a deeper dive in the cost. It deploys a VPC, IGW, 2 NAT Gateways, 3 Elastic IP's, among other resources. According to the documentation that's equates to about $770 a month, whereas CloudCraft is $49 per user/month.
I ran into a few bumps with WD. With the quota issue refer to the links below....I think that might be what you are bumping up against.
See step 4 under Launch Stack https://docs.aws.amazon.com/solutions/latest/workload-discovery-on-aws/automated-deployment.html The reference above links you to IAM and STS quotas - which I believe is what you are running into. https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-quotas.html
Thanks! I was concerned about the cost, too, but then noticed that most of it is for the two EC2 instances (for Neptune and Opensearch), so changed them to t3.medium at least for the proof-of-concept (assuming performance is OK). The other thing was just the breakeven point for number of users, so if you have a bunch of people who might want to visualize the resources, WD could end up being less expensive in the end.
On the other hand, there could be issues with access rights. Apparently there is no fine-grained authorization control in WD, so it sounds like if someone has access to the graph they can click on anything and get access to the resource (?). That's something I want to test and be sure I understand, since it could mean we don't want to spread out access to a large community of users (and so cost per user becomes a factor again).
Also thanks for the quota hints. Maybe this will let me move forward today.
Relevant content
- asked a year ago
- asked 4 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
Hi Divyam,
Thanks for your note. What I'm really looking for, though, is a comparison of the capabilities between AWS Workload Discovery and Cloudcraft. Do you have experience with either of those?
Came here to ask the same. I setup Workload Discovery and thus far is a nifty tool. I have scheduled a demo with CloudCraft next week. I'll be sure to share deets