Our Webview Applications Not Working After Authority Changes

Based on the information provided, it appears that your recent authorization changes have had unintended consequences, affecting both your server access and your webview applications. Let's address the issues one by one:

1. EC2 Instance SSH Access: The limited access to certain directories and lack of root privileges suggests that the user permissions have been modified. The empty sudoers.d directory and potential modifications to the /etc/sudoers file indicate that sudo privileges have been altered or removed for the ubuntu user.

2. Webview Application Issues: The authorization errors in API requests from the webview applications are likely related to the same changes that affected the server permissions. This could be due to modified security groups, IAM roles, or API gateway settings that are now preventing the webview applications from accessing the necessary resources.

To resolve these issues:

1. Review and restore the correct permissions in the /etc/sudoers file. You may need to use a root-level account or contact AWS support if you've completely lost sudo access.

2. Check your security groups and ensure that the necessary ports are open for your webview applications to communicate with your servers.

3. Review your IAM roles and policies to ensure that the correct permissions are in place for your applications to make API requests.

4. Verify that your API gateway settings haven't been inadvertently changed during the authorization updates.

Regarding your question about reverting to a backup: Yes, restoring from a backup taken a few days before the problem occurred could potentially solve these issues. This would revert your server and application configurations to a state before the problematic changes were made. However, keep in mind that this would also undo any other changes or updates made since that backup, so you'd need to carefully consider the implications and potentially reapply any necessary changes after the restore.

Before proceeding with a full restore, it's recommended to:

1. Attempt to fix the issues manually first, as this can be quicker and less disruptive.
2. If a restore is necessary, create a new test environment from the backup to verify that it resolves the issues before applying it to your production environment.
3. Document the current state and the changes made during the authorization update to help prevent similar issues in the future.

Remember to always test changes in a staging environment before applying them to production, and maintain detailed documentation of your system configurations and any modifications made.
Sources
Troubleshooting Image Builders - Amazon AppStream 2.0
Full Stack Development - Web and Mobile Apps - AWS Amplify Authentication