-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[New Resource]: Security Lake #29376
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I am interested in contributing, but as this would be my first issue on the AWS provider this might take a bit longer. I have a bit of experience with |
@aristosvo AWS published a workshop on contributing to the AWS provider, I would suggest you start there as a learning path. |
I will start working on this resource @aristosvo did you already made any progress? We can always collaborate :) |
Take it away, didn't have the time in the end. Will watch your MR to learn :) |
Happy to help contribute, I am a SME for Amazon Security Lake. |
Thats great @luescher-aws please ping me internally to connect @mkandyli |
Also happy to help if you want to connect internally. |
@luescher-aws anyone picked up the log configuration? If not happy to wrap that up, had a look and looks pretty straightforward. |
Hi @meetreks i am already working on that @luescher-aws you can work on custom logs if you want to pick something |
@markoskandylis shall i pick create subscriber then? |
@meetreks yes that sounds great 🙂 |
I wanted to see if progress is being made on aws log sources. I can pick that up if your work has stalled. |
Hi @gramsa49 aws log sources is now merged but you can take custom log sources if you want |
Hi i will stat the work for custom log source |
Anyone working on the securitylake subscriber resources ? |
Yes, let me check how far we are.
From: Kamalika Majumder ***@***.***>
Reply-To: hashicorp/terraform-provider-aws ***@***.***>
Date: Monday, February 12, 2024 at 1:20 PM
To: hashicorp/terraform-provider-aws ***@***.***>
Cc: "Luescher, Marc" ***@***.***>, Mention ***@***.***>
Subject: Re: [hashicorp/terraform-provider-aws] [New Resource]: Security Lake (Issue #29376)
Anyone working on the securitylake subscriber resources ?
—
Reply to this email directly, view it on GitHub<#29376 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7JB5GJMX6ODCCSWY3C4TL3YTJMNVAVCNFSM6AAAAAAU2S2JQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGI4TCNJRGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @kamalika-majumder currently i am working on it |
Oh great. @markoskandylis Any idea which release its going to be added next ? |
@kamalika-majumder i will aim for the 29th release hopefully a bit faster if posible |
This functionality has been released in v5.40.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Are there any plans to add a resource for managing Org configurations via following:
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Looking to add Security Lake as a new Terraform Resource / Data Source so users with IaC requirements in their production environments can effectively start using this service.
Requested Resource(s) and/or Data Source(s)
aws_security_lake_data_lake
aws_security_lake_aws_log_source
aws_security_lake_custom_log_source
aws_security_lake_subscriber
Potential Terraform Configuration
References
https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/securitylake
https://docs.aws.amazon.com/security-lake/latest/APIReference/API_CreateDatalake.html
https://docs.aws.amazon.com/security-lake/latest/APIReference/API_CreateSubscriber.html
https://docs.aws.amazon.com/security-lake/latest/APIReference/API_CreateAwsLogSource.html
https://docs.aws.amazon.com/security-lake/latest/APIReference/API_CreateCustomLogSource.html
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: