#refarch (2024-11)

We want to inform our community that starting next Tuesday (2024-11-12), we will begin migrating each component in this repository (cloudposse/terraform-aws-components) repository to a new GitHub organization. This change is essential to enhance the stability and usability of our components, including:

• Leveraging terratest automation for improved testing. • Implementing semantic versioning to clearly communicate updates and breaking changes. • Enabling a more modular structure, with a focus on maintaining individual components more effectively. • Accelerate PR reviews and component contributions • Automated dependabot updates • And tons more!!

What to Expect

• Migration Timeline: The migration process will start next Tuesday and is anticipated to be completed by the end of the following week. • Updated Documentation: We are actively updating our documentation and the cloudposse-component updater tool to facilitate a smooth transition. • Maintenance Mode: After this migration, this cloudposse/terraform-aws-components repository will enter maintenance mode. We will no longer accept new contributions here, and all updates should be directed towards the new individual component repositories. • Future Archiving: In approximately six months, we plan to archive this repository and transfer it to the cloudposse-archives organization.

FAQ

• Does this affect our terraform modules? No. We are not moving our terraform modules

We are committed to making this migration as seamless as possible, but if you have any questions or concerns, please post your comments in this issue. Your feedback is important to us, and we appreciate your support in this transition!

Thank you,

The Cloud Posse Team

When deploying a new cluster I wasn’t able to get node groups to join the cluster initially. It seems this is because the cluster endpoint is private and the vpc-cni addon isn’t deployed yet. By default we have addons_depends_on: true in our EKS catalog, however, that prevents the vpc-cni from being added. Changing it will prevent the workflow from completing successfully b/c coredns, etc. require a node.

What am I missing here?

Hi everyone,

Is it possible to somehow use reference architecture in one account?
Essentially, we need to set up just one prod account, without anything else, with just the vpc, IAM and a EKS cluster