Open watilde opened 3 years ago
@watilde Thank you for the feedback. We will work to prioritize this feature request and keep you updated.
In addition, an user reported a blocker that they needed filtering by IP address to adopt Amplify in their corporate blog. Apparently, filtering with S3 was used as work-around. Refs: The story of hosting a kintone Storybook with a product support team.
Just for reference that an another developer mentions the same pain point: https://twitter.com/shinofara/status/1371290463618015235.
@watilde just to be clear we are planning on adding support for IP filtering this year. Will that accomplish your usecase
@swaminator We also need to restrict access by source IP to a static website deployed from the Amplify Console.
Is your feature request related to a problem? Please describe. User story: As an enterprise architect, I want to restrict access via IAM/SSO so that Amplify console meets my company's security rule.
Describe the solution you'd like Support IAM/SSO at Amplify console's access control.
Additional context Some Amplify users mentioned the new announcement of GitHub pages that allows only users who have access to the repositories to see the GitHub Pages as a wish item to Amplify console.