@aws-amplify/amplify-category-storage
Advanced tools
amplify-cli storage plugin
The following table lists the current set of commands supported by the Amplify Storage Category Plugin.
| Command | Description |
|---|---|
| amplify storage add | Takes you through steps in the CLI to add a storage resource to your backend. |
| amplify storage update | Takes you through steps in the CLI to update a storage resource. |
| amplify storage push | Provisions only storage cloud resources with the latest local developments. |
| amplify storage remove | Removes storage resource from your local backend. The resources are removed from the cloud on the next push command. |
| amplify storage override | Generates 'overrides.ts' for storage resource in your local backend. The resource properties can be overridden by editing this file. The resource is overridden in the cloud on the next push command. |
FAQs
amplify-cli storage plugin
The npm package @aws-amplify/amplify-category-storage receives a total of 19,022 weekly downloads. As such, @aws-amplify/amplify-category-storage popularity was classified as popular.
We found that @aws-amplify/amplify-category-storage demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
