change ddb to be on demand billing method

[jhsinger-klotho]

• Does any part of it require special attention?
• Does it relate to or fix any issue?

closes #9

Standard checks

• Unit tests: Any special considerations?
• Docs: Do we need to update any docs, internal or public?
• Backwards compatibility: Will this break existing apps? If so, what would be the extra work required to keep them working?

[github-actions]

Package	Line Rate	Health
github.com/klothoplatform/klotho/pkg/analytics	2%	❌
github.com/klothoplatform/klotho/pkg/annotation	24%	❌
github.com/klothoplatform/klotho/pkg/core	21%	❌
github.com/klothoplatform/klotho/pkg/env_var	82%	✔
github.com/klothoplatform/klotho/pkg/exec_unit	41%	❌
github.com/klothoplatform/klotho/pkg/infra/kubernetes	56%	➖
github.com/klothoplatform/klotho/pkg/infra/kubernetes/helm	52%	➖
github.com/klothoplatform/klotho/pkg/input	63%	➖
github.com/klothoplatform/klotho/pkg/lang	37%	❌
github.com/klothoplatform/klotho/pkg/lang/dockerfile	0%	❌
github.com/klothoplatform/klotho/pkg/lang/golang	9%	❌
github.com/klothoplatform/klotho/pkg/lang/javascript	46%	❌
github.com/klothoplatform/klotho/pkg/lang/python	60%	➖
github.com/klothoplatform/klotho/pkg/lang/yaml	0%	❌
github.com/klothoplatform/klotho/pkg/logging	7%	❌
github.com/klothoplatform/klotho/pkg/multierr	95%	✔
github.com/klothoplatform/klotho/pkg/provider/aws	54%	➖
github.com/klothoplatform/klotho/pkg/runtime	75%	✔
github.com/klothoplatform/klotho/pkg/static_unit	22%	❌
github.com/klothoplatform/klotho/pkg/validation	70%	➖
Summary	41% (3472 / 8437)	❌

[ewucc]

We need to update anything customer facing to reflect?

edit: oh i guess we don't say anything in the docs about it

[gordon-klotho]

We'll need to notify customers that use this on the change of behaviour. Especially those that sed the capacity before deploying.

[jhsinger-klotho]

We'll need to notify customers that use this on the change of behaviour. Especially those that sed the capacity before deploying.

Do we know who that is? I agree we should, although if they are really only using the 1 read/write capacity it wont get too expensive since they barely use it anyways. Agreed though just have no idea who is using it