Skip to main content

8 posts tagged with "worx"

View All Tags

· 9 min read
Augusto Cocuzzo
Hugh Mooney

One of the first challenges in assisting AWS customers who have engaged a partner from the AWS Partner Network, like Hestio, is providing secure access to their AWS accounts with minimal permissions that align with good security practice.

Solution partners in the AWS Partner Network are often involved in shorter projects and ad-hoc activities such as security audits, well architected reviews, AWS migrations, and workload provisioning.

So, how can we make it easier for all AWS partners, not just Hestio, to help AWS customers?

· 10 min read
Augusto Cocuzzo

Welcome to another exciting blog post, where we will dive deep and explore how we helped a long-standing AWS customer regain control over their data lake, consisting of over 3 Petabytes (PB) of S3 data.

This customer embarked on their cloud journey over a decade ago, embracing the scalability and flexibility offered by AWS. Nevertheless, as time went by, they found themselves grappling with a growing challenge – an ever-increasing pool of data that had accumulated within their S3 buckets. Data management practices had adjusted with growth, however, the customer had no clear visibility into which data was essential to retain and which could be safely removed.

How can we decide what needs to be retained if we don't have visibility of the inventory we have?

· 4 min read
Hugh Mooney

As organizations embarked on their cloud adoption journeys, the established practice was to treat the cloud as a separate domain, similar to other specialized areas such as networking, user management, or databases. This approach involved dedicated and specialized teams responsible for the ownership and operation of yet another single vertical within the organization; cloud. However, this model has proven to be more of a hindrance than a long-term success, resulting in more barriers to adoption and ever increasing costs.


Figure: The traditional CCOE experience

· 4 min read
Hugh Mooney

What if I told you that delivering a modern asset management lifecycle could be achieved using automation and infrastructure-as-code in a way that could be added to your existing DevOps pipelines? Traditional DevOps pipelines and managing digital assets are a lot more alike than you think;


Figure: Digital Asset Management lifecycle as a pipeline

· 4 min read
Hugh Mooney

Clear benefits

The benefits of adopting an infrastructure-as-code (IAC) approach to provisioning and managing resources is widely accepted. The benefits unlocked by using Hashicorp's Terraform for this are also well documented, in short;

  1. Version Control: Terraform code can be stored in a version control system, making it easy to track changes and collaborate with others.
  2. Repeatability: Terraform IAC can be executed repeatedly, ensuring consistent and predictable infrastructure deployment.
  3. Idempotency: Terraform ensures that the desired state of infrastructure is always met, regardless of how many times the workflow is run.
  4. Automation: Terraform can help automate the provisioning and management of infrastructure, reducing manual effort and the risk of human error.
  5. Scalability: Terraform can manage multiple AWS resources and scale infrastructure up or down as needed.
  6. Improved visibility: Terraform provides clear and concise documentation of the infrastructure and its configuration, making it easier to understand and manage.
  7. Cross-provider support: Terraform can provision and manage infrastructure across multiple cloud providers, including AWS, making it a versatile tool for managing infrastructure.

At what cost and risk?

The challenge to unlocking those benefits though is to find an approach will be cost effective and minimise your risks.