Skip to content

Support disabling Amazon CloudFront for confidential use cases #125

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

Open
endowataru opened this issue May 8, 2023 · 2 comments
Open

Support disabling Amazon CloudFront for confidential use cases #125

endowataru opened this issue May 8, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@endowataru
Copy link

Is your feature request related to a problem? Please describe.

This solution depends on Amazon CloudFront to host the console UI. Using CloudFront is often prohibited for confidential use cases, especially in financial companies.

Describe the feature you'd like

Adding a feature to disable CloudFront and provide an alternative method. I think that the UI can be accessed via AWS PrivateLink instead.

@endowataru endowataru added the enhancement New feature or request label May 8, 2023
@kamyarz-aws
Copy link
Member

We will add this to our backlog for future developement .

@will-cloudful
Copy link

will-cloudful commented Mar 20, 2025

I have a similar need as CloudFront has not received authorization to run in GovCloud. I realized that if CloudFront is disabled, then console users will need to access the S3 bucket directory as a static website, which may not be ideal because you won't be able to access it through HTTPS. How about deploying the console app (which is build in React.js) using Elastic Beanstalk?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants