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

[amazon-neptune-and-aws-cdk-for-amundsen] In Customization #110

Open
sangram23 opened this issue Aug 26, 2022 · 3 comments
Open

[amazon-neptune-and-aws-cdk-for-amundsen] In Customization #110

sangram23 opened this issue Aug 26, 2022 · 3 comments

Comments

@sangram23
Copy link

Hi Team,

We have already working AWS account where we don't have option to create new vpn and public subnet. How can we customize this git as per our environment .

Customization like :

1)- Use existing VPC and respective perquisites.
2)- How to do all config in public subnet.
3)- ECS cluster creation and using ECR for docker image etc.

@triggan
Copy link
Contributor

triggan commented Aug 26, 2022

Hi @sangram23,

There are multiple samples within this repository. Which one specifically are you looking to reuse/customize?

@sangram23
Copy link
Author

I am looking for Amundsen where i can use already configured service in our environement for below stack:

VPC stack
Amazon RDS for PostgreSQL
Amazon Redshift cluster
Bastion host

@triggan triggan changed the title In Customization [amazon-neptune-and-aws-cdk-for-amundsen] In Customization Aug 26, 2022
@triggan
Copy link
Contributor

triggan commented Aug 26, 2022

That sounds like a very bespoke deployment. The code provided in this repo is to be used for reference purposes or experimentation. It doesn't cover every possible deployment pattern or architecture.

The Amundsen sample deployment stack[1] is written in CDK and modularized so that you can deploy each component individually. So if you wanted to skip the VPC, RDS Postgres, Redshift, and Bastion stacks, you can certainly do that. It may require manually retrieving the required parameters to launch the remaining stacks (as those parameters may have original come from the stacks that you don't want to deploy).

Modifying these stacks for public subnets may require directly modifying the CDK code. If you've never used CDK before, you can find some getting started material in our docs [1] and some really good introductory workshops [2].

Not everything in these stacks can take advantage of public subnets. For example, Neptune is only accessilble from inside of a VPC and only ever gets assigned private IP addresses (no public IP addresses are ever assigned, even if you specify using a public subnet).

[1] https://github.com/aws-samples/amazon-neptune-samples/tree/master/amazon-neptune-and-aws-cdk-for-amundsen
[2] https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html
[3] https://workshops.aws/card/cdk

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

No branches or pull requests

2 participants