npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@awsless/formation

v0.0.57

Published

The `@awsless/formation` package is a TypeScript API that provides an infrastructure as code solution for AWS.

Downloads

260

Readme

Infrastructure as code made fast & easy

The @awsless/formation package is a TypeScript API that provides an infrastructure as code solution for AWS.

The problem

The most used IaC solutions are slow & don't effectively leverage diffing to speed up their deployments.

Todo's

  • Make a build script to bridge terraform providers to awsless. (This will open up the ability for us to support all cloud providers currently supported by terraform.)
  • Add tags that will propagate to it's children nodes. (This will allow us to set tags on the stack and make the tag available for all resources inside the stack.)

Setup

Install with (NPM):

npm i @awsless/formation

Example

First, you need to create a workspace instance and pass in the cloud providers that you will use. We also need to give it a lock provider & state provider.

  • A cloud provider is used to create resources on a specific cloud provider. We have built-in cloud providers for AWS resources, but you could simply add your own as well.

  • The state provider is used for storing the latest deployment state.

  • The lock provider is used for acquiring a lock when you deploy your app. This will guarantee that multiple people can never deploy the same application at the same time.

In this example, we will use a local file lock & state provider.

import { minutes } from '@awsless/duration'
import { fromIni } from '@aws-sdk/credential-providers'
import { App, Asset, local, aws, Stack, WorkSpace } from '../src'

const workspace = new WorkSpace({
	cloudProviders: aws.createCloudProviders({
		region: 'AWS_REGION',
		credentials: fromIni({ profile: 'AWS_PROFILE' }),
		accountId: 'AWS_ACCOUNT_ID',
		timeout: minutes(15),
	}),
	stateProvider: new local.file.StateProvider({
		dir: './state',
	}),
	lockProvider: new local.file.LockProvider({
		dir: './locks',
	}),
})

With your workspace configuration ready we can now move on to defining your infrastructure. This example illustrates how simple it is to define multi-stack resources without worrying about cross-stack references.

const app = new App('shiny-new-app')
const stack = new Stack(app, 'storage')
const bucket = new aws.s3.Bucket(stack, 'files')

const stack2 = new Stack(app, 'todo')
const todoItem = new aws.s3.BucketObject(stack2, {
	bucket: bucket.name,
	key: 'item-1',
	body: Asset.fromString('Write documentation...'),
})

After defining your infrastructure, we can deploy our app.

await workspace.deployApp(app)

Or destroy our app.

await workspace.deleteApp(app)

Maybe you want to only deploy a subset of stacks.

await workspace.deployApp(app, {
	filters: ["storage"]
})

Production

For production, we recommend you use a state & lock provider that stores your data in the cloud. An AWS DynamoDB table is perfect for storing locks. While AWS S3 is perfect for storing your state files.

const workspace = new WorkSpace({
	cloudProviders: aws.createCloudProviders({ ... }),
	lockProvider: new aws.dynamodb.LockProvider({
		region,
		credentials,
		tableName: 'awsless-locks',
	}),
	stateProvider: new aws.s3.StateProvider({
		region,
		credentials,
		bucket: 'awsless-state-UNIQUE_ID',
	}),
})