aws-amplify / aws-amplify/amplify-cli
S3 ARN instead of URL?
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
Amplify CLI version 4.41.2. We are attempting to push the auth service to our instance, but we're getting the error "The specified bucket doesn't exist".
We were able to trace this down to `auth.providerMetadata.s3TemplateURL` in `amplify/backend/amplify-meta.json`. In the file, the template URL is an HTTPS URL instead of an AWS ARN. Our policy prohibits assigning public URLs to S3 buckets and when we try to use an ARN it gets reset to the HTTPS URL.
Is there a workaround for this, or does amplify require that the template URL be an HTTPS URL?
Contributor guide
Research direction
Start with amplify/backend/amplify-meta.json and the auth.providerMetadata.s3TemplateURL value, then reproduce the push with the HTTPS URL and with an ARN. Trace where the value is generated or reset; done means the supported template reference is documented or the reported reset behavior is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- authentication, cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100