fix(job): add resource policy to environment to unblock job logs #4979
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #4389. Customers who are currently blocked by the log resource policy issue should be able to resolve it by running
copilot env deploy
to upgrade their environments to the latest version.This PR creates a Log Resource Policy as a part of each environment which handles the necessary permissions for state machines to write logs to CloudWatch. The policy is managed as part of the environment lifecycle and will be cleaned up after deletion.
Customers who need more than 10 environments per account & region can get around this issue by running
copilot env override --tool yamlpatch
and removing the log resource policy:Then, they can set up a custom log resource policy for all their environments in a region:
Then, modify this
policy.json
file to include the following "resource" snippetBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the Apache 2.0 License.