-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Migrate to AWS SDKv2 #770
Comments
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
… location, dataSync task to awsSDKv2 gruntwork-io#770
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
… location, dataSync task to awsSDKv2 gruntwork-io#770
* change port access_analyzer, acm, acmpca, ami, API GWv1 & API GWv2 to awsSDKv2 #770 * change port backup vault, cloudTrail, cloudWatch alarm, cloudWatch dashboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 #770 * change port appRunner, ASG, config recorder, config service, dataSync location, dataSync task to awsSDKv2 #770
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
…l, ec2 ipam resource discovery, ec2 ipam scope, ec2 ipam to awsSDKv2 gruntwork-io#770 (gruntwork-io#781)
…l, ec2 ipam resource discovery, ec2 ipam scope, ec2 ipam to awsSDKv2 gruntwork-io#770
…ll resource policy, network firewall rule group, network firewall tls config to awsSDKv2 gruntwork-io#770
@james03160927 @wakeful Is EC2 being covered by someone? If not, then I think a new issue just for that would be nice. It's a much larger refactor. I would be happy to do it, but along the way, I would have some questions about how it's desired to be structured. |
@sc250024 You can pick the ec2 resource. AFAIK, there is some reference between ec2 resources and VPC (and actually all other network-related ones). Just ping on this issue to let us know what you'll be working on to avoid duplication. I’ll look over the weekend for any remaining resources that need a 'bump'. |
@wakeful I will open a new issue then. The reason is because I started down the rabbit hole with |
…fic policy to awsSDKv2 gruntwork-io#770
…fic policy to awsSDKv2 gruntwork-io#770
…ll resource policy, network firewall rule group, network firewall tls config to awsSDKv2 gruntwork-io#770
The AWS SDK v1 is officially deprecated (end-of-support is July 31, 2025). We need to migrate code to v2 before it ends the support for this.
The text was updated successfully, but these errors were encountered: