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

Add a script to determine the AWS resources used #1050

Merged
merged 2 commits into from
Oct 9, 2024

Conversation

peternied
Copy link
Member

Description

To help customers determine what resources are used by the Migration Assistant when deployed adding a shell script that can be used on the bootstrap machine to identify what there deployment will require based on the synthesized stacks.

Example output:

./aws-feature-usage.sh default
Synthesizing all stacks...
Synthesizing stack: networkStack-default
Synthesizing stack: migrationInfraStack
Synthesizing stack: reindexFromSnapshotStack
Synthesizing stack: migration-console
Finding resource usage from synthesized stacks...
-----------------------------------
IAM Policy Actions:
cloudwatch:GetMetricData
cloudwatch:ListMetrics
ec2:DescribeRouteTables
ec2:DescribeSubnets
ecr:BatchCheckLayerAvailability
...
-----------------------------------
Resources Types:
AWS::CDK::Metadata
AWS::EC2::InternetGateway
AWS::EC2::Route
AWS::EC2::RouteTable
AWS::EC2::SecurityGroup
...

Testing

Ran locally, manually

Check List

  • New functionality includes testing
    • All tests pass, including unit test, integration test and doctest
  • New functionality has been documented
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

To help customers determine what resources are used by the Migration
Assistant when deployed adding a shell script that can be used on the
bootstrap machine to identify what there deployment will require based
on the synthesized stacks.

Example output:
```shell
./aws-feature-usage.sh default
Synthesizing all stacks...
Synthesizing stack: networkStack-default
Synthesizing stack: migrationInfraStack
Synthesizing stack: reindexFromSnapshotStack
Synthesizing stack: migration-console
Finding resource usage from synthesized stacks...
-----------------------------------
IAM Policy Actions:
cloudwatch:GetMetricData
cloudwatch:ListMetrics
ec2:DescribeRouteTables
ec2:DescribeSubnets
ecr:BatchCheckLayerAvailability
...
-----------------------------------
Resources Types:
AWS::CDK::Metadata
AWS::EC2::InternetGateway
AWS::EC2::Route
AWS::EC2::RouteTable
AWS::EC2::SecurityGroup
...
```

Signed-off-by: Peter Nied <peternied@hotmail.com>
Copy link

codecov bot commented Oct 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.59%. Comparing base (647f601) to head (d61b416).
Report is 20 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1050      +/-   ##
============================================
+ Coverage     80.57%   80.59%   +0.02%     
  Complexity     2736     2736              
============================================
  Files           365      365              
  Lines         13611    13653      +42     
  Branches        941      941              
============================================
+ Hits          10967    11004      +37     
- Misses         2067     2069       +2     
- Partials        577      580       +3     
Flag Coverage Δ
gradle-test 78.58% <ø> (-0.03%) ⬇️
python-test 90.24% <ø> (+0.13%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

…ploy script

Signed-off-by: Peter Nied <peternied@hotmail.com>
@peternied peternied merged commit 376180d into opensearch-project:main Oct 9, 2024
14 checks passed
@peternied peternied deleted the aws-features branch October 9, 2024 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants