Many of our larger customers—especially in fintech, health tech—who operate in regulated industries have asked for a way to get private, real-time access to senior Cloud Posse engineers for their most critical projects.

These teams often run into scenarios where:

• Delays, mistakes, or failed migrations would cost big
• They need to de-risk complex platform changes
• They want trusted guidance on Cloud Posse architecture and components—from the engineers who built it

Platform Advisory was designed specifically to address these needs.

What is Platform Advisory?​

Platform Advisory gives your team:

• Private Slack Connect → direct access to Cloud Posse’s staff-to-principal-level engineers
• On-demand Zoom sessions → architecture reviews, migration planning, compliance discussions, and more
• Same-day response (4-hour SLA) → for high-impact requests
• 10 hrs/month of Flexible Support included → for bug fixes, upgrades, Atmos enhancements, new components, and integration work

It’s designed for teams running on Cloud Posse’s reference architecture and open source components who need priority access to expert guidance—especially when getting it wrong isn’t an option.

Why we built this​

As more of our customers adopt Cloud Posse architecture for mission-critical platforms, they’ve asked for a way to engage more deeply—especially for projects where de-risking migrations and accelerating delivery matters.

When the team is facing a complex migration, rolling out new environments, or making high-impact platform changes—waiting days for answers isn’t good enough.

Platform Advisory gives them priority access to engineers who:

• Know Cloud Posse architecture inside and out
• Understand their environments and goals
• Can chart the best path forward quickly and safely

How it fits with our other support options​

Where to learn more​

You can explore all the details on the Platform Advisory support page.

If you’re unsure whether Platform Advisory is the right fit for your team, reach out to us—we’re happy to help.

Remember: When you invest in Cloud Posse, you’re not just helping your team—you’re strengthening the ecosystem your business depends on.

We’re excited to make Platform Advisory available—and we look forward to helping more teams succeed on Cloud Posse architecture.

Hello SweetOps!

A few months ago, we embarked on a MASSIVE project to enable Component Testing.

The goal is to improve the stability of our components, detect and fix integration errors, and pave the way for confident delivery of new features. In the first phase, we split the cloudposse/terraform-aws-components monorepo consisting of 160+ Terraform Components into individual repositories in the cloudposse-terraform-components GitHub organization. We updated the cloudposse/github-action-atmos-component-updater GitHub action to rewrite URLs in component manifests automatically, allowing you to smoothly migrate to new repositories.

Current Status​

Now, we are happy to announce that we have completed the second phase of this project, introducing automated tests for the first 27 components. Hopefully, you are already using components from the new organization!

The complete list of covered components can be found here.

We've developed a Go-based testing framework built on top of Terratest, optimized specifically for testing Atmos components.
Additionally, we created a step-by-step guide to help you write effective component tests.
You can track the project's progress on this board.

We invite everyone to contribute to this project.

Please like the "Add component tests" issue in the corresponding component repository for which you are interested in prioritizing test coverage. If you want to contribute more, we have the opportunity.

How can you help?​

We really need help writing tests.

You can take any "Add component tests" issue with the "Good First Question" label and contribute to the test following our documentation.

We will prioritize reviewing your PRs in the #pr-reviews channel and help ensure they get merged smoothly.. Feel free to DM to @Erik Osterman or @Igor Rodionov in Slack with any questions or feedback.

P.S.: Huge thanks to @RoseSecurity for the first community-driven component test contribution here.

We're excited to announce that starting on November 12, 2024, we will begin migrating each component in the cloudposse/terraform-aws-components repository to individual repositories under a new GitHub organization. This change aims to improve the stability, maintainability, and usability of our components.

Why This Migration?​

Our goal is to make each component easier to use, contribute to, and maintain. This migration will allow us to:

What to Expect Starting November 12, 2024​

Migration Timeline​

The migration will begin on November 12 and is anticipated to finish by the end of the following week.

Code Freeze​

Starting on November 12, this repository will be set to read-only mode, marking the beginning of a code freeze. No new pull requests or issues will be accepted here after that date.

New Contribution Workflow​

After the migration, all contributions should be directed to the new individual component repositories.

Updated Documentation​

To support this transition, we are updating our documentation and cloudposse-component updater.

Future Archiving​

In approximately six months, we plan to archive this repository and transfer it to the cloudposse-archives organization.

Frequently Asked Questions​

Does this affect Terraform modules?​

No, only the terraform-aws-components repository is affected. Our Terraform modules will remain where they are.

We are committed to making this transition as seamless as possible. If you have any questions or concerns, please feel free to post them in this issue. Your feedback is important to us, and we appreciate your support as we embark on this new chapter!