-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix endpoint override for demo deployment #2823
Conversation
@@ -11,7 +11,7 @@ let app = `meetingV2`; | |||
let useEventBridge = false; | |||
let enableTerminationProtection = false; | |||
let disablePrintingLogs = false; | |||
let chimeSDKMeetingsEndpoint = 'https://service.chime.aws.amazon.com'; | |||
let chimeSDKMeetingsEndpoint = 'https://meetings-chime.us-east-1.amazonaws.com'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we generate the endpoint based on region?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally yes but these values are default value and the default region value is us-east-1 so it does not make any difference.
const chimeSDKMediaPipelines = new ChimeSDKMediaPipelines({ region: 'us-east-1' }); | ||
chimeSDKMediaPipelines.endpoint = process.env.CHIME_SDK_MEDIA_PIPELINES_ENDPOINT || "https://media-pipelines-chime.us-east-1.amazonaws.com" | ||
const chimeSDKMediaPipelines = new ChimeSDKMediaPipelines({ | ||
region: 'us-east-1', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use currentRegion
her as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think SDK media pipeline is currently hard-coded to us-east-1 by default. Thought about fixing it but decided not to as it is not related to this PR which is just to fix endpoint syntax for the SDK client.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thanks!
Description of changes:
Fix endpoint override for demo deployment. After migrating to aws sdk js v3, the previous syntax for override endpoint did not work.
Testing:
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Testing serverless demo with overriden endpoint
Checklist:
Have you successfully run
npm run build:release
locally? YesDo you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? N/A
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.