awslabs / aws-break-glass-role Goto Github PK

As a User
I want to install aws-break-glass-role via brew
So that I am able to easily and quickly add an AWS Break Glass Role to my AWS account(s)

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

From AWS SDK for JavaScript v2 README:

We are formalizing our plans to make the Maintenance Announcement (Phase 2) for AWS SDK for JavaScript v2 in 2023.

Describe the solution you'd like

Migrate JS SDK v2 APIs to v3

Migration Guide: https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/migrating-to-v3.html

Describe alternatives you've considered
N/A

The actions the BreakGlass user does are logged in CloudTrail, but at least for the signin, this depends on the region. By default it's only logged, if the user signs in in us-east-1. All our resources are located in eu-central-1. If the user signs in there, nothing is logged.
In my opinion it's not a good solution to just deploy the logging resources in every region, as the list of default regions is pretty long. They can not be disabled as it's very error prone, as one can easily forget a region.

Either an easy to deploy logging accross all regions needs to be added or a chance to limit the user to login in dedicated regions.

Our organisation is only active in one region, eu-central-1. IAM is a global service to it's logged in us-east-1.

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

[email protected] verify-conditions
node ./scripts/index.js signin && node ./scripts/index.js cleanup us-east-1 us-east-2 us-west-2 && npm run integ

Credentials File Created
No Log Groups found for us-east-1
No Log Groups found for us-east-2
No Log Groups found for us-west-2

[email protected] integ
npm run test-build && integ-runner

[email protected] test-build
tsc --project tsconfig.test.json

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

When a contributor makes a pull request, we want to be able to test the code in the PR while also avoiding running the integration tests for pull requests to reduce attack surface for bad actors.

Add instructions to the readme for installing from npm

The architecture diagram in the Readme.md has a hyperlink. The target is an Amazon-internal resource protected by midway, rendering it inaccessible to non-Amazonians.