Skip to content
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

Merged
merged 1 commit into from
Jan 8, 2024
Merged

Fix endpoint override for demo deployment #2823

merged 1 commit into from
Jan 8, 2024

Conversation

ltrung
Copy link
Contributor

@ltrung ltrung commented Jan 6, 2024

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:

  1. Have you successfully run npm run build:release locally? Yes

  2. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? N/A

  3. 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.

@ltrung ltrung requested a review from a team as a code owner January 6, 2024 02:58
@@ -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';
Copy link
Contributor

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?

Copy link
Contributor Author

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',
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thanks!

@ltrung ltrung merged commit a97110f into main Jan 8, 2024
10 checks passed
@ltrung ltrung deleted the fix-script branch January 8, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants