Operations | Monitoring | ITSM | DevOps | Cloud

Today, Stackery is announcing enhanced security and continuous integration and delivery (CI/CD) capabilities that enable teams to automate delivery best practices from laptop to production. With additional audit capabilities, scoped IAM permissions, and secrets management for automated verification and deployment pipelines, Stackery helps teams scale serverless usage and accelerate modernization and innovation projects.

I recently joined Stackery from Puppet: a company that specializes in great automation software for the globe’s biggest enterprise IT operations teams. I had the privilege of learning from folks doing the best work of their life to automate the provisioning, configuration, and maintenance of infrastructure that enables teams of developers to move fast and make a difference for their business.

Stackery’s secure serverless platform for AWS offers teams a key resource to help realize the promise of serverless – by automating otherwise complex infrastructure processes, we enable you to leverage the massive suite of AWS tools and services with minimal management overhead. It’s crucial for teams to do this while enforcing security and ensuring adherence to compliance guidelines.

A good software design tool enables rapid visualization of application architectures, much like a virtual whiteboard. A great design tool validates service architectures, their communication flows and the infrastructure required to execute them—and builds a scaffold that can be seamlessly taken forward into development. Security is a vital component of that scaffolding, starting at the design stage and extending through the application lifecycle.

Stackery is pleased to announce its addition of support for the new AWS HTTP APIs service which is being introduced today alongside the existing API Gateway tooling. Our addition of such support, in parallel with the GA announcement of HTTP APIs, is an example of how we partner with AWS to accelerate serverless application development and delivery for customers.

This article was originally published on The New Stack Kubernetes in 2020 has become synonymous with the term cloud native and is also often used as a vehicle for vendors and IT organizations alike to claim they are transforming or modernizing their workloads. But what are they actually transforming? What is Kubernetes itself actually providing?

Whether you help architect serverless applications at work or you’re just getting started in the community, chances are you’ve caught wind of a ServerlessDays event. Each one gathers members of a local community to talk about where serverless technology currently stands and where it’s going. The best part is that they are a true community event, built by and for serverless users.

Team Stackery has been hosting the PDX Serverless Architecture meetup at our Portland office since June of 2018, although the meetup began the year before. It’s always great to see repeat visitors and new faces, and especially to see our community change over the months. In February, we had an entertaining, dynamic, and knowledgeable speaker in Yves Gurcan.

This weekend I had the opportunity to participate in the AWS Hackathon in Portland. Based on the hackathons hosted at re:Invent, this brought together about 100 developers of all skill levels to break up into small teams and produce a demo product in 10 hours. I had a great time, and wanted to share what I learned! There may be organization-specific roadblocks to adopting AWS Lambda right now and therefore, it might not be the right fit for your team at this particular juncture.

Too often serverless is equated with just AWS Lambda. Yes, it’s true: Amazon Web Services (AWS) helped to pioneer what is commonly referred to as serverless today with AWS Lambda, which was first announced back in 2015. But in 2020, it’s important for enterprises to understand that the serverless landscape is much bigger with more opportunities. Serverless is sometimes (narrowly) defined as just being about functions-as-a-service, but that’s a very limited viewpoint.