Firefly Cloud Resilience

Our main use case for Firefly is generating image variations, which we are using in Adobe Experience Manager on AEM pages and various kinds of images because our solutions are image heavy. We generate variations of the same image for various viewports.

We upload the image in AEM DAM, and from the DAM, the UX team or the creative team use creative tools such as Photoshop or Figma to import these images into their toolset. They create various variations for different dimensions, viewports, and shadings for the same image.

Firefly is integrated with AEM and other UX tools such as Adobe Express, Adobe Photoshop, and Figma, through which images uploaded in the DAM are accessible in the UX tools.

Firefly has impacted my organization positively because it is very quick and does not take much time to create various kinds of images from the same image. Bulk accessing is a quick connection from AEM DAM to UX tools. We can see all the images which are uploaded in the DAM directly viewable in these tools, and the UX team can pick the right asset that they need to work upon.

In terms of time saved or improvements for my team, people who have basic understanding of using UX tools find it very convenient to work with and create many images in a quick time. Earlier it was taking too much time to find the right asset, and we had huge dependency on the marketing team. Now the creative team helps us to create the required images with these tools and Firefly.

We save about fifty percent of our time because earlier, to get images for one page, the marketing team used to take one or two days to provide the right assets. Now with the help of Firefly and these UX tools, the team is able to do it in half of the day.

Firefly offers on-the-fly viewport generations, shading, and various variations of the same image, including changing the background and changing the color. It is an asset that you can work with and generate various kinds of assets on the fly. Based on the use case, you can pick the right asset.

Out of the features mentioned, including on-the-fly viewport generation, shading, and background changes, I find myself using the cropping of the same image for mobile, tablet, and desktop viewports the most because this is one of the best features that we love from Firefly.

The integration with UX tools is very easy from AEM, and the UX team finds it very convenient to work with. They are using Firefly to generate various renditions and variations of the same image.

Firefly could be improved by providing more connected plugins or integrations with other tools or some freeware tools which do not require any kind of licensing. Currently, all these UX tools are licensed tools where we need to pay monthly subscription fees. If Firefly could be provided freely, then other UX professionals could use it.

This is somewhat tricky because if someone does not have good experience on the UX side, they will find it difficult to navigate and find the right asset. There are many controls on these UX tools, with widgets placed throughout, making it very difficult to find where to click to locate the right asset and how to browse assets properly. This requires some technical knowledge and familiarity to use these tools.

We have been using Firefly for more than three years.

Firefly is very stable.

Firefly scales very well because the moment you upload any asset in the DAM, you can quickly browse these assets in these UX tools. In Figma, Photoshop, or Adobe InDesign, Firefly picks the images very quickly and does not take much time.

Customer support is pretty good because if there is any issue, we raise a support ticket to the Adobe console and the Adobe team helps with that.

I would rate customer support an eight.

We were using the out-of-the-box DAM solution and the marketing team provided assets earlier, but now we have moved to Firefly and these UX tools.

It is a good decision to use Firefly because it creates nice images, very clean images with no blurry images, and the images that we are using from Firefly and rendering on the page look very nice, attracting our users to come back and see the pages again and again.

Our experience with pricing, setup cost, and licensing is that Firefly came along with the license from Adobe Experience Manager, and all customers who have purchased Adobe Experience Manager have tool access to Figma, Adobe InDesign, and Adobe Photoshop. The creative team can use these tools, but the exact costing details may be known by our account team.

Before choosing Firefly, we have only explored the out-of-the-box DAM solutions in Adobe Experience Manager.

I would rate Firefly an eight.

I chose eight out of ten for Firefly because it requires some technical knowledge to browse assets from AEM DAM, and we need to have plugins to browse DAM assets in Firefly tools such as Photoshop, InDesign, or Figma.

I have not used the AI capability from Firefly.

I have not explored the accuracy and reliability of Firefly's AI capabilities either.

I would definitely advise that if somebody wants nice and clean images and variations of images with various viewport renditions, Firefly is the right choice.

I have been working more than seven years in the AWS cloud solutioning part.

My main use case for Firefly is for AWS solutioning and building the infrastructure as code, because infrastructure as code is a standard for building new infrastructure. I used Firefly for building new code.

A specific example of how I used Firefly for infrastructure as code in my AWS solutioning work is when I was starting a new project and needed to write the entire infrastructure as code from scratch, similar to any Terraform or CloudFormation resources. Firefly helped me from scratch to building a solid infrastructure as code and deploying my resources on the cloud, leading to end-to-end delivery for infrastructure.

Regarding my main use case for Firefly, during the project, we had many resources manually created, making it difficult to find and standardize building the infrastructure code. Firefly's UI and visualization dashboard helped me find those resources, allowing me to transform and build infrastructure code that met the necessary compliance standards.

The best features Firefly offers include cost saving and drift detection, which native infrastructure as code solutions do not provide. Drift detection and governance are great features for Firefly that help me identify unutilized resources that can save costs.

Firefly's drift detection and governance help me day-to-day by notifying me of any configuration drifts, such as when developers change configurations that I cannot control. For example, if I have a number of VMs running and their configurations are changed, Firefly alerts me to these changes, allowing me to identify gaps in configurations that can be corrected.

Firefly's accuracy and reliability in output are impressive, with approximately 80% accuracy in building the required code for various services from the foundation services like EKS and VPC.

Firefly has positively impacted my organization mainly through cost savings and governance. It allows me to have a centralized dashboard for a complete view of my AWS accounts to find problems easily. Additionally, it has saved me time because I no longer need to write every Terraform from scratch, as Firefly provides best industry practices code.

For example, I monitored my database instances and found that someone had expanded the ACU size from the required number to ten times more, which began costing me $10,000 monthly extra for one AWS account. Firefly detected this and saved me the $10,000 extra expenditure.

In terms of improvements for Firefly, it can be made more AI native, though it already has a powerful Thinkerbel AI agent for recovery. There are initial setup and dependency requirements that could be made easier for broader audiences, and the UI can feel overwhelming for teams just starting their infrastructure as code journey, so more tutorials would be beneficial for beginners.

The documentation could be enhanced to help new users navigate the platform more effectively.

I have been working more than seven years in the AWS cloud solutioning part.

Firefly is stable and I have not experienced any downtime or reliability issues.

Firefly's scalability is impressive; as we add new AWS accounts and requirements, it has handled the growth well without any challenges.

Firefly's performance and speed when handling large-scale infrastructure have been good, with no noticeable slowdowns, although our initial learning speed as a team was slow.

Customer support for Firefly has been good, as we can easily reach them through ticketing or email, and our issues are typically resolved within the required SLA.

I would rate customer support an eight out of ten.

I have not used any paid infrastructure as code solutions before; we were utilizing Terraform for manual coding of everything. Firefly has made the implementation process easier and allowed for standardized processes.

Prior to choosing Firefly, I evaluated some Terraform Enterprise solutions, but we decided to go with Firefly because it supports multi-cloud environments and offers the enriched solutions we were looking for.

Firefly handles updates, patches, and ongoing maintenance smoothly by following a rolling update process, which has not caused any downtime for my application workloads.

Customizing Firefly to meet my organization's unique needs on the AWS platform is manageable, as best practices are readily available online, so I have not faced significant challenges in this area.

I see a return on investment because Firefly allows fewer resources to be needed for project delivery, resulting in a win-win situation for staff efficiency.

Regarding pricing, I feel there should be some free options available for new users, but overall, I find the pricing acceptable.

Prior to choosing Firefly, I evaluated some Terraform Enterprise solutions, but we decided to go with Firefly because it supports multi-cloud environments and offers the enriched solutions we were looking for.

I would rate Firefly around 7.5 out of 10.

I gave Firefly a 7.5 because it is very good for organizations looking to expand their cost saving and governance capabilities. However, understanding how it fits into existing complex systems can be challenging, so I expect more integration improvements. For greenfield applications or infrastructure, Firefly is a top tool.

Firefly provides helpful security recommendations and notifications about non-compliant cloud resources and can build a dashboard for tracking compliance fixes. I want to further explore how to remediate these issues using their AI agents in the next six months.

Firefly handles compliance and regulatory requirements well by allowing us to define client-specific standards like HIPAA or ISO compliance. Once rules are set up, Firefly helps identify necessary remediation and governance.

I purchased Firefly through the AWS Marketplace.

I believe we have covered most of the improvements needed for Firefly, particularly related to agentic workflows.

I have primarily used Firefly on AWS as I am an AWS native user and have not integrated it with any other cloud vendors, though the documentation suggests it supports multiple vendors.

The learning curve for new users adopting Firefly can be overwhelming; I believe improvements in onboarding and training materials are necessary to facilitate quicker adoption.

My advice for others looking into using Firefly is that if they have a new team developing greenfield environments on AWS, Firefly will provide an extra hand to help start quickly and correctly by following best practices.

My main use case for Firefly is cloud infrastructure management and Infrastructure as a Code governance. Specifically, I use it to discover and inventory cloud resources, detect configuration drift between cloud environments and Terraform, and generate and maintain Infrastructure as a Code.

Another valuable use case for Firefly is improving infrastructure visibility across teams.

The best features Firefly offers are automatic Infrastructure as a Code generation, configuration drift detection, unified cloud inventory, policy as code governance, asset history, and change tracking.

The automatic Infrastructure as a Code generation feature saves a lot of manual effort. For example, when an existing AWS resource is created manually or I inherit an environment that is not managed by Terraform, Firefly scans the environment and generates the Terraform code for those resources automatically. My team reviews the generated code, commits it to Git, and starts managing infrastructure through our normal CI/CD pipeline.

Another feature I find valuable is end-to-end infrastructure visibility.

Firefly has a positive impact on my organization by improving cloud governance, infrastructure consistency, and engineering productivity. Some of the key benefits are reduced manual effort in managing Infrastructure as a Code, improved visibility into cloud resources across accounts, and faster identification and remediation of configuration drift.

Some of the areas Firefly can improve are a simpler onboarding process for organizations with large and multi-cloud environments, more customization for generated Terraform code to better match existing coding standards and module structures, and more native integrations with DevOps and ITSM tools.

Additional improvements would include better cost optimization insights alongside the governance recommendations and better collaboration features.

I have been using Firefly for more than two years.

My advice for others looking into using Firefly would be to start with a well-organized Infrastructure as a Code strategy. Firefly delivers the most value when Terraform or another IaC tool is already part of your workflow. Use it early to discover unmanaged resources and bring them under version control before cloud environments grow larger. Integrate it with your GitOps or CI/CD pipeline and review AI-generated IaC and remediation suggestions before applying them to production. I would rate this product a 9 out of 10.