aws / aws/aws-cdk

aws_cdk.aws_ec2.NatInstanceProvider: Access NAT Instance Profile

Open
#23,894 1 comment 0 reactions 1 assignee Claimed by @pahud View on GitHub
@aws-cdk/aws-ec2 bug effort/small p2
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
1d 19h
Merged PRs (30d)
74

Description

### Describe the bug

There is no way to interact with the Instance Profile generated for the NAT in order to attach the AmazonSSMManagedInstanceCore policy so that Security Hub SSM.1 | EC2 instances should be managed by AWS Systems Manager will be happy. :)

### Expected Behavior

There would be some way to access or set the Instance Profile the NAT instance will use.

### Current Behavior

There is no way to access it or replace the NAT instance profile.

### Reproduction Steps

Build a NAT instance as part of a VPC and the instance profile it creates has no policies attached and there is no way to access them via the CDK.

### Possible Solution

Make an instance_profile parameter on NatInstanceProvider Class. Or attach the SSM policy by default.

### Additional Information/Context

https://docs.aws.amazon.com/cdk/api/v1/python/aws_cdk.aws_ec2/NatInstanceProvider.html

### CDK CLI Version

2.61.1 (build d319d9c)

### Framework Version

_No response_

### Node.js Version

v14.17.0

### OS

WSL: 20.04.5 LTS (Focal Fossa)

### Language

Python

### Language Version

Python 3.8.10

### Other information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.