Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dynamodb_table support for On-Demand billing #56923

Open
kmasaryk opened this issue May 24, 2019 · 6 comments
Open

dynamodb_table support for On-Demand billing #56923

kmasaryk opened this issue May 24, 2019 · 6 comments

Comments

@kmasaryk
Copy link

@kmasaryk kmasaryk commented May 24, 2019

SUMMARY

A new billing mode was added to DynamoDB back in Nov, 2018 called On-Demand which acts as an alternative to setting RCU and WCU values. This feature is already supported in Boto 3 with the BillingMode attribute. This feature request is to implement the On-Demand billing option in the dynamodb_table module.

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

dynamodb_table

ADDITIONAL INFORMATION

Note that there's already an Issue opened for this which wasn't filled in correctly: #54963. Instead of letting that issue languish any further, I suggest closing it in favor of this one.

Another link explaining how the new pricing model works: https://aws.amazon.com/dynamodb/pricing/

I'd suggest adding a 'billing_mode' parameter to the module which can hold a value of either 'provisioned' or 'pay_per_request' to reflect Boto3 values. The 'indexes' parameter will also need to be updated since GSI's can also support on-demand billing. 'billing_mode' should probably default to 'pay_per_request' since that seems like a more popular and generic setting unless you know exactly how many RCU/WCU's you want; This is the reason AWS added this mode, of course. To support backwards compatibility with existing tasks, if 'read_capacity' and 'write_capacity' are set then the 'billing_mode' would switch to 'provisioned' automatically.

Example:

- dynamodb_table:
    name: my-table
    region: us-east-1
    hash_key_name: id
    hash_key_type: STRING
    range_key_name: create_time
    range_key_type: NUMBER
    billing_mode: PAY_PER_REQUEST
    tags:
      tag_name: tag_value
@ansibot

This comment has been minimized.

Copy link
Contributor

@ansibot ansibot commented May 24, 2019

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot

This comment has been minimized.

Copy link
Contributor

@ansibot ansibot commented May 24, 2019

@ansibot

This comment has been minimized.

Copy link
Contributor

@ansibot ansibot commented May 24, 2019

@kmasaryk, just so you are aware we have a dedicated Working Group for aws.
You can find other people interested in this in #ansible-aws on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

@Gourds

This comment has been minimized.

Copy link

@Gourds Gourds commented Jul 30, 2019

I also need this option now.

@prasadkatti

This comment has been minimized.

Copy link
Contributor

@prasadkatti prasadkatti commented Oct 5, 2019

The module needs to be upgraded to use boto3 before we can add this feature. There is a stale PR related to this - #45402.

@ansibot

This comment has been minimized.

Copy link
Contributor

@ansibot ansibot commented Jan 25, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.