Richard Boyd
Richard Boyd
I think you could accomplish this by creating a "naming Aspect" that manually sets the physical name for each resource it visits. Since the decision to apply the prefix to...
@hoegertn Right, which is why the customers should implement their own Naming Aspect. I'm really curious how this security approach works when you need to replace a DynamoDB Table that...
I'm sure there are plenty of teams that are using name prefixes for security, but I'm not sure that adding it to cdk core is the right solution. Suppose the...
They can both lead to fully specified LogicalIds, which CFN turns into physical names.
@PeterBengtson Here is an example to do what you're asking app.py ``` #!/usr/bin/env python3 from aws_cdk import ( core ) from hello.hello_stack import MyStack, LogicalIdSetter app = core.App() my_prefix =...
This will walk every node in the cdk Construct and look for either Lambda Functions or S3 Buckets and give them a name like `MyTeam-hellocdk1MyLambdaFunctionA23CA5A9`
Obviously, you would have the Aspect defined separately from the Stacks, I just consolidated them into fewer files to make it easier to share on github.
Closing this because @steven-cuthill-otm 's issue is a much better (more generic) version of this request. https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues/86
I’ve been convinced that they’re actually separate issues, thought they’d compliment each other nicely.
@keetonian I have a solution that I'm speaking to the API Gateway team about this week. I'd love to be able to add it to SAM