aws_security_viz 0.2.1.pre.alpha.pre.362 → 0.2.1.pre.alpha.pre.375

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +21 -0
  3. data/aws_security_viz.gemspec +1 -1
  4. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a4310a3c1e1ec252c7a1cd0faeb95f5981024e553beb3431a340ea566f382f42
4
- data.tar.gz: cc1ebc90a80247a50a5f4c25c35960731a557593e9cfd42167bd115ec0b91f68
3
+ metadata.gz: 9792223a0a63ba3eba3e5bc62494a66bc49d7bdd87ab0fc82c9d62d4b69819ef
4
+ data.tar.gz: 9c69e3e6b921286ac622dde7201ff979ef293ae19fae50bf36949b0283d4a2ef
5
5
  SHA512:
6
- metadata.gz: d83d3ed86b2f2182015464a9c958a53d2efc54125af621f653a91340cde25c2a044ac6171cacb5d565f048e3f90aa8b5a24ad91e3b0dbcc9aa17d688fc0702c3
7
- data.tar.gz: cbc60d0cf32ed6ecfa645ea355524b371c14f9b984847f000221a0702fefa7ea5d98a6daabab09e3a28935ce3711a76690aafbfdb2ffec35928692fd8b58edf0
6
+ metadata.gz: d187218ed2a11c2750d43c811056a76ab8d8dc3e48925381ef565d0493b59a2ab00dd3c7f51ca204de6283fca2f5902741fb3d9f9ab5f5012af20539137a2e72
7
+ data.tar.gz: 60dbdb7b87493d77e48a316969b5527980e558b0a3acb13e883132c482ceaf30a85632350e61bdd161ee8ddbed71851c9ea75e54cf3771c576462c22f2ece718
data/README.md CHANGED
@@ -81,6 +81,27 @@ Options:
81
81
  -h, --help Show this message
82
82
  ```
83
83
 
84
+ #### Configuration
85
+
86
+ aws-security-viz only uses the `ec2:DescribeSecurityGroups` api so a minimal IAM policy which grants only `ec2:DescribeSecurityGroups` access should be enough.
87
+
88
+ ```json
89
+ {
90
+ "Version": "2012-10-17",
91
+ "Statement": [
92
+ {
93
+ "Effect": "Allow",
94
+ "Action": "ec2:DescribeSecurityGroups",
95
+ "Resource": "*"
96
+ }
97
+ ]
98
+ }
99
+ ```
100
+
101
+ Alternatively you can use [aws-vault](https://github.com/99designs/aws-vault/) and run it using short lived temporary credentials.
102
+
103
+ `$ aws-vault exec <profile> -- aws_security_viz -f aws.json --renderer navigator`
104
+
84
105
  #### Advanced configuration
85
106
 
86
107
  You can generate a configuration file using the following command:
@@ -32,7 +32,7 @@ Gem::Specification.new do |s|
32
32
  s.add_runtime_dependency 'optimist', '~> 3.0.0'
33
33
  s.add_runtime_dependency 'organic_hash', '~> 1.0', '>= 1.0.2'
34
34
  s.add_runtime_dependency 'rgl', '~> 0.5.3'
35
- s.add_runtime_dependency 'aws-sdk-ec2', '>= 1.65', '< 1.112'
35
+ s.add_runtime_dependency 'aws-sdk-ec2', '>= 1.65', '< 1.166'
36
36
 
37
37
  s.required_ruby_version = '>= 2.0.0'
38
38
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws_security_viz
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.1.pre.alpha.pre.362
4
+ version: 0.2.1.pre.alpha.pre.375
5
5
  platform: ruby
6
6
  authors:
7
7
  - Anay Nayak
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2020-05-17 00:00:00.000000000 Z
11
+ date: 2020-06-11 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler
@@ -155,7 +155,7 @@ dependencies:
155
155
  version: '1.65'
156
156
  - - "<"
157
157
  - !ruby/object:Gem::Version
158
- version: '1.112'
158
+ version: '1.166'
159
159
  type: :runtime
160
160
  prerelease: false
161
161
  version_requirements: !ruby/object:Gem::Requirement
@@ -165,7 +165,7 @@ dependencies:
165
165
  version: '1.65'
166
166
  - - "<"
167
167
  - !ruby/object:Gem::Version
168
- version: '1.112'
168
+ version: '1.166'
169
169
  description: Provides a quick mechanism to visualize your EC2 security groups in multiple
170
170
  formats
171
171
  email: anayak007+rubygems@gmail.com