Fugue solves many of the complex problems associated with declaring, deploying, and managing cloud workloads at scale and the functionality highlighted here is just part of our solution. If you find yourself reading this and you’re still asking... What’s Fugue? We suggest starting on the Fugue Product Page or taking a few minutes to scan the FAQ.
We have a lot of great documentation, so if you’re not sure what information you need, and you’re interested in exploring some of what Fugue offers, we’ve organized content here based on the question - What are you looking for?
I need to build new infrastructure. Excellent, we can definitely help with that.
- Composer is a tool that offers an interactive diagram of a composition (Ludwig files) so you can visually explore the infrastructure you want to build. Read more about it here.
- Take at look at our
option for commands. Using
dry-runprovides a preview of how Fugue will provision your infrastructure in a composition without actually executing the command. It’s a great way to see what you’re building before you deploy.
- Do you need somewhere to start writing configurations with Ludwig? We have that covered. If you’re looking for something more advanced, Fugue includes a Standard Library Reference that offers a catalog of every library and utility that ships with our product.
- Beyond that, for a much deeper dive, you can also check out a guide for Learning Ludwig Syntax and explore more content about Advanced Ludwig.
I have existing infrastructure - and I’d like it to be managed by Fugue
- Did you know that you can use Fugue to migrate your existing infrastructure? You can!
- With Fugue you can use Composer or Transcriber to scan your AWS account for existing infrastructure to generate a Ludwig composition representing your resources, and import those details using the Fugue CLI.
I need tools to manage my users & infrastructure. To learn a bit more about the mechanics of Infrastructure Governance or perhaps just take a closer look at some other tools Fugue offers.
- For help managing permissions, Fugue includes RBAC (role-based access control) to define user roles and responsibilities.
- We also allow you to define, provision, and enforce cloud infrastructure across multiple AWS accounts with a single Conductor using our Multi-Account feature.
- And if you’re interested in policy and compliance, we have tools for validations that can be done before you deploy with Design-Time Validations, or as part of your running infrastructure with Runtime Validations.
Hopefully you’ve found something you were looking for! But… if you find yourself interested in getting your hands dirty, why not Try an Example? Curious to understand how things work - read about our System Architecture. Still have questions, we want to know! Reach out to us through firstname.lastname@example.org.
Every release of Fugue includes updates to our documentation. To browse the full product release notes head over to the Download Portal. If you want to know what’s new in the docs for our 2018.07.25 release, here are the highlights:
- Added documentation for the new
fugue runtimecommand. The
runtimecommand enables users to make changes to Conductor log levels and how often the Conductor makes certain API calls. Read more about it here.
- Updated the Product Setup Options page with default values.
around usage for
fugue user set.
- Updated docs with information on Fugue support for subscriber-based activity notifications in JSON with AWS SNS topics.
Previous updates from 2018.06.15
- Added information on the new RBAC delegation function including a hands-on example demonstrating this feature.
- Updated our Functions Tutorial to provide answer keys in the Github repo. We also improved Exercise 2.
- Expanded documentation on using
fugue killto include a section on caveats and exceptions.
- Provided details on Fugue’s support for running through a proxy.
- Documented the ability to install the Fugue Conductor in an existing VPC.
- Updated the steps for adding a second AWS account.
If you have question or concerns, as always reach out to us via email@example.com