-
Notifications
You must be signed in to change notification settings - Fork 1.2k
documentation: Info about offline s3 bucket key when creating feature group #2646
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
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
reduce AWS KMS requests costs by up to 99 percent. | ||
For more information, see the S3 documentation for | ||
`Bucket Key | ||
<https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-key.html>`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWS KMS key ID for offline store.
If a KMS encryption key is not specified, SageMaker encrypts all data at
rest using the default AWS KMS key. By defining your bucket-level key for SSE, you can
reduce the cost of AWS KMS requests.
For more information, see
Bucket Key <https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-key.html>
_
in the Amazon S3 User Guide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(You should not use any marketing words in the sdk docstrings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revised according to your comments, thanks!
Issue #, if available:
Documentation offline_store_kms_key_id is not inclusive and lead charging customers more on encryption.
Description of changes:
Add more descriptive documentation message of offline_store_kms_key_id in create feature group to elaborate how to bring down the cost of using bucket key.
Testing done:
tox
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.General
Tests
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.