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

estimate-template-cost resource type coverage #217

Open
PatMyron opened this issue Oct 15, 2019 · 3 comments
Open

estimate-template-cost resource type coverage #217

PatMyron opened this issue Oct 15, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@PatMyron
Copy link
Contributor

PatMyron commented Oct 15, 2019

estimate-template-cost, aws/aws-cdk-rfcs#70

resource types that are currently supported in some form need to be documented

Looks like CloudFront, CloudWatch, EBS, EC2, ElastiCache, ELB, Elastic Beanstalk, RDS, Redshift, Route53, S3, SimpleDB, SNS, SQS, and VPC might have some level of support

We should also consider ignoring unsupported resource types rather than throwing an error

@PatMyron PatMyron self-assigned this Oct 15, 2019
@PatMyron
Copy link
Contributor Author

PatMyron commented Oct 21, 2019

Support for every EC2/RDS instance type supported by the simple monthly calculator rolling out region-by-region now. ElastiCache/Redshift still lacking support of some instance types supported by the simple monthly calculator

team currently working on me-south-1, af-south-1, and eu-south-1 support

Other partitions are not supportable with the current architecture

OSType won't be fully supported soon because describe-images doesn't yet return detailed Platform information beyond being Windows or not and we're not going to be calling describe-images on customers' private images anyways

simple monthly calculator

@atkinsonm
Copy link

It may become necessary to re-tool this command against https://calculator.aws which will eventually replace the SMC

@secbug
Copy link

secbug commented Nov 30, 2023

Is this issue being worked on by anyone @PatMyron or @brianterry , or potentially being overruled by another worktrack?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants